On 10/22/07, Bram Moolenaar <[EMAIL PROTECTED]> wrote: > > Yakov Lerner wrote: > > > Would you add to the todo list some way to lock the > > filename completion to the end of the filename ? Currently, the > > :e *a<Tab> > > automatically adds the * at the end. This shows not > > files endnig with 'a', but all files *containing* 'a' . This > > is by design. The consequence is that user cannot make the > > completion show files the ending with 'a', no ? > > > > Maybe some character can be defined that anchors the to the > > end of name and tells the completion mechanism not to add > > the trailing * ? For example, > > :e *a$<Tab> > > ? > > > > This affects usefulness of filename completion when > > directory contains very large number of files. > > You can at least match with the end of a word: > :e *a\><Tab> > > Somehow using a dollar doesn't work here, probably because of expanding > environment vars. We might not be able to change this without breaking > backwards compatiblity.
$$ maybe ? some sequence never used before ? This is completion-specific issue. In glob, the problem does not exist. Strangely, :e $<Tab> completes names of env.vars, but :e *a$<Tab> does not complete anything. Since <Tab> completions are not scriptable, backward-compatibility here is different maybe ? There are human habits of course. \> in filenames is weird. It works depending on current syntax which does not make much sense for filenames (For example, In ft=c, it matches before '.' and before '-' . In 'help' mode, it does not). Yakov --~--~---------~--~----~------------~-------~--~----~ You received this message from the "vim_dev" maillist. For more information, visit http://www.vim.org/maillist.php -~----------~----~----~----~------~----~------~--~---
