On Sun, Jul 16, 2017 at 2:14 AM, lewis <lewisn...@operamail.com> wrote:
Yes, technically they are commands and in your example you use the keyboard > directly, not the menu. > This is a discussion about menus, not commands. > In the context of a menu they appear as a File Open menu operation. They > seem duplicated and out of position. > Opening important Leo files in the File menu seems reasonable to me. I am not bothered about the duplication, as I said. > Under a Cmds heading the display should be the actual commands: > > open-cheat-sheet-leo > open-leo-plugins-leo > open-LeoDocs-leo > open-quickstart-leo > open-scripts-leo > Reasonable, despite possible duplication ;-) Further, a better learning opportunity for newbies would be a > 'Help-for-Menus' entry to show the menu coding. HTH with that if you like :) > Took me a few seconds to understand what you meant by "menu coding. You mean, I presume, the format of @menu and @item settings within settings files. This information belongs in leoSettings.leo, along with the documentation of all other kinds of settings nodes. A help-for command would not good--the information is for devs, not newbies. leoSettings.leo should document @menu and @item in direct children of the node called: `About this file, leoSettings.leo`. I thought they were there, but apparently not. This is a big miss. Good catch. Please feel free to modify leoSettings.leo, or to suggest such changes here. Edward -- You received this message because you are subscribed to the Google Groups "leo-editor" group. To unsubscribe from this group and stop receiving emails from it, send an email to leo-editor+unsubscr...@googlegroups.com. To post to this group, send email to leo-editor@googlegroups.com. Visit this group at https://groups.google.com/group/leo-editor. For more options, visit https://groups.google.com/d/optout.
