This file is indexed.

/usr/share/doc/ne/html/Changing-Menus.html is in ne-doc 2.5-1.

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
<html lang="en">
<head>
<title>Changing Menus - ne's manual</title>
<meta http-equiv="Content-Type" content="text/html">
<meta name="description" content="ne's manual">
<meta name="generator" content="makeinfo 4.13">
<link title="Top" rel="start" href="index.html#Top">
<link rel="up" href="Configuration.html#Configuration" title="Configuration">
<link rel="prev" href="Key-Bindings.html#Key-Bindings" title="Key Bindings">
<link href="http://www.gnu.org/software/texinfo/" rel="generator-home" title="Texinfo Homepage">
<meta http-equiv="Content-Style-Type" content="text/css">
<style type="text/css"><!--
  pre.display { font-family:inherit }
  pre.format  { font-family:inherit }
  pre.smalldisplay { font-family:inherit; font-size:smaller }
  pre.smallformat  { font-family:inherit; font-size:smaller }
  pre.smallexample { font-size:smaller }
  pre.smalllisp    { font-size:smaller }
  span.sc    { font-variant:small-caps }
  span.roman { font-family:serif; font-weight:normal; } 
  span.sansserif { font-family:sans-serif; font-weight:normal; } 
--></style>
</head>
<body>
<div class="node">
<a name="Changing-Menus"></a>
<p>
Previous:&nbsp;<a rel="previous" accesskey="p" href="Key-Bindings.html#Key-Bindings">Key Bindings</a>,
Up:&nbsp;<a rel="up" accesskey="u" href="Configuration.html#Configuration">Configuration</a>
<hr>
</div>

<h3 class="section">5.2 Changing Menus</h3>

<p><a name="index-Configuring-the-menus-226"></a>
<code>ne</code> allows you to change the contents of its menus. To
accomplish this task, you have to create a file named <samp><span class="file">.menus</span></samp> in your
home directory, or in <samp><span class="file">~/.ne</span></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>Each line of a menu configuration file not starting with the &lsquo;<samp><span class="samp">MENU</span></samp>&rsquo; or
&lsquo;<samp><span class="samp">ITEM</span></samp>&rsquo; keywords is considered a comment. You should describe the menus
as in the following example:

<pre class="example">     MENU "File"
     ITEM "Open...     ^O" Open
     ITEM "Close         " Close
     ITEM "DoIt          " Macro DoIt
</pre>
   <p>In other words: a line of this form
<pre class="example">     MENU "<var>title</var>"
</pre>
   <p>will start the definition of a new menu, having the given title. Each line
of the form
<pre class="example">     ITEM "<var>text</var>" <var>command</var>
</pre>
   <p>will then define a menu item, and associate the given command to it.

   <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&mdash;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 class="noindent"><strong>Warning:</strong> the description of key bindings in menus
(&lsquo;<samp><span class="samp">^O</span></samp>&rsquo; 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>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>.

   </body></html>