zsh-workers
 help / color / mirror / code / Atom feed
From: Peter Stephenson <p.stephenson@samsung.com>
To: Klaus Alexander Seistrup <klaus@seistrup.dk>,
	Zsh Workers <zsh-workers@zsh.org>
Subject: Re: BUG: Shell builtin `which` prints non-existent commands to stdout
Date: Mon, 24 Sep 2018 11:22:18 +0100	[thread overview]
Message-ID: <20180924102219eucas1p2469f827265423a2f3b5e7d98fc08412e~XTuQ1aIyy2293622936eucas1p2L@eucas1p2.samsung.com> (raw)
In-Reply-To: <20180924080031.ee7lqmthxpmvqaal@klaus.seistrup.dk>

On Mon, 24 Sep 2018 10:00:31 +0200
Klaus Alexander Seistrup <klaus@seistrup.dk> wrote:
> TL;DR: When `which` does not find a command it prints the error to 
> standard output instead of standard error. Exit code is set correctly, 
> though, and error messages about ‘bad options’ are sent to standard 
> error as expected.

This is not a bug and has been discussed numerous times, e.g. the thread
that starts at.

http://www.zsh.org/mla/workers//2015/msg02253.html

(official zsh-workers message number 36330).

We definitely don't wish to change this now.

pws


  reply	other threads:[~2018-09-24 10:32 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CGME20180924080113epcas4p4f8f89aa03a2cebc5030fd45dca0f6e84@epcas4p4.samsung.com>
2018-09-24  8:00 ` Klaus Alexander Seistrup
2018-09-24 10:22   ` Peter Stephenson [this message]
2018-09-24 12:29     ` Klaus Alexander Seistrup
2018-09-24 12:51       ` Peter Stephenson
2018-09-24 13:22         ` [PATCH] zshbuiltins(1): Document 'which''s "not found is not an error" behaviour Daniel Shahaf
2018-09-24 22:18         ` BUG: Shell builtin `which` prints non-existent commands to stdout Stephane Chazelas
2018-09-25  7:56           ` Stephane Chazelas
2018-09-24 22:32         ` Stephane Chazelas
2018-09-25  9:10           ` Peter Stephenson
     [not found]   ` <20180924112218.7bac7f2c@camnpupstephen.cam.scsc.local>
2018-09-24 10:25     ` 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='20180924102219eucas1p2469f827265423a2f3b5e7d98fc08412e~XTuQ1aIyy2293622936eucas1p2L@eucas1p2.samsung.com' \
    --to=p.stephenson@samsung.com \
    --cc=klaus@seistrup.dk \
    --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).