- Jun
- 1,092
- 48
Please change the behavior of filename completion customization so that adding any customization no longer removes all the default settings, at least as an option. The way things work now, once one adds a definition, such as for an alias, all the defaults are gone. So one faces an all-or-nothing situation.
For now, I have gone through the help and captured all the documented default settings and added them to my custom settings.
By the way, in the help for customization, the following statement appears (emphasis added):
That's how I would like it to work, but it currently overrides the settings for all commands.
Alternatively, if the coding for my request would be too difficult, at least provide a list (or, even better, a variable such as _filecompletion) that contains all the default definitions.
I just experimented with defining the completion for a command twice in the filecompletion environment variable, and it appears that a second definition is ignored. So if you provided a variable such as _filecompletion with the default settings, one could define a custom version as follows:
Settings for new commands would be added, and settings for commands already covered would take precedence over the default.
For now, I have gone through the help and captured all the documented default settings and added them to my custom settings.
By the way, in the help for customization, the following statement appears (emphasis added):
Setting options in OPTION / Filename Completion, or with the FILECOMPLETION environment variable, will override the default filename completion settings such as "complete hidden files / directories" options for that command.
That's how I would like it to work, but it currently overrides the settings for all commands.
Alternatively, if the coding for my request would be too difficult, at least provide a list (or, even better, a variable such as _filecompletion) that contains all the default definitions.
I just experimented with defining the completion for a command twice in the filecompletion environment variable, and it appears that a second definition is ignored. So if you provided a variable such as _filecompletion with the default settings, one could define a custom version as follows:
Code:
set filecompletion=[my settings];%_filecompletionSettings for new commands would be added, and settings for commands already covered would take precedence over the default.
