From: Timo Buhrmester <fstd.lkml@gmail.com>
To: Bart Schaefer <schaefer@brasslantern.com>
Cc: Zsh hackers list <zsh-workers@zsh.org>
Subject: Re: [patch] "which"-builtin writes diagnostics to stdout
Date: Tue, 1 Sep 2015 15:14:22 +0200 [thread overview]
Message-ID: <20150901131422.GA22568@frozen.localdomain> (raw)
In-Reply-To: <150831230431.ZM894@torch.brasslantern.com>
> } Out of curiosity, what reason would zsh (being more bourne-ish than
> } csh-ish, as far as I can tell) have to maintain this particular csh
> } glitch rather than fixing it?
>
> What makes you think it's a glitch?
>
> I.e., "not found" here is not an error message! It is the answer to the
> question you asked
It seems to me like a diagnostic message intended for human consumption, mainly because there's an infinite number of ways it could answer the same thing (``I can' find <xyz>'' and ``no such <xyz>'', etc). So unless on the other end of the pipeline you have a human, or a program that understands English, you'll have to deal with this as a special case. Heck, I could even have a file named ``foobar not found'' sitting around, making things worse. :)
I obviously can't argue with behavior of ancient shells, but IMO there is exactly one correct, unambiguous and machine-readable answer to the ``which'' question:
The empty answer.
> and you asked for the answer in csh format ("which" is "whence -c").
> If you don't want csh behavior, you should be using "whence" directly
> so that you can omit the "-c" option.
Okay, I didn't know about that.
Doesn't make my point less valid, but I'm glad there's a way out with `whence`. Thanks.
Timo
next prev parent reply other threads:[~2015-09-01 13:14 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 [this message]
2015-09-01 13:45 ` Peter Stephenson
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=20150901131422.GA22568@frozen.localdomain \
--to=fstd.lkml@gmail.com \
--cc=schaefer@brasslantern.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).