From: Peter Stephenson <p.w.stephenson@ntlworld.com>
To: zsh-workers@zsh.org
Subject: Re: Function code breaking out of if then ...fi
Date: Sat, 10 Nov 2012 21:23:30 +0000 [thread overview]
Message-ID: <20121110212330.0d74f97f@pws-pc.ntlworld.com> (raw)
In-Reply-To: <121109171319.ZM4069@torch.brasslantern.com>
On Fri, 09 Nov 2012 17:13:19 -0800
Bart Schaefer <schaefer@brasslantern.com> wrote:
> I believe I know the reason for this behavior, and perhaps it points to a
> bug:
>
> When reading a startup file such as .zshrc, there is an intent to avoid
> skipping the entire configuration just because of one erroneous command
> somewhere in the middle.
I've a vague memory of this too, but evidence suggests it's not showing
CONTINUE_ON_ERROR behaviour (this is before my patch):
% cat ~/tmp/zdotdir/.zshrc
print First line
echo *fumblewumble*
print Second line
% ZDOTDIR=~/tmp/zdotdir zsh
First line
/home/pws/tmp/zdotdir/.zshrc:2: no matches found: *fumblewumble*
% exit # <- this is the prompt inside the new shell
% zsh ~/tmp/zdotdir/.zshrc
First line
/home/pws/tmp/zdotdir/.zshrc:2: no matches found: *fumblewumble*
Second line
So if that was the intention, we've already messed it up. A bit of
historical research might be interesting.
--
Peter Stephenson <p.w.stephenson@ntlworld.com>
Web page now at http://homepage.ntlworld.com/p.w.stephenson/
next prev parent reply other threads:[~2012-11-10 21:23 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-02 9:09 Michal Maruska
2012-11-02 21:39 ` Bart Schaefer
2012-11-05 8:22 ` Han Pingtian
2012-11-05 9:31 ` Han Pingtian
2012-11-05 14:29 ` Peter Stephenson
2012-11-05 14:55 ` Peter Stephenson
2012-11-05 16:08 ` Peter Stephenson
2012-11-06 6:47 ` Han Pingtian
2012-11-09 22:52 ` Peter Stephenson
2012-11-10 1:13 ` Bart Schaefer
2012-11-10 21:23 ` Peter Stephenson [this message]
2012-11-12 10:24 ` Peter Stephenson
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=20121110212330.0d74f97f@pws-pc.ntlworld.com \
--to=p.w.stephenson@ntlworld.com \
--cc=zsh-workers@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).