Zsh Mailing List Archive
Messages sorted by:
Reverse Date,
Date,
Thread,
Author
Re: bash like tab tab 's
- X-seq: zsh-users 385
- From: "Bart Schaefer" <schaefer@xxxxxxxxxxxxxxxxxxxxxxx>
- To: Duncan Sargeant <dunc@xxxxxxxxxxxxxxxxxxx>
- Subject: Re: bash like tab tab 's
- Date: Tue, 27 Aug 1996 02:48:31 -0700
- Cc: dunc@xxxxxxxxxxxxxxxxx, zsh-users@xxxxxxxxxxxxxxx
- In-reply-to: Duncan Sargeant <dunc@xxxxxxxxxxxxxxxxxxx> "Re: bash like tab tab 's" (Aug 27, 5:31pm)
- References: <199608270931.RAA31201@xxxxxxxxxxxxxxxxxxx>
- Reply-to: schaefer@xxxxxxx
On Aug 27, 5:31pm, Duncan Sargeant wrote:
} Subject: Re: bash like tab tab 's
}
} > } I noticed bash's tab tab feature, where pressing tab once
} > } will try to complete a word as per usual, but if it can't, pressing it a
} > } second time will give a list of commands.
} >
} > I think you want
} >
} > setopt autolist listambiguous
}
} that's does a list after the first TAB. I was interested in having it
} complete as far as possible first, beep, then (after second TAB) list.
`setopt autolist` lists after the first tab on any ambiguous competion.
If you add `setopt listambiguous` then it completes as far as possible
and lists only if "as far as possible" means "no further".
This is as close as you can get; it saves you having to type the second
tab when the completion is immediately ambiguous, which is (partly) why
it works this way.
--
Bart Schaefer Brass Lantern Enterprises
http://www.well.com/user/barts http://www.nbn.com/people/lantern
New male in /home/schaefer:
>N 2 Justin William Schaefer Sat May 11 03:43 53/4040 "Happy Birthday"
Messages sorted by:
Reverse Date,
Date,
Thread,
Author