From: Roman Perepelitsa <roman.perepelitsa@gmail.com>
To: Ray Andrews <rayandrews@eastlink.ca>
Cc: Zsh Users <zsh-users@zsh.org>
Subject: Re: permission denied
Date: Mon, 17 Apr 2023 21:07:32 +0200 [thread overview]
Message-ID: <CAN=4vMqwc8-LFr4ZAh9Mi6RtWNdG+21_AVbfsXFP-_muw3O6EQ@mail.gmail.com> (raw)
In-Reply-To: <5e16ada3-6968-78e9-7347-44b6181c29b1@eastlink.ca>
> On Mon, Apr 17, 2023 at 8:46 PM Ray Andrews <rayandrews@eastlink.ca> wrote:
>
> So, now having my 'chain' variable and experimenting with using it as a
> command, I run into this problem with any of my functions, like 'l' here:
>
> % chain=( ls ); $chain
>
> ... OK as expected
>
> % chain=( l ); $chain
>
> zsh: permission denied: l
>
> % chain=( l ); eval $chain
>
> ... works fine.
>
> It seems strange that a perfectly usable function throws 'permission
> denied' used that way. IIRC there are times when that message is
> misleading, it's not really a permissions issue but something else. I
> vaguely recall crashing into this before but I can't remember what the
> real reason was. And why does 'eval' fix it?
Run `which l` and have your question answered.
Roman.
next prev parent reply other threads:[~2023-04-17 19:08 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-17 18:34 Ray Andrews
2023-04-17 19:07 ` Roman Perepelitsa [this message]
2023-04-17 20:41 ` Ray Andrews
2023-04-17 21:52 ` Bart Schaefer
2023-04-17 22:44 ` Ray Andrews
2023-04-18 2:41 ` Bart Schaefer
2023-04-18 3:35 ` Ray Andrews
2023-04-20 21:35 ` Ray Andrews
2023-04-20 21:47 ` Roman Perepelitsa
2023-04-20 22:09 ` Ray Andrews
2023-04-20 22:13 ` Bart Schaefer
2023-04-20 22:47 ` Ray Andrews
2023-04-21 3:12 ` Bart Schaefer
2023-04-21 13:33 ` Ray Andrews
2023-04-21 14:12 ` Peter Stephenson
2023-04-21 14:42 ` Ray Andrews
2023-04-21 21:58 ` Bart Schaefer
2023-04-22 0:56 ` Ray Andrews
2023-04-20 22:17 ` Roman Perepelitsa
-- strict thread matches above, loose matches on Subject: below --
2020-12-21 23:01 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='CAN=4vMqwc8-LFr4ZAh9Mi6RtWNdG+21_AVbfsXFP-_muw3O6EQ@mail.gmail.com' \
--to=roman.perepelitsa@gmail.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).