This file is indexed.

/usr/share/doc/mailutils-doc/mailutils.html/Paths.html is in mailutils-doc 1:2.99.99-1ubuntu2.

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
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
<html>
<!-- Published by the Free Software Foundation,
51 Franklin Street, Fifth Floor
Boston, MA 02110-1301, USA

Copyright (C) 1999-2004, 2008-2012, 2014-2015 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, no Front-Cover, and no Back-Cover texts.
A copy of the license is included in the section entitled "GNU Free
Documentation License". -->
<!-- Created by GNU Texinfo 6.1, http://www.gnu.org/software/texinfo/ -->
<head>
<title>GNU Mailutils Manual: Paths</title>

<meta name="description" content="GNU Mailutils Manual: Paths">
<meta name="keywords" content="GNU Mailutils Manual: Paths">
<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="Function-Index.html#Function-Index" rel="index" title="Function Index">
<link href="index.html#SEC_Contents" rel="contents" title="Table of Contents">
<link href="conf_002dsyntax.html#conf_002dsyntax" rel="up" title="conf-syntax">
<link href="Include.html#Include" rel="next" title="Include">
<link href="Statements.html#Statements" rel="prev" title="Statements">
<style type="text/css">
<!--
a.summary-letter {text-decoration: none}
blockquote.indentedblock {margin-right: 0em}
blockquote.smallindentedblock {margin-right: 0em; font-size: smaller}
blockquote.smallquotation {font-size: smaller}
div.display {margin-left: 3.2em}
div.example {margin-left: 3.2em}
div.lisp {margin-left: 3.2em}
div.smalldisplay {margin-left: 3.2em}
div.smallexample {margin-left: 3.2em}
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.nolinebreak {white-space: nowrap}
span.roman {font-family: initial; font-weight: normal}
span.sansserif {font-family: sans-serif; font-weight: normal}
ul.no-bullet {list-style: none}
-->
</style>


</head>

<body lang="en">
<a name="Paths"></a>
<div class="header">
<p>
Previous: <a href="Statements.html#Statements" accesskey="p" rel="prev">Statements</a>, Up: <a href="conf_002dsyntax.html#conf_002dsyntax" accesskey="u" rel="up">conf-syntax</a> &nbsp; [<a href="index.html#SEC_Contents" title="Table of contents" rel="contents">Contents</a>][<a href="Function-Index.html#Function-Index" title="Index" rel="index">Index</a>]</p>
</div>
<hr>
<a name="Statement-Path"></a>
<h4 class="subsubsection">2.2.1.3 Statement Path</h4>

<p><code>Mailutils</code> configuration files have a distinct hierarchical
structure.  Each statement in such files can therefore be identified
by its name and the names of block statements containing it.  Such
names form this statement <em>pathname</em>, similar to that used,
e.g. by UNIX file system.
</p>
<p>For example, consider the following file:
</p>
<div class="example">
<pre class="example">foo {
  bar {
    baz 45;   # <span class="roman">A.</span>
  }
  baz 98;     # <span class="roman">B.</span>
}
</pre></div>

<p>The full pathname of the statement marked with &lsquo;<samp>A</samp>&rsquo; can be written
as:
</p>
<div class="example">
<pre class="example">.foo.bar.baz
</pre></div>

<p>Similarly, the statement marked with &lsquo;<samp>B</samp>&rsquo; has the following
pathname:
</p>
<div class="example">
<pre class="example">.foo.baz
</pre></div>

<p>The default path component separator is dot.  A pathname beginning with
a component separator is called <em>absolute pathname</em>.  Absolute
pathnames uniquely identify corresponding statements.  If the leading
dot is omitted, the resulting pathname is called
<em>relative</em>.  Relative pathnames identify statements in relation to 
the current point of reference in the configuration file.
</p>
<p>Any other punctuation character can be used as a component separator,
provided that it appears at the beginning of the pathname.  In other
words, only absolute pathnames allow for a change in component separators.
</p>
<p>A block statement that has a tag is referred to by its name, followed
by an equals sign, followed by the tag value.  For example, the
statement &lsquo;<samp>A</samp>&rsquo; in the file below:
</p>
<div class="example">
<pre class="example">program x {
  bar {
    baz 45;   # <span class="roman">A.</span>
  }
}
</pre></div>

<p>is identified by the following pathname:
</p>
<div class="example">
<pre class="example">.program=x.bar.baz
</pre></div>

<p>The tag can optionally be enclosed in a pair of double quotes.  Such a
quoting becomes mandatory for tags that contain white space or path
component separator, e.g.:
</p>
<div class="example">
<pre class="example">.program=&quot;a.out&quot;.bar.baz
</pre></div>

<hr>
<div class="header">
<p>
Previous: <a href="Statements.html#Statements" accesskey="p" rel="prev">Statements</a>, Up: <a href="conf_002dsyntax.html#conf_002dsyntax" accesskey="u" rel="up">conf-syntax</a> &nbsp; [<a href="index.html#SEC_Contents" title="Table of contents" rel="contents">Contents</a>][<a href="Function-Index.html#Function-Index" title="Index" rel="index">Index</a>]</p>
</div>



</body>
</html>