This file is indexed.

/usr/share/doc/mailutils-doc/mailutils.html/Option-Basics.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
<!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: Option Basics</title>

<meta name="description" content="GNU Mailutils Manual: Option Basics">
<meta name="keywords" content="GNU Mailutils Manual: Option Basics">
<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="command-line.html#command-line" rel="up" title="command line">
<link href="Common-Options.html#Common-Options" rel="next" title="Common Options">
<link href="command-line.html#command-line" rel="prev" title="command line">
<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="Option-Basics"></a>
<div class="header">
<p>
Next: <a href="Common-Options.html#Common-Options" accesskey="n" rel="next">Common Options</a>, Up: <a href="command-line.html#command-line" accesskey="u" rel="up">command line</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="Basic-Notions-About-Command-Line-Options"></a>
<h4 class="subsection">2.1.1 Basic Notions About Command Line Options</h4>

<p>Many command line options have two forms, called short and long
forms.  Both forms are absolutely identical in function; they are
interchangeable. 
</p>
<p>The <em>short</em> form is a traditional form for UNIX utilities.
In this form, the option consists of a single dash, followed by a
single letter, e.g.  <samp>-c</samp>.
</p>
<p>Short options which require arguments take their arguments
immediately following the option letter, optionally separated by white
space.  For example, you might write <samp>-f name</samp>, or <samp>-fname</samp>.
Here, <samp>-f</samp> is the option, and <samp>name</samp> is its argument.
</p>
<p>Short options which allow optional arguments take their arguments
immediately following the option letter, <em>without any intervening
white space characters</em>.  This is important, so that the command line
parser might discern that the text following option is its argument,
not the next command line parameter.  For example, if option <samp>-d</samp>
took an optional argument, then <samp>-dname</samp> would mean the option
with its argument (<samp>name</samp> in this case), and <samp>-d name</samp> would
mean the <samp>-d</samp> option without any argument, followed by command
line argument <samp>name</samp>.
</p>
<p>Short options&rsquo; letters may be clumped together, but you are not
required to do this.  When short options are clumped as a set, use one
(single) dash for them all, e.g.  <samp>-cvl</samp> is equivalent to <samp>-c
-v -l</samp>.  However, only options that do not take arguments may be
clustered this way.  If an option takes an argument, it can only be
the last option in such a cluster, otherwise it would be impossible to
specify the argument for it.  Anyway, it is much more readable to
specify such options separated.
</p>
<p>The <em>long</em> option names are probably easier to memorize than
their short counterparts.  They consist of two dashes, followed by a
multi-letter option name, which is usually selected to be a mnemonics
for the operation it requests.  For example, <samp>--verbose</samp> is a
long option that increases the verbosity of a utility.  In addition,
long option names can abbreviated, provided that such an abbreviation
is unique among the options understood by a given utility.  For
example, if a utility takes options <samp>--foreground</samp> and
<samp>--forward</samp>, then the shortest possible abbreviations for these
options are <samp>--fore</samp> and <samp>--forw</samp>, correspondingly.  If
you try to use <samp>--for</samp>, the utility will abort and inform you
that the abbreviation you use is ambiguous, so it is not clear which
of the options you intended to use.
</p>
<p>Long options which require arguments take those arguments following
the option name.  There are two ways of specifying a mandatory
argument.  It can be separated from the option name either by an equal
sign, or by any amount of white space characters.  For example, if the
<samp>--file</samp> option requires an argument, and you wish to supply
<samp>name</samp> as its argument, then you can do so using any of the
following notations: <samp>--file=name</samp> or <samp>--file name</samp>.
</p>
<p>In contrast, optional arguments must always be introduced using an
equal sign.
</p>
<hr>
<div class="header">
<p>
Next: <a href="Common-Options.html#Common-Options" accesskey="n" rel="next">Common Options</a>, Up: <a href="command-line.html#command-line" accesskey="u" rel="up">command line</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>