From: Peter Stephenson <p.w.stephenson@ntlworld.com>
To: zsh workers <zsh-workers@zsh.org>
Subject: Re: BUG: failure in "vcs_info prompt" aborts precmd function
Date: Sun, 23 Nov 2014 19:02:01 +0000 [thread overview]
Message-ID: <20141123190201.37536a9f@pws-pc.ntlworld.com> (raw)
In-Reply-To: <141122144400.ZM15674@torch.brasslantern.com>
On Sat, 22 Nov 2014 14:44:00 -0800
Bart Schaefer <schaefer@brasslantern.com> wrote:
> On the other hand, I don't know WHY $(<notafile) was made a fatal error.
Looks like most redirection errors are fatal, so from that point of view
this would be consistent. However, from the other point of view,
$(<...) might be thought to be faking up a subshell, in which case it
probably shouldn't be. I suppose that just never got discussed before.
The principle of least surprise perhaps says it doesn't look like it should
be fatal, therefore it shouldn't be.
pws
next prev parent reply other threads:[~2014-11-23 19:07 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-22 17:13 Daniel Hahler
2014-11-22 17:20 ` [PATCH] vcs_info: test -f .git/rebase-merge/done before reading it Daniel Hahler
2014-11-22 17:51 ` BUG: failure in "vcs_info prompt" aborts precmd function Mikael Magnusson
2014-11-22 18:01 ` Daniel Hahler
2014-11-22 22:20 ` Mikael Magnusson
2014-11-22 22:44 ` Bart Schaefer
2014-11-23 19:02 ` Peter Stephenson [this message]
2014-11-23 19:38 ` Bart Schaefer
2014-11-23 20:04 ` Peter Stephenson
2014-11-23 15:58 ` Daniel Hahler
2014-11-23 18:08 ` Mikael Magnusson
2014-11-23 19:57 ` TRY_BLOCK_ERROR and exit status Bart Schaefer
2014-11-24 10:11 ` Peter Stephenson
2014-11-25 8:01 ` Bart Schaefer
2014-11-25 9:18 ` Peter Stephenson
2014-11-23 18:13 ` BUG: failure in "vcs_info prompt" aborts precmd function Bart Schaefer
2014-11-23 18:52 ` Mikael Magnusson
2014-11-23 19:47 ` Bart Schaefer
2014-11-23 22:03 ` Oliver Kiddle
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=20141123190201.37536a9f@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).