RE: Omni-completion problems

2006-05-04 Thread Bram Moolenaar
Robert Webb srote: > > You wouldn't type these things, they would be in a script. There it's > > not difficult to check for the existence of t:tabName. > > > >:set guitablabel=%{MyTabName()} > >func MyTabName() > > if exists('t:tabName') > > return t:tabName > > endi

RE: Omni-completion problems

2006-05-04 Thread Robert Webb
Bram, > You wouldn't type these things, they would be in a script. There it's > not difficult to check for the existence of t:tabName. > >:set guitablabel=%{MyTabName()} >func MyTabName() > if exists('t:tabName') > return t:tabName > endif > return '' >endfunc Bu

RE: Omni-completion problems

2006-05-04 Thread Bram Moolenaar
Robert Webb wrote: > > > > Another issue: it's a bit disconcerting that during insert-mode > > > > completion the cursor goes to the end of the line rather than > > > > staying in correct cursor position. I am talking about before the > > > > menu appears and millions of file names are speeding

RE: Omni-completion problems

2006-05-04 Thread Bram Moolenaar
Robert Webb wrote: > > > The example below is quite long, but I think it all comes down to > > > the "bunload" command. > > > > Vim never writes unless you tell it to. You must have an > > autocommand that does this or the 'autowrite' option is on. > > I have 'autowrite' set, but didn't expect

RE: Omni-completion problems

2006-05-04 Thread Robert Webb
> > > Another issue: it's a bit disconcerting that during insert-mode > > > completion the cursor goes to the end of the line rather than > > > staying in correct cursor position. I am talking about before the > > > menu appears and millions of file names are speeding past on the > > > status line

RE: Omni-completion problems

2006-05-03 Thread Robert Webb
Bram, > > The example below is quite long, but I think it all comes down to > > the "bunload" command. > > Vim never writes unless you tell it to. You must have an > autocommand that does this or the 'autowrite' option is on. I have 'autowrite' set, but didn't expect it to apply to :bunload. Tu

RE: Omni-completion problems

2006-05-03 Thread Robert Webb
> My 2 cents - I highly dislike the "C-p/C-n use omnicompletion" > thing. I was suggesting it as an option in 'complete', probably not present by default. > The argument "I don't want to think about the completion I want" is > moot. If you're writing something that requires omni-completion, > yo

Re: Omni-completion problems

2006-05-03 Thread Aaron Griffin
My 2 cents - I highly dislike the "C-p/C-n use omnicompletion" thing. When I hit C-p or C-n I *know* that I am using standard vim completion, and that's what I want. Just like C-x,C-f or C-x,C-o. I know exactly what I'm trying to complete. The argument "I don't want to think about the completi

Re: Omni-completion problems

2006-05-03 Thread Bram Moolenaar
Matt Mzyzik wrote: > > > (5) > > > Finally, when a completion was found, a new window appeared above my > > > current one titled "[Scratch] [Preview]". It has some info about the > > > match, but why is it there? The window also stays around after I've > > > chosen a match and moved on. It cer

RE: Omni-completion problems

2006-05-03 Thread Bram Moolenaar
Robert Webb wrote: > > > Five issues with omni-completion. > > > > > > (1) How about adding an option to 'complete' to use omni-search? > > > That way ^P and ^N can be used for everything. If omni worked > > > well, then I'd probably put it first in the list, even before ".". > > > > Unfortuna

RE: Omni-completion problems

2006-05-03 Thread Robert Webb
> > Another issue: it's a bit disconcerting that during insert-mode > > completion the cursor goes to the end of the line rather than > > staying in correct cursor position. I am talking about before the > > menu appears and millions of file names are speeding past on the > > status line. I'm usi

Re: Omni-completion problems

2006-05-03 Thread mzyzik
> > (5) > > Finally, when a completion was found, a new window appeared above my > > current one titled "[Scratch] [Preview]". It has some info about the > > match, but why is it there? The window also stays around after I've > > chosen a match and moved on. It certainly shouldn't stay around >

Re: Omni-completion problems

2006-05-03 Thread Bram Moolenaar
Robert Webb wrote: > Five issues with omni-completion. > > (1) > How about adding an option to 'complete' to use omni-search? > That way ^P and ^N can be used for everything. If omni worked well, > then I'd probably put it first in the list, even before ".". Unfortunately that's very complicat

Re : Omni-completion problems

2006-05-03 Thread NEANG Vissale
For omni-completion on c++ files you can use the script cppomnicomplete.vim at http://www.vim.org/scripts/script.php?script_id=1520, it's not finished yet but I think you can work with it. To remove the preview window you can set completeopt-=preview --- Message d'origine --- > De : Robert Webb