Doc material on Windows and triple-double-quoting (#595)

* Windows doc re DSL quoting

* windows screenshot

* Windows doc re DSL quoting
This commit is contained in:
John Kerl 2021-07-06 03:29:38 +00:00 committed by GitHub
parent 6e3b9ac5d1
commit 10c89c5cba
No known key found for this signature in database
GPG key ID: 4AEE18F83AFDEB23
4 changed files with 14 additions and 5 deletions

View file

@ -37,6 +37,12 @@ The Windows-support code within Miller makes effort to support Linux/Unix/MacOS-
.. image:: pix/miller-msys-complex.png
One workaround is to use MSYS2. Another is to put more complex DSL expressions into a file:
Single quotes with ``&&`` or ``||`` inside are fundamentally unhandleable within Windows; there is nothing Miller can do here as the Windows command line is split before Miller ever receives it.
One workaround is to use MSYS2. Another workaround is to put more complex DSL expressions into a file:
.. image:: pix/miller-windows-complex-workaround.png
A third workaround is to replace ``"`` with ``"""``, then ``'`` with ``"``:
.. image:: pix/miller-windows-triple-double-quote.png

View file

@ -34,6 +34,12 @@ The Windows-support code within Miller makes effort to support Linux/Unix/MacOS-
.. image:: pix/miller-msys-complex.png
One workaround is to use MSYS2. Another is to put more complex DSL expressions into a file:
Single quotes with ``&&`` or ``||`` inside are fundamentally unhandleable within Windows; there is nothing Miller can do here as the Windows command line is split before Miller ever receives it.
One workaround is to use MSYS2. Another workaround is to put more complex DSL expressions into a file:
.. image:: pix/miller-windows-complex-workaround.png
A third workaround is to replace ``"`` with ``"""``, then ``'`` with ``"``:
.. image:: pix/miller-windows-triple-double-quote.png

Binary file not shown.

After

Width:  |  Height:  |  Size: 85 KiB

View file

@ -25,9 +25,6 @@ DOC6
* number-formatting page
* windows &&/|| note
o note "true&&false" vs 'true && false'; & " ... """...""" ..."
* check <-> manpage/olh sections & doc6 sections
* fill out: