From: Bart Schaefer <schaefer@brasslantern.com>
To: zsh-workers@sunsite.dk
Subject: Re: Bug#517008: alias not expanded with zsh -c
Date: Thu, 26 Mar 2009 08:12:59 -0700 [thread overview]
Message-ID: <090326081259.ZM9239@torch.brasslantern.com> (raw)
In-Reply-To: <20090326095029.52a8ce33@news01>
On Mar 26, 9:50am, Peter Stephenson wrote:
} Subject: Re: Bug#517008: alias not expanded with zsh -c
}
} On Wed, 25 Mar 2009 17:14:31 -0700
} Bart Schaefer <schaefer@brasslantern.com> wrote:
} > It just seems to me that we're potentially penalizing a script that
} > does not use aliases in the can't-open-tempfile case in order to
} > support a script that does not use aliases.
In case it wasn't obvious, there's an extra "not" in that last line.
} > Given potential security problems with using tempfiles and the
} > likelyhood of a script using an alias vs. the likelyhood of file
} > creation failing, which case ought we be catering too?
Good grief, I was having a bad typing day yesterday. Must be because
I was home sick at the time ...
} From what I've heard, it doesn't sound like it's worth more than a
} warning.
}
} +other piece of shell code evaluated as one unit. Note this may
} +cause differences from other shells even when the option is in
} +effect. For example, when running a command with `tt(zsh -c)' the
} +entire command argument is parsed in one go, so aliases defined within
Is it obvious enough that "evaluated as one unit" and "parsed in one go"
mean the same thing? And should that be tt(sh -c) rather than zsh?
next prev parent reply other threads:[~2009-03-26 15:14 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20090225022850.GA4841@vin.lip.ens-lyon.fr>
2009-03-25 14:54 ` Clint Adams
2009-03-25 16:30 ` Peter Stephenson
2009-03-25 17:25 ` Peter Stephenson
2009-03-25 18:11 ` Bart Schaefer
2009-03-25 18:20 ` Peter Stephenson
2009-03-26 0:14 ` Bart Schaefer
2009-03-26 9:50 ` Peter Stephenson
2009-03-26 15:12 ` Bart Schaefer [this message]
2009-03-26 15:18 ` Peter Stephenson
2009-03-25 23:35 ` Vincent Lefevre
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=090326081259.ZM9239@torch.brasslantern.com \
--to=schaefer@brasslantern.com \
--cc=zsh-workers@sunsite.dk \
/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).