public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Jeff <for.listmail@verizon.net>
To: cygwin@cygwin.com
Subject: Re: missing 'which' documentation
Date: Thu, 13 Dec 2007 17:03:00 -0000	[thread overview]
Message-ID: <TBVYHx3lQ3ZK092yn@verizon.net> (raw)
In-Reply-To: <20071213082429.GA4670@calimero.vinschen.de>

As seen from lists.cygwin, on
Thu, 13 Dec 2007 09:24:29 +0100,
Corinna Vinschen <corinna-cygwin@cygwin.com> wrote:

>On Dec 12 22:55, Lee D. Rothstein wrote:
>> Does anybody know or care that there is an option --
>> '-a' -- for 'which' -- that is not documented on
>> Cygwin. That is, there is no internal help, and there
>> is no 'man' or 'info' page provided by Cygwin install.
>> If anybody wants this, I will find or create the 'man'
>> page and make it cover '-a', and then do *what* with
>> it? Pointers appreciated!
>
>Cygwin's which is quite an old one written by me.  The best way to move
>forward would probably be to remove it from the Cygwin distro in favor
>of the which used in several (all?) Linux distros:

I recall (perhaps even correctly :) ) that SunOS had a "where" command
with the functionality of your 'which -a'. The idea was that "where"
would show you all scripts and executables of a given name in your
command path (ie. "where" they are), while "which" would tell you
*which* one of them would execute at the shell prompt. So unusual, to
see a pair of utilities whose names were so nearly self-explanatory. :)
Is the Linux "which" like yours (ie. 'which -a' == SunOS 'where')?

-- 
"Sorry, my life is still in beta, and nowhere near stable enough for a
release."

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

  reply	other threads:[~2007-12-13 17:03 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-12-13  3:55 Lee D. Rothstein
2007-12-13  7:34 ` Marco Atzeri
2007-12-13 15:03   ` Jeff
2007-12-13 15:47     ` Marco Atzeri
2007-12-13 18:38       ` Jeff
2007-12-13 23:50     ` Brian Dessent
2007-12-14 13:04       ` Jeff
2007-12-13  8:24 ` Corinna Vinschen
2007-12-13 17:03   ` Jeff [this message]
2007-12-13 17:17     ` Corinna Vinschen
2007-12-13 14:29 ` Frederich, Eric P21322
2007-12-23  1:55 ` phil curb

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=TBVYHx3lQ3ZK092yn@verizon.net \
    --to=for.listmail@verizon.net \
    --cc=cygwin@cygwin.com \
    /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.
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 read-only IMAP folder(s) and NNTP newsgroup(s).