From: "Lawrence Velázquez" <larryv@zsh.org>
To: "Zach Riggle" <zachriggle@gmail.com>
Cc: "Bart Schaefer" <schaefer@brasslantern.com>, zsh-users@zsh.org
Subject: Re: Odd behavior with various (q) array modifiers and non-printable characters (backspace, newline)
Date: Wed, 11 Aug 2021 17:42:09 -0400 [thread overview]
Message-ID: <27bc215c-3916-4afe-b8b3-7946dd0cb4bc@www.fastmail.com> (raw)
In-Reply-To: <CAH+w=7bkaBZYR0Ok+zwqEqNDAjRDK1GyP9k74wY4-X+6jOrTEw@mail.gmail.com>
On Wed, Aug 11, 2021, at 5:16 PM, Bart Schaefer wrote:
> You need to stop testing things with "echo". The "echo" builtin
> interprets some backslash escapes itself, which will confuse you about
> what the quoting options have done.
>
> Repeat all your tests instead with
> printf "%s\n" ${(q)...}
> and so on, and come back if you still have questions.
Additionally, \b and \n are not interpreted in double quotes, so
your initial data does not actually contain BS or NL characters.
Presumably you thought "..." works like $'...'.
% mysed_orig=( gsed "s/\ba\b/x/" )
% typeset -p mysed_orig
typeset -a mysed_orig=( gsed 's/\ba\b/x/' )
% mysed_fixed=(gsed $'s/\ba\b/x/')
% typeset -p mysed_fixed
typeset -a mysed_fixed=( gsed $'s/\C-Ha\C-H/x/' )
% newline_orig=( aa "b\nb" cc )
% typeset -p newline_orig
typeset -a newline_orig=( aa 'b\nb' cc )
% newline_fixed=( aa $'b\nb' cc )
% typeset -p newline_fixed
typeset -a newline_fixed=( aa $'b\nb' cc )
As per the QUOTING section of zshmisc(1):
Inside double quotes (""), parameter and command substitution
occur, and `\' quotes the characters `\', ``', `"', `$',
and the first character of $histchars (default `!').
--
vq
next prev parent reply other threads:[~2021-08-11 21:46 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-11 20:29 Zach Riggle
2021-08-11 21:16 ` Bart Schaefer
2021-08-11 21:42 ` Lawrence Velázquez [this message]
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
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=27bc215c-3916-4afe-b8b3-7946dd0cb4bc@www.fastmail.com \
--to=larryv@zsh.org \
--cc=schaefer@brasslantern.com \
--cc=zachriggle@gmail.com \
--cc=zsh-users@zsh.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
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).