This file is indexed.

/usr/share/doc/texinfo/html/Menu-Location.html is in texinfo-doc-nonfree 4.13a-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
80
81
82
83
84
85
<html lang="en">
<head>
<title>Menu Location - GNU Texinfo 4.13</title>
<meta http-equiv="Content-Type" content="text/html">
<meta name="description" content="GNU Texinfo 4.13">
<meta name="generator" content="makeinfo 4.13">
<link title="Top" rel="start" href="index.html#Top">
<link rel="up" href="Menus.html#Menus" title="Menus">
<link rel="next" href="Writing-a-Menu.html#Writing-a-Menu" title="Writing a Menu">
<link href="http://www.gnu.org/software/texinfo/" rel="generator-home" title="Texinfo Homepage">
<!--
This manual is for GNU Texinfo (version 4.13, 18 September 2008),
a documentation system that can produce both online information and a
printed manual from a single source.

Copyright (C) 1988, 1990, 1991, 1992, 1993, 1995, 1996, 1997,
1998, 1999, 2000, 2001, 2002, 2003, 2004, 2005, 2006, 2007, 2008
Free Software Foundation, Inc.

     Permission is granted to copy, distribute and/or modify this
     document under the terms of the GNU Free Documentation License,
     Version 1.2 or any later version published by the Free Software
     Foundation; with no Invariant Sections, with the Front-Cover Texts
     being ``A GNU Manual'', and with the Back-Cover Texts as in (a)
     below.  A copy of the license is included in the section entitled
     ``GNU Free Documentation License.''

     (a) The FSF's Back-Cover Text is: ``You are free to copy and modify
     this GNU Manual.  Buying copies from GNU Press supports the FSF in
     developing GNU and promoting software freedom.''
  -->
<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="Menu-Location"></a>
<p>
Next:&nbsp;<a rel="next" accesskey="n" href="Writing-a-Menu.html#Writing-a-Menu">Writing a Menu</a>,
Up:&nbsp;<a rel="up" accesskey="u" href="Menus.html#Menus">Menus</a>
<hr>
</div>

<h3 class="section">7.1 Menu Location</h3>

<p><a name="index-Menu-location-341"></a><a name="index-Location-of-menus-342"></a>
A menu must be located at the end of a node, without any regular text
or additional commands between the <code>@end menu</code> and the beginning
of the next node.  (As a consequence, there may be at most one menu in
a node.)

  <p><a name="index-Info-format_002c-and-menus-343"></a>This is actually a useful restriction, since a reader who uses the
menu could easily miss any such text.  Technically, it is necessary
because in Info format, there is no marker for the end of a menu, so
Info-reading programs would have no way to know when the menu ends and
normal text resumes.

  <p><a name="index-Hierarchical-documents_002c-and-menus-344"></a>Technically, menus can carry you to any node, regardless of the
structure of the document; even to nodes in a different Info file. 
However, we do not recommend ever making use of this, because the
<samp><span class="command">makeinfo</span></samp> implicit pointer creation feature (see <a href="makeinfo-Pointer-Creation.html#makeinfo-Pointer-Creation">makeinfo Pointer Creation</a>) and GNU Emacs Texinfo mode updating commands work
only to create menus of subordinate nodes in a hierarchically
structured document.  Instead, use cross references to refer to
arbitrary nodes.

  <p>In the past, we recommended using a &lsquo;<samp><span class="samp">@heading</span></samp>&rsquo; command within an
<code>@ifinfo</code> conditional instead of the normal sectioning commands
after a very short node with a menu.  This had the advantage of making
the printed output look better, because there was no very short text
between two headings on the page.  But this also does not work with
<samp><span class="command">makeinfo</span></samp>'s implicit pointer creation, and it also makes the
XML output incorrect, since it does not reflect the true document
structure.  So, regrettably, we can no longer recommend this.

  </body></html>