Re: Completing the command line using 'all' as the option to command.complete

On Thu, 31 Jul 2008 15:14:00 -0500
Adam Krolnik <adam.krolnik@xxxxxxxxxxxxxxx> wrote:

> It appears that configuring the key binding 'Tab' for the command line 
> to complete 'all' (types) does not complete files.
> 
> Strangely, it will complete executable files (rwx...) and list them (as 
> if they are a directory.)
> But files without a execute permission do not get completed. If I set 
> the complete option to 'files'
> it will complete them though.
> 
> I have not tried completing the mount type.
Adam,

I'm not sure exactly what you did, but it's intended to work like this:

comm<Tab> (i.e. no whitespace) is expected to be completion of a command name, 
and will retrieve executable files only.

command <Tab> is essentially useless but will work like the previous case

command arg<Tab> will complete arg taking full account of the config-specified 
completion argument, defaulting to 'all' if there's no such argument.

command arg <Tab> is essentially useless but will work like the previous case.

However when doing 'all' and match(es) exist in a specific category e.g. mounts 
or dirs or files, it stops scanning (no more categories). I'm not sure why this 
behaviour was implemented. Need to think about it.

Regards
Tom


-- 
Users can unsubscribe from the list by sending email to 
emelfm2-request@xxxxxxxxxxxxx with 'unsubscribe' in the subject field or by 
logging into the web interface.

Other related posts: