ne allows you to change the contents of its menus. In order to
accomplish this task, you have to create a file named `
.menus' in your
home directory, or in `
$HOME/.ne'. You can change the default name
(possibly specifying a complete path) using the
Each line of a menu configuration file not starting with the `
ITEM' keywords is considered a comment. You should describe the menus
as in the following example:
MENU "Project" ITEM "Open... ^O" Open ITEM "Close " Close ITEM "DoIt " Macro DoIt
In other words: a line of this form
will start the definition of a new menu, having the given title. Each line of the form
ITEM "text" command
will then define a menu item, and associate the given command to it.
Any number of menus can be accomodated, but you should consider that many terminals are 80 column wide. There is also a minor restriction on the items---their width has to be constant throughout each menu (but different menus can have different widths). Note that the text of an item, as the name of a menu, is between quotes. Whatever follows the last quote is considered the command associated to the menu.
^O' in the previous example) is very important for the beginner;
there is no relation inside
ne about what you say in the menu and how
you configure the key bindings (see Key Bindings). Please do not say
things in the menus which are not true in the key binding file.
The menu configuration file is parsed at startup. If something does not
ne exits displaying an error message. If you want to skip this
phase (for instance, in order to correct the broken file), just give
--noconfig argument. See Arguments.