From: Bart Schaefer <schaefer@brasslantern.com>
To: Ray Andrews <rayandrews@eastlink.ca>
Cc: Zsh Users <zsh-users@zsh.org>
Subject: Re: array with newlines preserved as literal text
Date: Tue, 2 Feb 2021 12:25:22 -0800 [thread overview]
Message-ID: <CAH+w=7bAZKawy_BfTMGzuCm96NB=gDA6R-K9aZBd4N+uOOT-=A@mail.gmail.com> (raw)
In-Reply-To: <52dba8e4-2538-7c96-ecd5-66e017ab2b8e@eastlink.ca>
On Tue, Feb 2, 2021 at 11:16 AM Ray Andrews <rayandrews@eastlink.ca> wrote:
>
> I create some nasty output involving a grep search, save to to a
> variable, send it to a function which ends up calling 'eval' which
> receives the input and executes it like this:
>
> @ eval "$@"
> echo "\nYou (hard return)
> will\\nregret'\x0a'\nthe day you '\n' were born."
I'm curious why you want to save this in the form of a command to be
eval'd rather than just save the argument string?
Pretty much any time I start to write an "eval" I go back to make sure
I didn't do something wrong earlier. **
Roman's answers are otherwise spot-on.
** Of about 90 instances of "eval" in the contributed Functions
directory, 45 are one of these three cases:
1) eval "var_$suffix=value" (there are 36 of these)
2) eval "[[ ... ]]"
3) eval "(( ... ))"
Most eval'd assignments could probably be replaced with { typeset
var_$suffix=value } (sometimes adding -g).
next prev parent reply other threads:[~2021-02-02 20:26 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-02 19:16 Ray Andrews
2021-02-02 19:26 ` Roman Perepelitsa
2021-02-03 1:10 ` Ray Andrews
2021-02-02 20:25 ` Bart Schaefer [this message]
2021-02-02 23:31 ` Ray Andrews
2021-02-03 2:21 ` Bart Schaefer
2021-02-03 19:29 ` Ray Andrews
2021-02-03 21:19 ` Bart Schaefer
2021-02-04 2:07 ` Ray Andrews
2021-02-05 2:57 ` Bart Schaefer
2021-02-04 21:55 ` Ray Andrews
2021-02-05 3:22 ` Bart Schaefer
2021-02-05 4:17 ` Ray Andrews
2021-02-05 4:24 ` 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='CAH+w=7bAZKawy_BfTMGzuCm96NB=gDA6R-K9aZBd4N+uOOT-=A@mail.gmail.com' \
--to=schaefer@brasslantern.com \
--cc=rayandrews@eastlink.ca \
--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).