On Fri, 21 May 2010, Peng Yu wrote:
> On Fri, May 21, 2010 at 11:19 AM, Marc Herbert <Marc.Herbert@gmail.com> wrote:
> > Le 21/05/2010 16:25, Peng Yu a ?crit :
> >> When I type something after 'which', something means a command.
> >> However, bash doesn't do command completion for the argument after
> >> 'which'. Is there a way to configure bash behave depending on the
> >> context (in this case, do autocomplete after 'which')?
> >
> > By the way it is better to use "type" instead of "which". "which" is
> > often misleading, compare for instance:
> >
> > type pwd
> > which pwd
> >
> > "which" is misleading in many other cases.
>
> Since pwd is a shell command, when /bin/pwd is actually used? In
> shells that don't have built-in pwd?
And all POSIX shells have the $PWD variable.
--
Chris F.A. Johnson, <http://cfajohnson.com>
Author:
Pro Bash Programming: Scripting the GNU/Linux Shell (2009, Apress)
Shell Scripting Recipes: A Problem-Solution Approach (2005, Apress)