On Tuesday, December 24, 2013 4:54:08 PM UTC-6, Pedro Ferrari wrote:
> Along the way I realized that if try the following mappings
> 
> nnoremap * *<C-o>
> nnoremap # #<C-o>
> 
> then once again: (i) in gVim the # mapping works fine and the * mapping 
> doesn't and (ii) in console vim none of the mappings work. 
> 
> I don't know if this a bug or a problem with my setup (I'm relatively new to 
> Vim) but any help will be greatly appreciated.
> 
> Thanks!

If I use vim -N -u NONE -i NONE then these two mappings work fine.

If I drop the -N and just do vim -u NONE -i NONE then Vim searches for the word 
under the cursor and then beeps at me.

Note that without the -N, Vim is running in "compatible" mode and therefore 
tries to behave like plain vi. With the -N it is in "nocompatible" mode.

I don't know whether <C-O> is actually supposed to fail in compatible mode, but 
I do notice in the help for CTRL-O that it says "not in vi".

I wonder if this is the cause, and whether something similar is going on in 
your actual mapping.

...oh nevermind, I guess you do a "set nocp" right in the beginning before you 
source the script. Time to investigate further...

-- 
-- 
You received this message from the "vim_dev" 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

--- 
You received this message because you are subscribed to the Google Groups 
"vim_dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
For more options, visit https://groups.google.com/groups/opt_out.

Raspunde prin e-mail lui