Tony Mechelynck wrote: > Mikolaj Machowski wrote: >> Dnia Thursday 17 of January 2008, Bram Moolenaar napisał: >>> Hello Vim users, >>> >>> I have added two items to vote on: >>> >>> - add collaborative editing: changes made to a file show up in another >>> Vim in a second >>> - add flexible tab stops, can be used for tables >>> >> I'd like to see something simpler(?): better command line completion of >> built-in commands. You can script user defined commands as you wish to >> perform all magic but completion of many built-in commands is really >> dumb. >> >> For example I am working lately with "Tab Separated Values". When I try >> to insert Tab into regular expression of vimgrep Vim constantly tries to >> resolve it to file name. I have to resort to <C-V><C-I>. >> >> m. > > To search for a hard tab, use \t in the pattern. > > Currently, :command can have at most one -complete= parameter. I suspect this > unicity also applies to builtin commands.
And maybe I'm just dumb, but isn't auto-complete on a regular expression a bit of a silly idea?! If it's so obvious from what you've already typed what it should be completed to, you probably already have enough typed there to do the search... Inserting <Tab> as ^I isn't auto-complete, but lack thereof, and \t, as Tony points out, is a better way of doing that anyway, even though it involves pressing an extra key. Another way of getting around it would be to use a different key to <Tab> for your autocomplete (if there's a key you need to enter less often)! Ben. Send instant messages to your online friends http://au.messenger.yahoo.com --~--~---------~--~----~------------~-------~--~----~ You received this message from the "vim_dev" maillist. For more information, visit http://www.vim.org/maillist.php -~----------~----~----~----~------~----~------~--~---
