After the "menu already exists: &<menu name>" warning, the menu entries are added to the existing menu.

[SegundoBob]

Adding the menu items to the existing menu, is the wrong thing to do for my use cases.

For example, I define a menu in my myLeoSettings.leo file. Hence, whenever I use the "Settings" menu to open myLeoSettings.leo, I get a warning message and my menu gets a complete set of duplicate menu items.

Another example, I keep a diary Leo-Editor file for each month. This file defines a menu of diary operations. When the diary operation "begin new month" happens, the new month file gets the warning message and a complete set of duplicate items.

Is there a case where adding the menu items to an existing menu is the right thing to do?

If no one suggests such a use case, then after the "menu already exists" warning, the menu items should NOT be added to the existing menu.

This problem is demonstrated by the file and the test procedures attached to bug 1286909.

Test System:
Xubuntu64 13.10
Leo Log Window
Leo 4.11 final, build 128f96dcd70d (branch: master), 2014-03-02 13:11:09
Python 2.7.5, qt version 4.8.4
linux2
setting leoID from os.getenv('USER'): 'bob06'
load dir: /home/ldi/git/leo-editor/leo/core
global config dir: /home/ldi/git/leo-editor/leo/config
home dir: /home/bob06
reading settings in /home/ldi/git/leo-editor/leo/config/leoSettings.leo
docutils loaded
reading settings in /home/bob06/.leo/myLeoSettings.leo
Found /help
Abbreviations off
reading settings in /home/ldi/tmp/settingsCreep01.leo
Found /help
Abbreviations off
reading: /home/ldi/tmp/settingsCreep01.leo

[Edward K. Ream (edreamleo)]

Moved to github tracker: https://github.com/leo-editor/leo-editor/issues/73

[Edward K. Ream (edreamleo)]

An @button node might be better in your use case.