From: Peter Stephenson <p.stephenson@samsung.com>
To: Zsh hackers list <zsh-workers@zsh.org>
Subject: Re: [patch] "which"-builtin writes diagnostics to stdout
Date: Tue, 01 Sep 2015 14:45:27 +0100 [thread overview]
Message-ID: <20150901144527.3ee45953@pwslap01u.europe.root.pri> (raw)
In-Reply-To: <CAH+w=7aNzRtsJcvGcfyYFPAiRtNY69imSN+oGrF7K7unD5aNcA@mail.gmail.com>
On Sat, 29 Aug 2015 22:15:38 -0700
Bart Schaefer <schaefer@brasslantern.com> wrote:
> On Sat, Aug 29, 2015 at 8:06 PM, Timo Buhrmester <fstd.lkml@gmail.com> wrote:
> > When invoking the `which` builtin for something that does not exist, like:
> >
> > | % which doesnotexist
> > | doesnotexist not found
> >
> > the "doesnotexist not found" message goes to standard output, rather than standard error.
>
> Believe it or not, this is intentional, because the original "which"
> builtin from csh does that. Try it in tcsh, for example.
This is an obvious candidate for hiding behind one of the options like
CSH_JUNKIE_STUFF_THAT_NO_ONE_COULD_CONCEIVABLY_WANT_ANY_MORE on the
grounds of consistency --- it's hard to see how sending the error to
stder could make anything other than a script/function deliberately set
up to expect csh output any more confused --- though I'm not that set on
the option name.
pws
next prev parent reply other threads:[~2015-09-01 13:55 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-30 3:06 Timo Buhrmester
2015-08-30 5:15 ` Bart Schaefer
2015-08-30 5:26 ` Timo Buhrmester
2015-09-01 6:04 ` Bart Schaefer
2015-09-01 6:12 ` Mikael Magnusson
2015-09-01 23:16 ` Bart Schaefer
2015-09-02 8:53 ` Peter Stephenson
2015-09-02 13:48 ` Vincent Lefevre
2015-09-01 13:14 ` Timo Buhrmester
2015-09-01 13:45 ` Peter Stephenson [this message]
2015-09-01 23:10 ` Bart Schaefer
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=20150901144527.3ee45953@pwslap01u.europe.root.pri \
--to=p.stephenson@samsung.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).