On 11/9/06, Bram Moolenaar <[EMAIL PROTECTED]> wrote:
buffer-local menus are complicated. What about menus that are not for
the current buffer, hide them? Would make jumping between buffers very
slow.
Emacs does this, I believe. I don't think there's a noticable lag.
Mind you, I don't use m
On Thu, 9 Nov 2006, Bram Moolenaar wrote:
> buffer-local menus are complicated. What about menus that are not
> for the current buffer, hide them? Would make jumping between
> buffers very slow.
When I've defined menus that are only applicable to a buffer or a
filetype I've just defined autocom
Benji Fisher wrote:
> Maps and menus work in much the same way, and when writing a vim
> script (especially an ftplugin) I like to make a menu item corresponding
> to each key map that I define. Unfortunately, there are two ways that
> maps and menus differ:
>
> 1. There is an :amenu comma
Yakov Lerner wrote:
> Vim can be in "stacked-mode", like insert -> -> :norm!
> is normal-mode inside-command-mode inside insert-mode.
>
> mode() function reports ony one mode, this is incompete info.
> It makes a difference whether we are in "command-mode
> inside insert-mode", or in "command-m
Maps and menus work in much the same way, and when writing a vim
script (especially an ftplugin) I like to make a menu item corresponding
to each key map that I define. Unfortunately, there are two ways that
maps and menus differ:
1. There is an :amenu command (and also :anoremenu), but ther
Vim can be in "stacked-mode", like insert -> -> :norm!
is normal-mode inside-command-mode inside insert-mode.
mode() function reports ony one mode, this is incompete info.
It makes a difference whether we are in "command-mode
inside insert-mode", or in "command-mode not inside insert mode".
Curr
