On 5/6/06, Mikolaj Machowski <[EMAIL PROTECTED]> wrote:
Dnia sobota, 6 maja 2006 00:01, Eric Arnold napisał:
> On 5/5/06, Mikolaj Machowski <[EMAIL PROTECTED]> wrote:
> > Dnia piątek, 5 maja 2006 14:35, Eric Arnold napisał:
> > > I think vim-dev@vim.org is probably a place to start...
> > >
> > > I've been hacking the statusline for a long time to do various
> > > things a keystroke at a time. I've finally got a compiling env, so
> > > I decided to take a stab a creating a key-event.
> >
> > Very, very, very good thing. It makes possible high-level of
> > automation for some things - eg. map Space and pry it will not
> > interfere with some scripts.
> >
> > Personally I'd like to see separation for Insert and Normal mode
> > (GetChar, GetCharI?).
>
> I think 'mode()' will probably suffice for this?
I've had bad experiences in the past with mode(). But maybe they were
Have a look at the test script in the new version I'll post after this.
only my things - I didn't really have time to test various possibilities
of v:getchar. BTW - general rule for v:variables is they are read-only.
It's a common rule, but there are several which are already
read/write. It's the only clean way I can think of to deliver
information back into a C function which has no Vim script equiv.
Would be good thing to keep consistency.
I knot it is late but this would be really good addition to Vim7. For
example it could automatically open omnicompletion menu after some
letters and in desired context - no need to press <C-X><C-O> (or
equivalent)! Possibilities are endless.
m.
Ya. I think it would be cool to have it released with Vim7 to be able
to start writing scripts with it that will be publicly usable.
I'm hoping I've isolated the changes enough that it will be
acceptable. I think it's pretty solid, though there are some weird
side cases, mostly dealing with re-calling back into 'getchar()'.
