2008/6/30 Marcel Boon <marcelsp...@gmail.com>:
> Oh.. I just started this, but when it's all finsihed I probably easily can
> add configurations for other editors. I think it would be something like
> Slick Ultra Multi Vim Plus, for easy switching to vim. Delivered with
> several congurations. ;)
I know the problem, that is sometimes hard for newbies to find
into Vim. However, I think that there is a better solution than
yours: If you want an editor to behave like MultiEdit, it will
be wise to use MultiEdit. If you want an editor to behave like
Notepad, it will be wiser to use Notepad. In my humble opinion,
it is not the best way to make Vim a completely different
editor than it is meant to be.
Instead you can try mswin.vim (if you are using Windows), which
is much easier to start with. This isn't doing things completely
in the Vim way, but it is very near to it and maybe you won't
stop using Vim so quickly, if there is more you are familiar
with. However, finally one should arrive at using Vim the Vim
way which is the most efficient way to use Vim. But we should
not forget, that due to the flexibility of Vim, there are many
ways using Vim the Vim way.
This is at least the way I found into Vim. Others may have found
into Vim in a completely different way. Once I really disliked
(or better: hated) Vi and thus this way (and realizing Vim's
mighty regular expressions) was necessary for me to become a big
fan of this greatest of all possible editors in the multiverse.
No. I don't want it to behave like MultiEdit, I like it to be easy for
MultiEdit users. A big difference.
So keymappings are allowed. Disabling modes, like cream does, not. I'm
used to MultiEdit, but there is no Linux version, although they
promised it for years. So I searched for an other editor, Vim seems my
best option. And I know it's a completely other editor, but I think it
can be more newbiefriendly than it is without doing a completely
facelift like Cream, so without really changing the way it works.
I want to make a configuration that functions as a guide for a
MultiEdit user saying."Hey you,I recognise the keystroke, you
Multiedituser, but ... read on... actually this is the way to do it in vim."
For me a learning process and the result is a configuration that is
very friendly towards frustrated Multiedit users.
This was all an introduction to my question: what is the best way to
show the message?
Can it be done in a neat way?
You can remove "preview" from 'completeopt' so it never pops up the
window. If you want it to pop up, but go away after you finish
entering text, you could probably do something like:
autocmd InsertLeave * pclose
That's what I plan to do, but I haven't played with this yet, because
for some reason I can't get the preview window to pop up at all!
This surely is nice. It was more or less what I had in mind woth the
exception that it would be great that if the help is shown it's not in
a new window but shown as layover, like the dropdown omnicomplete. So
it's drawn over the current screen.
But I don't think that is possible.
Your solution is very nice and I will surely use it. Thanks.