zsh-users
 help / color / mirror / code / Atom feed
From: Sweth Chandramouli <sweth@gwu.edu>
To: zsh-users@sunsite.auc.dk
Subject: Re: cd directory completion?
Date: Mon, 23 Aug 1999 11:03:21 -0400	[thread overview]
Message-ID: <19990823110321.A1724@cj952583-b.alex1.va.home.com> (raw)
In-Reply-To: <19990823160716.M32224@hp.com>

On Mon, Aug 23, 1999 at 04:07:16PM +0200, Dominik Vogt wrote:
> 
> Looks pretty much like the stuff I use. In the end all compctl
> configs end up the same :-) But I wonder why you use whence
> and where at all (do you?). It's so much easier to just type
> 
>   # ls =filename
> 
> and hit TAB :-))

	yes, but that returns totally different information, especially in
zsh, where which and type are just cosmetic variants of whence--all three
thus go through the entire process of command lookup, including functions
and builtins.  the =<command> syntax just does alias expansion and 
executable searching via path, while (k/c)sh-style which just does executable
searching; these two also thus do not provide any information about whether 
some command is a function or a builtin, and don't expand aliases/functions/
builtins so that you can quickly see their definition without looking at
source files, etc.

	(i personally think the zsh versions of those commands should mirror 
the equivalent ksh tools in behaviour (it's sometimes very useful to only
do executable searching, for example), but since /bin/which and /bin/type
exist and act like the ksh versions, i've just aliased which and type to 
their executable versions.  (of course, then you have issues figuring out
just what `alias which=/bin/which ; alias which=$(whence -a which | head -1)' 
does, but that's what makes playing with your shell fun.))

	-- sweth.

-- 
Sweth Chandramouli ; <sweth@gwu.edu>
<a href="http://astaroth.nit.gwu.edu/resume/">Will Work For Food.</a>
<a href="http://astaroth.nit.gwu.edu/~sweth/disc.html">*</a>


  reply	other threads:[~1999-08-23 15:04 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1999-08-23 13:22 Dominik Vogt
1999-08-23 13:35 ` Andre Pang
1999-08-23 14:07   ` Dominik Vogt
1999-08-23 15:03     ` Sweth Chandramouli [this message]
1999-08-25 13:46       ` listing all executables matching 'foo' Sven Guckes
1999-08-25 14:22         ` Hubert Canon
1999-08-25 14:53           ` Sven Guckes
1999-08-25 14:59             ` Paul Lew
1999-08-26  3:59         ` James Cribb
1999-08-26 12:27           ` Sven Guckes
1999-08-26 16:24         ` Sweth Chandramouli
1999-08-25  4:32     ` cd directory completion? Bek Oberin
1999-08-23 13:26 Sven Wischnowsky
1999-08-23 14:03 ` Dominik Vogt
1999-08-23 14:09   ` Swen Thuemmler
1999-08-23 13:26 John Riddoch
1999-08-23 14:07 Sven Wischnowsky

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=19990823110321.A1724@cj952583-b.alex1.va.home.com \
    --to=sweth@gwu.edu \
    --cc=zsh-users@sunsite.auc.dk \
    /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).