/usr/share/doc/ne/html/Changing-Menus.html is in ne-doc 3.0.1-2build1.
This file is owned by root:root, with mode 0o644.
The actual contents of the file can be viewed below.
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100 101 102 103 104 105 106 107 108 109 110 111 112 113 114 115 116 117 118 119 120 | <!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
<html>
<!-- Created by GNU Texinfo 5.2, http://www.gnu.org/software/texinfo/ -->
<head>
<title>ne’s manual: Changing Menus</title>
<meta name="description" content="ne’s manual: Changing Menus">
<meta name="keywords" content="ne’s manual: Changing Menus">
<meta name="resource-type" content="document">
<meta name="distribution" content="global">
<meta name="Generator" content="makeinfo">
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
<link href="index.html#Top" rel="start" title="Top">
<link href="Concept-Index.html#Concept-Index" rel="index" title="Concept Index">
<link href="Command-Index.html#SEC_Contents" rel="contents" title="Table of Contents">
<link href="Configuration.html#Configuration" rel="up" title="Configuration">
<link href="Hints-and-Tricks.html#Hints-and-Tricks" rel="next" title="Hints and Tricks">
<link href="Key-Bindings.html#Key-Bindings" rel="prev" title="Key Bindings">
<style type="text/css">
<!--
a.summary-letter {text-decoration: none}
blockquote.smallquotation {font-size: smaller}
div.display {margin-left: 3.2em}
div.example {margin-left: 3.2em}
div.indentedblock {margin-left: 3.2em}
div.lisp {margin-left: 3.2em}
div.smalldisplay {margin-left: 3.2em}
div.smallexample {margin-left: 3.2em}
div.smallindentedblock {margin-left: 3.2em; font-size: smaller}
div.smalllisp {margin-left: 3.2em}
kbd {font-style:oblique}
pre.display {font-family: inherit}
pre.format {font-family: inherit}
pre.menu-comment {font-family: serif}
pre.menu-preformatted {font-family: serif}
pre.smalldisplay {font-family: inherit; font-size: smaller}
pre.smallexample {font-size: smaller}
pre.smallformat {font-family: inherit; font-size: smaller}
pre.smalllisp {font-size: smaller}
span.nocodebreak {white-space:nowrap}
span.nolinebreak {white-space:nowrap}
span.roman {font-family:serif; font-weight:normal}
span.sansserif {font-family:sans-serif; font-weight:normal}
ul.no-bullet {list-style: none}
-->
</style>
</head>
<body lang="en" bgcolor="#FFFFFF" text="#000000" link="#0000FF" vlink="#800080" alink="#FF0000">
<a name="Changing-Menus"></a>
<div class="header">
<p>
Previous: <a href="Key-Bindings.html#Key-Bindings" accesskey="p" rel="prev">Key Bindings</a>, Up: <a href="Configuration.html#Configuration" accesskey="u" rel="up">Configuration</a> [<a href="Command-Index.html#SEC_Contents" title="Table of contents" rel="contents">Contents</a>][<a href="Concept-Index.html#Concept-Index" title="Index" rel="index">Index</a>]</p>
</div>
<hr>
<a name="Changing-Menus-1"></a>
<h3 class="section">5.2 Changing Menus</h3>
<a name="index-Configuring-the-menus"></a>
<p><code>ne</code> allows you to change the contents of its menus. To
accomplish this task, you have to create a file named <samp>.menus</samp> in your
home directory, or in <samp>~/.ne</samp>. You can change the default name
(possibly specifying a complete path) using the <code>--menus</code> argument
(see <a href="Arguments.html#Arguments">Arguments</a>).
</p>
<p>Each line of a menu configuration file not starting with the ‘<samp>MENU</samp>’ or
‘<samp>ITEM</samp>’ keywords is considered a comment. You should describe the menus
as in the following example:
</p>
<div class="example">
<pre class="example">MENU "File"
ITEM "Open... ^O" Open
ITEM "Close " Close
ITEM "DoIt " Macro DoIt
</pre></div>
<p>In other words: a line of this form
</p><div class="example">
<pre class="example">MENU "<var>title</var>"
</pre></div>
<p>will start the definition of a new menu, having the given title. Each line
of the form
</p><div class="example">
<pre class="example">ITEM "<var>text</var>" <var>command</var>
</pre></div>
<p>will then define a menu item, and associate the given command to it.
</p>
<p>Any number of menus can be accommodated, but you should consider that many
terminals are 80 columns 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.
</p>
<p><strong>Warning:</strong> the description of key bindings in menus
(‘<samp>^O</samp>’ in the previous example) is very important for the beginner;
there is no relation inside <code>ne</code> about what you say in the menu and how
you configure the key bindings (see <a href="Key-Bindings.html#Key-Bindings">Key Bindings</a>). Please do not say
things in the menus that are not true in the key binding file.
</p>
<p>The menu configuration file is parsed at startup. If something does not
work, <code>ne</code> exits displaying an error message. If you want <code>ne</code> to
skip the menu configuration phase (for instance, to correct the
broken file), just give <code>ne</code> the <code>--no-config</code> argument.
See <a href="Arguments.html#Arguments">Arguments</a>.
</p>
<hr>
<div class="header">
<p>
Previous: <a href="Key-Bindings.html#Key-Bindings" accesskey="p" rel="prev">Key Bindings</a>, Up: <a href="Configuration.html#Configuration" accesskey="u" rel="up">Configuration</a> [<a href="Command-Index.html#SEC_Contents" title="Table of contents" rel="contents">Contents</a>][<a href="Concept-Index.html#Concept-Index" title="Index" rel="index">Index</a>]</p>
</div>
</body>
</html>
|