From: Bart Schaefer <schaefer@brasslantern.com>
To: kynn@panix.com
Cc: zsh-users@sunsite.dk
Subject: Re: =nonexistent crashes scripts
Date: Wed, 24 Nov 2004 10:51:24 -0800 (PST) [thread overview]
Message-ID: <Pine.LNX.4.61.0411241046230.31945@toltec.zanshin.com> (raw)
In-Reply-To: <200411241832.iAOIW1408107@panix3.panix.com>
On Wed, 24 Nov 2004 kynn@panix.com wrote:
> This seems like a serious bug to me; it makes the =command facility all
> but useless. Is there any way around this?
It's not a bug, it's an intentional feature of file expansion. Try
"setopt nonomatch".
Or don't use file expansion. =command was really meant as a shortcut for
interactive command entry, not as a scripting tool. In a script you
should be using something like
FOO=$(whence -p nonexistent)
prev parent reply other threads:[~2004-11-24 18:52 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-24 18:32 kynn
2004-11-24 18:51 ` Bart Schaefer [this message]
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=Pine.LNX.4.61.0411241046230.31945@toltec.zanshin.com \
--to=schaefer@brasslantern.com \
--cc=kynn@panix.com \
--cc=zsh-users@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).