Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > gnu.bash.bug > #14131
| From | Chet Ramey <chet.ramey@case.edu> |
|---|---|
| Newsgroups | gnu.bash.bug |
| Subject | Re: [PATCH] Add nofirstword completion option |
| Date | 2018-05-23 09:15 -0400 |
| Message-ID | <mailman.325.1527081344.1292.bug-bash@gnu.org> (permalink) |
| References | <20180518110611.5099-1-bluca@debian.org> <96bcb197-40d1-aac8-c214-c513a6db805d@case.edu> <1527068652.6997.5.camel@debian.org> |
[Multipart message — attachments visible in raw view] - view raw
On 5/23/18 5:44 AM, Luca Boccassi wrote: > So by that, do you mean that it's possible to stop autocompleting to > files/dirs/binaries just using a programmable completion script? Or did > I misunderstand? Apologies if that's the case. > > Right now we do have completion scripts to implement the help text for > the commands (and for the empty set, which displays a general help with > a summary), what's missing is stopping files/dirs/binaries completion > for the first word, so that exclusively the commands are shown. Exactly. What you want, I gather, is a way to restrict completions on the command word to the small set of router commands valid in whichever mode the console happens to be. Programmable completion provides a mechanism to do that, but there is a missing piece of functionality that would allow it to work on the command word. That's the change I would prefer to see. Chet -- ``The lyf so short, the craft so long to lerne.'' - Chaucer ``Ars longa, vita brevis'' - Hippocrates Chet Ramey, UTech, CWRU chet@case.edu http://tiswww.cwru.edu/~chet/
Back to gnu.bash.bug | Previous | Next | Find similar | Unroll thread
Re: [PATCH] Add nofirstword completion option Chet Ramey <chet.ramey@case.edu> - 2018-05-23 09:15 -0400
csiph-web