Steps to reproduce
Launch MacVim 8.2.3455 (172).
Press and hold the option key and use the mouse to open the File menu. Repeat this several times, with a half-second or so delay. Observe the "Close" / "Close All" menu items.
Eventually, often by the third or fourth try, "Close All" will become "<<Close All -unlocalized>>"
menu.vim doesn't define a "Close All" item or corresponding :macmenu, it appears that Cocoa inserts this alternate item to the item with the performClose: selector. In fact, doing aunmenu * in gvimrc and then rebuilding a File menu with any item associated with performClose: via macmenu will exhibit this behavior.
Searching the internet reveals that other applications have experienced this.
Doing let do_no_lazyload_menus = 1 in vimrc (as the very first line, before executing anything that causes menu.vim to get sourced) seems to make the problem much harder to reproduce, even though nothing in menu.vim directly affected by the variable seems obviously related. Specifically, it seems to take opening a separate window in MacVim to trigger the menu changing.
Expected behaviour
"Close All" should remain "Close All" not display what appears to be diagnostics text.
Version of Vim and architecture
MacVim 8.2.3455 (172)
Environment
macOS Monterey 12.1 on a MacBook Pro (14-inch, 2021) (M1 Max).
How MacVim was installed
Downloaded from GitHub releases page (using the .dmg).
Logs and stack traces
No response
Vim configuration where issue is reproducable
No response
Issue has been tested with given configuration
Issue has been tested with no configuration
Other conditions
Steps to reproduce
Launch MacVim 8.2.3455 (172).
Press and hold the option key and use the mouse to open the File menu. Repeat this several times, with a half-second or so delay. Observe the "Close" / "Close All" menu items.
Eventually, often by the third or fourth try, "Close All" will become "<<Close All -unlocalized>>"
menu.vimdoesn't define a "Close All" item or corresponding:macmenu, it appears that Cocoa inserts this alternate item to the item with theperformClose:selector. In fact, doingaunmenu *ingvimrcand then rebuilding a File menu with any item associated withperformClose:viamacmenuwill exhibit this behavior.Searching the internet reveals that other applications have experienced this.
Doing
let do_no_lazyload_menus = 1invimrc(as the very first line, before executing anything that causesmenu.vimto get sourced) seems to make the problem much harder to reproduce, even though nothing inmenu.vimdirectly affected by the variable seems obviously related. Specifically, it seems to take opening a separate window in MacVim to trigger the menu changing.Expected behaviour
"Close All" should remain "Close All" not display what appears to be diagnostics text.
Version of Vim and architecture
MacVim 8.2.3455 (172)
Environment
macOS Monterey 12.1 on a MacBook Pro (14-inch, 2021) (M1 Max).
How MacVim was installed
Downloaded from GitHub releases page (using the .dmg).
Logs and stack traces
No response
Vim configuration where issue is reproducable
No response
Issue has been tested with given configuration
Issue has been tested with no configuration
mvim --clean(orgvim, supplied by MacVim distribution)vim --clean(in terminal, supplied by MacVim distribution)vim --clean(in terminal, other suppliers, e.g. /usr/bin/vim)Other conditions