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 20:36:58 -0400 [thread overview]
Message-ID: <185cb06d-c7fb-4104-9301-48be63e6b789@www.fastmail.com> (raw)
In-Reply-To: <CAMP9c5krwMUZpe+PiUPsMSUQVMbu50-eb9ShDY3bPtouobsCiw@mail.gmail.com>
On Wed, Aug 11, 2021, at 7:25 PM, Zach Riggle wrote:
> TLDR 1: I learned/realized that zsh builtin echo automatically
> interprets escape codes, unlike bash echo and /bin/echo.
But like the builtins of dash and yash.
% zsh -c 'echo "a\nb"'
a
b
% bash -c 'echo "a\nb"'
a\nb
% ksh -c 'echo "a\nb"'
a\nb
% dash -c 'echo "a\nb"'
a
b
% yash -c 'echo "a\nb"'
a
b
The echo(1) utility is notoriously unportable [1][2], and it's worth
considering avoiding it completely.
[1]: https://pubs.opengroup.org/onlinepubs/9699919799/utilities/echo.html#tag_20_37_16
[2]: https://wiki.bash-hackers.org/commands/builtin/echo#portability_considerations
--
vq
next prev parent reply other threads:[~2021-08-12 0:38 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
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 [this message]
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=185cb06d-c7fb-4104-9301-48be63e6b789@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).