On Jan 20, 12:02 am, Tony Mechelynck <[EMAIL PROTECTED]>
wrote:
> ap wrote:
> > On Jan 17, 10:07 pm, Mikolaj Machowski <[EMAIL PROTECTED]> wrote:
> [...]
> >> 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>.
>
> > I tend to agree, but would have argued the other way around.
> > Completing
> > with '^J' is useless in 99% of my standard use-cases. I believe,
> > ultimately
> > the completion should be configurable like for custom-commands. That
> > way everybody can have it the way he wants.
>
> [...]
>
> Do you mean ^J (newline or maybe null) or ^I (tab)?
>
> Even in a user command, the -complete= parameter (or its absence) is defined
> when the command is defined and cannot be altered later (other than by
> redefining the command). Now builtin ex-commands are defined in the C source
> and cannot be redefined.
>
That sounds like you don't like it, but is actually the best reason
for it.
What I have in mind, is the ability to use a wrapper function around
the
builtin command completion. 2 internal functions. First one returns
which kinds
vim would complete, second the (mostly) static wordlists with
typeinfo.
Then one could complete caseinsensitive filenames or add words from
the buffer in a :s command or be happy without '^I' popping up.
Note: Some custom cline completion is already possible via 'CTRL-\e'.
It's just an idea, i wouldn't die for it.
-ap
> Best regards,
> Tony.
> --
> hundred-and-one symptoms of being an internet addict:
> 245. You use Real Audio to listen to a radio station from a distant
> city rather than turn on your stereo system.
--~--~---------~--~----~------------~-------~--~----~
You received this message from the "vim_dev" maillist.
For more information, visit http://www.vim.org/maillist.php
-~----------~----~----~----~------~----~------~--~---
