zsh-users
 help / color / mirror / code / Atom feed
* Odd behavior with various (q) array modifiers and non-printable characters (backspace, newline)
@ 2021-08-11 20:29 Zach Riggle
  2021-08-11 21:16 ` Bart Schaefer
  2021-08-11 21:27 ` Bart Schaefer
  0 siblings, 2 replies; 13+ messages in thread
From: Zach Riggle @ 2021-08-11 20:29 UTC (permalink / raw)
  To: Zsh Users

Hello all!  It's me again, hopefully with a useful question.

TLDR: (q-) behaves unexpectedly for \010 aka "\b", and there are other
corner cases that may be unintended.

I love the (q-) modifier for array expansion, since it allows printing
out e.g. a command and then running it.

    run() {
        echo '$' "${(q-)@}"
        "$@"
    }

The docs (https://zsh.sourceforge.io/Doc/Release/Expansion.html,
search for "q-" to jump to the right area) state:

> If a q- is given (only a single q may appear), a minimal form of single quoting is used that only quotes the string if needed to protect special characters. Typically this form gives the most readable output.
> If a q+ is given, an extended form of minimal quoting is used that causes unprintable characters to be rendered using $’...’. This quoting is similar to that used by the output of values by the typeset family of commands.

However, it appears that half of the q modifiers handle 0x08 / \010 /
"\b" aka "backspace" in an unexpected manner.  Notably, (q) is
incorrect, (qq) (q+) and (q-) embed a literal backspace, which causes
unexpected output (it's there if you pipe to e.g. xxd, but it should
be escaped).

    $ mysed=( gsed "s/\ba\b/x/" )

    $ echo "aaaa a aaa" | "${mysed[@]}"
    aaaa x aaa

    $ echo ${(q)mysed}
    gsed s/\ba\b/x/

    $ echo ${(qq)mysed}
    'gsed' 's/x/'

    $ echo ${(qqq)mysed}
    "gsed" "s/\ba\b/x/"

    $ echo ${(qqqq)mysed}
    $'gsed' $'s/\ba\b/x/'

    $ echo ${(q+)mysed}
    gsed 's/x/'

    $ echo ${(q-)mysed}
    gsed 's/x/'

This issue also appears with newlines, but for these one could argue
it's entirely legitimate to have a *literal* newline that breaks the
quoted statement onto multiple lines.  Once again, the same culprits
are (qq), (q-), and (q+).  Interestingly, bare (q) is actually
incorrect.

    $ newline=( aa "b\nb" cc )

    $ echo ${(q)newline}
    aa b\nb cc

    $ echo ${(qq)newline}
    'aa' 'b
    b' 'cc'

    $ echo ${(qqq)newline}
    "aa" "b\nb" "cc"

    $ echo ${(qqqq)newline}
    $'aa' $'b\nb' $'cc'

    $ echo ${(q-)newline}
    aa 'b
    b' cc

    $ echo ${(q+)newline}
    aa 'b
    b' cc

IMHO both newline and backspace should be escaped at LEAST for (q-)
and (q+), and newline behavior for (q) is incorrect.  What's your
opinion?

Zach Riggle


^ permalink raw reply	[flat|nested] 13+ messages in thread

end of thread, other threads:[~2021-10-21 15:24 UTC | newest]

Thread overview: 13+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2021-08-11 20:29 Odd behavior with various (q) array modifiers and non-printable characters (backspace, newline) Zach Riggle
2021-08-11 21:16 ` Bart Schaefer
2021-08-11 21:42   ` Lawrence Velázquez
2021-08-11 23:25     ` Zach Riggle
2021-08-12  0:22       ` Bart Schaefer
2021-08-12  0:34         ` Lawrence Velázquez
2021-08-12 13:34         ` Ray Andrews
2021-08-12  0:36       ` Lawrence Velázquez
2021-08-14 15:52     ` Daniel Shahaf
2021-10-19 19:17       ` Zach Riggle
2021-10-21 14:24         ` Daniel Shahaf
2021-10-21 15:23           ` Bart Schaefer
2021-08-11 21:27 ` Bart Schaefer

Code repositories for project(s) associated with this public inbox

	https://git.vuxu.org/mirror/zsh/

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).