> >> plugin to do anything for me. Pretty sure also the problem is me.
> >> Something simple I'm overlooking.
> >
> > since I have also unsuccessfully tried to use orgmode in the past,
> > I installed it now and I get exactly the same behaviour as you,
> > i.e. the plugin does nothing. However, this is only true for
> > console vim, in gvim the mappings work. I don't know whether the
> > author tests with gvim only...
>
> Thanks, Stephan. I'm having the problem with MacVim.
OK, what I found out is this (maybe someone else on the list can
confirm this):
- Mappings like <S-CR> do not work in the console version of vim.
- I do not know about Macvim, but you can test this yourself. In my
gvim, I can do e.g.
:map <S-CR> echo('Hi')<CR>
and every time I press Shift-CR, `Hi' is printed. In my console
vim this does nothing.
So I suspect that the orgmode plugin is working normally, but many of
the mappings (all that use Shift-something or Control-something) do not
work. In theory you could fix this yourself, the keybindings are
contained in the .py-Files in the .vim/ftplugin/orgmode/plugins folder
(maybe the folder layout differs for MacVim). However, as long as you
do not exactly know what the functions you are mapping are actually
good for, you will probably not be able to come up with a sensible
mapping.
The other course of action would be to complain to the orgmode-author
that his mappings are not compatible with all vim versions. Also,
mappings that use the shift and control key a lot are really not
something you should use in vim. Actually it reminds me more of this...
other... editor.
I think the author is also on this list, so maybe he reads this and
wants to defend himself ;)
Best,
Stephan
--
You received this message from the "vim_use" maillist.
Do not top-post! Type your reply below the text you are replying to.
For more information, visit http://www.vim.org/maillist.php
No comments:
Post a Comment