From: Ray Andrews <rayandrews@eastlink.ca>
To: Zsh Users <zsh-users@zsh.org>
Subject: why is eval needed?
Date: Sat, 19 Nov 2022 06:34:30 -0800 [thread overview]
Message-ID: <d0ef2035-e8e9-00c5-7f53-b16609d96262@eastlink.ca> (raw)
[-- Attachment #1: Type: text/plain, Size: 891 bytes --]
In a script:
local level='-L 2'
tree $level
#eval tree $level
run it:
2 /aWorking/Zsh/Source/Wk 0 $ . testing
tree: Missing argument to -L option.
If I use 'eval' it's fine. Now, I roughly understand that we need
'eval' when there's some complicated nesting of expansions or some other
complexity, but I also recall that in almost every case where I've
discussed an 'eval' here, I've been shown that it isn't really needed.
In this case the expansion seems so trivial that I'm puzzled. If
'level' were some other switch that didn't require a space in it ('tree'
demands a space between the 'L' and the number) then it works without
eval, but what's the issue? The '2' is there, why does 'tree' not see
it? Is this one of those invisible bogeys? Something about argument
counts or such? But quoting didn't change the error message.
[-- Attachment #2: Type: text/html, Size: 1224 bytes --]
next reply other threads:[~2022-11-19 14:35 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-19 14:34 Ray Andrews [this message]
2022-11-19 14:43 ` Roman Perepelitsa
2022-11-19 17:02 ` Ray Andrews
2022-11-19 17:10 ` Roman Perepelitsa
2022-11-19 18:02 ` Clinton Bunch
2022-11-19 18:18 ` Roman Perepelitsa
2022-11-19 16:48 ` Stephane Chazelas
2022-11-19 19:12 ` Ray Andrews
2022-11-19 19:50 ` Lawrence Velázquez
2022-11-19 22:21 ` Ray Andrews
2022-11-20 8:55 ` Stephane Chazelas
2022-11-20 13:47 ` Ray Andrews
2022-11-20 15:08 ` Stephane Chazelas
2022-11-20 16:27 ` Ray Andrews
2022-11-20 20:16 ` Stephane Chazelas
2022-11-20 22:31 ` Bart Schaefer
2022-11-21 2:13 ` Ray Andrews
2022-11-20 22:47 ` Ray Andrews
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=d0ef2035-e8e9-00c5-7f53-b16609d96262@eastlink.ca \
--to=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).