Thanks, both, for the advice. Now that I know what the problem is, I can take appropriate steps to rectify it in my .vimrc.
>From the broader standpoint of making Vim better, I still think that this particular Vim "feature" shouldn't be the default though. Consider the average user who downloads Vim for the first time, launches it in "Easy" mode, and starts typing. Ideally he should be able to do basic editing having never learned about :unmap, :source, or .vimrc files. Most of Vim seems to be designed this way, which is great because it makes the learning curve for Vim reasonable. But the behavior we've identified is a peculiar exception. It affects even the most basic editing tasks in a highly unintuitive, unconventional, and unexplained way. I'm a fan of backward compatability, but even if this exists for compatability reasons I think that this is one case where backward compatibility should take a back seat to user-friendliness. Would there be severe consequences to changing the map command in vimrc_example.vim to an nmap in future releases of Vim? That seems to me like a graceful solution that would at least hide this oddity from easy-mode users and the like. Best, Kevin --~--~---------~--~----~------------~-------~--~----~ You received this message from the "vim_dev" maillist. For more information, visit http://www.vim.org/maillist.php -~----------~----~----~----~------~----~------~--~---
