[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [PATCH] Add nofirstword completion option

From: Luca Boccassi
Subject: Re: [PATCH] Add nofirstword completion option
Date: Wed, 23 May 2018 10:44:12 +0100

On Sun, 2018-05-20 at 15:34 -0400, Chet Ramey wrote:
> On 5/18/18 7:06 AM, Luca Boccassi wrote:
> > Network operating systems traditionally have provided a command
> > line interface with "operation mode" and "configuration mode", with
> > different auto-completion behaviour - specifically, with a small
> > set
> > of supported commands that are printed using the auto-completion
> > shortcut key, depending on the mode.
> > In order to be able to implement such modes using Bash, Linux and
> > Free
> > Software, it's necessary to be able to optionally disable
> > auto-completion on the first word, so that the relevant help text
> > (depending on the mode) can be printed on the console instead.
> > Add and document a nofirstword completion option to implement this
> > feature.
> I don't like this, and don't see it as having much general use. If
> this
> functionality is required, I would rather see it implemented as a
> programmable completion mode (and a new option to `complete') that
> can be
> used to auto-complete command names.
> Chet

Hello Chet,

Thanks for your feedback!

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.

Kind regards,
Luca Boccassi

Attachment: signature.asc
Description: This is a digitally signed message part

reply via email to

[Prev in Thread] Current Thread [Next in Thread]