Re: Command-line completion

[prev] [thread] [next] [lurker] [Date index for 2005/02/01]

From: Jason Diamond
Subject: Re: Command-line completion
Date: 17:48 on 01 Feb 2005
Hakim wrote:

>  In Windows, command line completion has the lovely feature of
>  expanding files prepended with a dot before the actual filename. So
>  if while I'm editing foo.pl, I type
>
>  perl f<TAB>
>
>  it gets expanded to
>
>  perl .foo.pl.swp
>
>  Obviously, this feature is great for people who like to run Vim swap
>  files.

You can configure Vim to put all of your swap files in a fixed location 
instead of the current directory.

:help 'directory'

>  In case I'm not being even-handed in my hate, I also hate that bash
>  doesn't expand a file when there are alternatives. Sure, I could ls
>  and then work out which characters to type to disambiguate, but why
>  can't I just repeatedly press <TAB> like a simpleton and have it do
>  the right thing? (I guess this being Unix there will be some simple
>  config change to make the hate go away though).

Here's the .inputrc file I use to make bash more Windows-like:

 >>>>
set completion-ignore-case On

TAB: menu-complete

# Shift-Tab reverse completes.
"\e[Z": "\M--1\t"

# Two escapes clear command line.
"\e\e": "\C-a\C-k"
<<<<

It's hard to hate configurable software.

-- Jason

Generated at 23:00 on 03 Feb 2005 by mariachi 0.52