D7net Mini Sh3LL v1
| Current File : //usr/share/systemd/../libc-bin/../doc/libgcc-s1/../info/html/Invoking-Info.html |
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
<html>
<!-- This manual is for Stand-alone GNU Info (version 6.7,
23 September 2019), a program for viewing documents in Info format
(usually created from Texinfo source files).
Copyright (C) 1992, 1993, 1996, 1997, 1998, 1999, 2001,
2002, 2003, 2004, 2005, 2006, 2007, 2008, 2009, 2010, 2011, 2012,
2013, 2014, 2015, 2016, 2017, 2018, 2019 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.3 or
any later version published by the Free Software Foundation; with no
Invariant Sections, with no Front-Cover Texts, and with no Back-Cover
Texts. A copy of the license is included in the section entitled
"GNU Free Documentation License" in the Texinfo manual.
This document is part of a collection distributed under the GNU Free
Documentation License. If you want to distribute this document
separately from the collection, you can do so by adding a copy of the
license to the document, as described in section 6 of the license. -->
<!-- Created by GNU Texinfo 6.7, http://www.gnu.org/software/texinfo/ -->
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
<title>Invoking Info (Stand-alone GNU Info 6.7)</title>
<meta name="description" content="Invoking Info (Stand-alone GNU Info 6.7)">
<meta name="keywords" content="Invoking Info (Stand-alone GNU Info 6.7)">
<meta name="resource-type" content="document">
<meta name="distribution" content="global">
<meta name="Generator" content="texi2any">
<link href="index.html" rel="start" title="Top">
<link href="Index.html" rel="index" title="Index">
<link href="index.html#SEC_Contents" rel="contents" title="Table of Contents">
<link href="index.html" rel="up" title="Top">
<link href="Cursor-Commands.html" rel="next" title="Cursor Commands">
<link href="Stand_002dalone-Info.html" rel="prev" title="Stand-alone Info">
<style type="text/css">
<!--
a.summary-letter {text-decoration: none}
blockquote.indentedblock {margin-right: 0em}
div.display {margin-left: 3.2em}
div.example {margin-left: 3.2em}
div.lisp {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}
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">
<span id="Invoking-Info"></span><div class="header">
<p>
Next: <a href="Cursor-Commands.html" accesskey="n" rel="next">Cursor Commands</a>, Previous: <a href="Stand_002dalone-Info.html" accesskey="p" rel="prev">Stand-alone Info</a>, Up: <a href="index.html" accesskey="u" rel="up">Top</a> [<a href="index.html#SEC_Contents" title="Table of contents" rel="contents">Contents</a>][<a href="Index.html" title="Index" rel="index">Index</a>]</p>
</div>
<hr>
<span id="Invoking-Info-1"></span><h2 class="chapter">2 Invoking Info</h2>
<span id="index-Info_002c-invoking"></span>
<span id="index-invoking-Info"></span>
<span id="index-command-line-options"></span>
<span id="index-options_002c-command-line"></span>
<span id="index-arguments_002c-command-line"></span>
<p>GNU Info accepts several options to control the initial node or nodes
being viewed, and to specify which directories to search for Info files.
Here is a template showing an invocation of GNU Info from the shell:
</p>
<div class="example">
<pre class="example">info [<var>option</var>…] [<var>manual</var>] [<var>menu-or-index-item</var>…]
</pre></div>
<p>Info will look for an entry called <var>manual</var> in the directory
files, which are named <samp>dir</samp>, that it finds in its search path.
The search is case-insensitive and considers substrings.
(If <var>manual</var> is not given, by default Info displays a composite
directory listing, constructed by combining the <samp>dir</samp> files.)
A basic example:
</p>
<div class="example">
<pre class="example">info coreutils
</pre></div>
<p>This looks for an entry labelled <code>coreutils</code>, or
<code>Coreutils</code>, etc., and if found, displays the referenced file
(e.g., <samp>coreutils.info</samp>) at the location given.
<code>info coreu</code> will find it too, if there is no better match.
</p>
<p>Another example:
</p>
<div class="example">
<pre class="example">info ls
</pre></div>
<p>Assuming the normal <code>dir</code> entry for <code>ls</code>, this will show the
<code>ls</code> documentation, which happens to be within the
<code>coreutils</code> manual rather than a separate manual. The <code>dir</code>
entries can point to an any node within a manual, so that users don’t
have to be concerned with the exact structure used by different
authors.
</p>
<span id="index-compressed-Info-files"></span>
<span id="index-files_002c-compressed"></span>
<span id="index-Info-files_002c-compressed"></span>
<p>If no entry is found in the directories, Info looks for files in its
search path with names based on <var>manual</var>. If <var>manual</var> is
not found, Info looks for it with a number of known extensions of Info
files, namely <samp>.info</samp>, <samp>-info</samp>, <samp>/index</samp>, and <samp>.inf</samp>.
For every known extension, if a regular file is not found, Info looks
for a compressed file. Info supports files compressed with <code>gzip</code>,
<code>xz</code>, <code>bzip2</code>, <code>lzip</code>, <code>lzma</code>, <code>compress</code> and
<code>yabba</code> programs, assumed to have extensions <samp>.z</samp>, <samp>.gz</samp>,
<samp>.xz</samp>, <samp>.bz2</samp>, <samp>.lz</samp>, <samp>.lzma</samp>, <samp>.Z</samp>, and
<samp>.Y</samp> respectively.<a id="DOCF1" href="#FOOT1"><sup>1</sup></a>
</p>
<p>You can specify the name of a node to visit with the <code>--node</code> or
<code>-n</code> option. Alternatively, you can specify the file and node
together using the same format that occurs in Info cross-references.
These two examples both load the ‘<samp>Files</samp>’ node within the
‘<samp>emacs</samp>’ manual:
</p>
<div class="example">
<pre class="example">info emacs -n Files
info '(emacs)Files'
</pre></div>
<span id="index-absolute-Info-file-names"></span>
<span id="index-relative-Info-file-names"></span>
<span id="index-file-names_002c-relative"></span>
<span id="index-Info-files_002c-relative"></span>
<p>If you want to load a file without looking in the search path, specify
<var>manual</var> either as an absolute path, or as a path relative to the
current directory which contains at least one slash character. (You
can also use the <code>--file</code> option for similar behavior, described
below.)
Examples:
</p>
<div class="example">
<pre class="example">info /usr/local/share/info/bash.info
info ./document.info
</pre></div>
<p>Info looks for <var>manual</var> only in the explicitly specified
directory, and adds that directory to its search path.
</p>
<span id="command_002dline-menu-items"></span><span id="index-menu_002c-following"></span>
<p>Info treats any remaining arguments as the names of menu items, or
(see below) index entries. The first argument is a menu item in the
‘<samp>Top</samp>’ node of the file loaded, the second argument is a menu item
in the first argument’s node, etc. You can move to the node of your
choice by specifying the menu names which describe the path to that
node. For example,
</p>
<div class="example">
<pre class="example">info emacs buffers
info texinfo Overview 'Using Texinfo'
</pre></div>
<p>The first example selects the menu item ‘<samp>Buffers</samp>’ in the node
‘<samp>(emacs)Top</samp>’. The second example loads the <samp>texinfo</samp> file and
looks in its top-level menu for a ‘<samp>Overview</samp>’ item, looks in the menu
of the node referenced, and finally displays the node referenced by the
‘<samp>Using Texinfo</samp>’ item.
</p>
<p>If there was only one <var>menu-or-index-item</var> argument and it wasn’t
found as a menu item, Info looks for it as an index entry. For example:
</p>
<div class="example">
<pre class="example">info libc printf
</pre></div>
<p>This loads the libc Info manual and first looks for <code>printf</code> in
the top-level menu as usual; since it isn’t there (at this writing),
it then looks in the indices. If it’s found there (which it is),
the relevant node at the given location is displayed.
</p>
<p>A complete list of options follows.
</p>
<dl compact="compact">
<dd><span id="g_t_002d_002dall"></span></dd>
<dt><code>--all</code></dt>
<dt><code>-a</code></dt>
<dd><span id="index-_002d_002dall-_0028_002da_0029-command-line-option"></span>
<p>Find all files matching <var>manual</var>. Three usage patterns are
supported, as follows.
</p>
<p>First, if <code>--all</code> is used together with <samp>--where</samp>,
<code>info</code> prints the names of all matching files found on
standard output (including ‘<samp>*manpages*</samp>’ if relevant) and exits.
</p>
<p>Second, if <code>--all</code> is used together with <samp>--output</samp>, the
contents of all matched files are dumped to the specified output
file.
</p>
<p>Otherwise, an interactive session is initiated. If more than one file
matches, a menu node is displayed listing the matches and allowing you
to select one. This menu node can be brought back at any time by
pressing <kbd>C-x f</kbd>. If there is only one match, <code>info</code>
starts as usual.
</p>
<p>When used with the <samp>--index-search</samp> option, <code>info</code>
displays a menu of matching index entries (just as the
<code>virtual-index</code> command does; see <a href="Index-Commands.html">Index Commands</a>).
</p>
<p>The <samp>--node</samp> option cannot be used together with this option.
</p>
<span id="g_t_002d_002dapropos"></span></dd>
<dt><code>--apropos=<var>string</var></code></dt>
<dt><code>-k <var>string</var></code></dt>
<dd><span id="index-_002d_002dapropos-_0028_002dk_0029-command-line-option"></span>
<span id="index-Searching-all-indices"></span>
<span id="index-Info-files_002c-searching-all-indices"></span>
<span id="index-Apropos_002c-in-Info-files"></span>
<p>Specify a string to search in every index of every Info file installed
on your system. Info looks up the named <var>string</var> in all the
indices it can find, prints the results to standard output, and then
exits. If you are not sure which Info file explains certain issues,
this option is your friend. (If your system has a lot of Info files
installed, searching all of them might take some time!)
</p>
<p>You can invoke the apropos command from inside Info; see
<a href="Searching-Commands.html">Searching Commands</a>.
</p>
</dd>
<dt><code>--debug=<var>number</var></code></dt>
<dt><code>-x <var>number</var></code></dt>
<dd><span id="index-_002d_002ddebug-_0028_002dx_0029-command-line-option"></span>
<span id="index-debugging"></span>
<p>Print additional debugging information. The argument specifies the
verbosity level, so a higher level includes all the information from
lower levels. For all available debugging output, use
<samp>-x -1</samp>. Info version 6.7 has these levels:
</p>
<dl compact="compact">
<dt><code>1</code></dt>
<dd><p>Print information about file handling, such as looking for <samp>dir</samp>
files and nodes written with ‘<samp>--output</samp>’.
</p>
</dd>
<dt><code>2</code></dt>
<dd><p>Print operations relating to <code>INFOPATH</code>.
</p>
</dd>
<dt><code>3</code></dt>
<dd><p>Print information about node searching.
</p></dd>
</dl>
<p>Debugging output goes to standard error.
</p>
</dd>
<dt><code>--directory <var>directory-path</var></code></dt>
<dt><code>-d <var>directory-path</var></code></dt>
<dd><span id="index-_002d_002ddirectory-_0028_002dd_0029-command-line-option"></span>
<span id="index-directory-path"></span>
<span id="index-INFOPATH"></span>
<span id="INFOPATH"></span><p>Add <var>directory-path</var> to the list of directory paths searched
when Info needs to find a file. You may issue <code>--directory</code>
multiple times; once for each directory which contains Info files,
or with a list of such directories separated by a colon (or semicolon
on MS-DOS/MS-Windows).
</p>
<p>Directories specified in the environment variable <code>INFOPATH</code> are added
to the directories specified with <code>--directory</code>, if any. The value of
<code>INFOPATH</code> is a list of directories usually separated by a colon;
on MS-DOS/MS-Windows systems, the semicolon is used. If the value of
<code>INFOPATH</code> ends with a colon (or semicolon on MS-DOS/MS-Windows),
the initial list of directories is constructed by appending the
build-time default to the value of <code>INFOPATH</code>.
</p>
<p>If you do not define <code>INFOPATH</code>, Info uses a default path defined
when Info was built as the initial list of directories.
</p>
<p>Regardless of whether <code>INFOPATH</code> is defined, the default
documentation directory defined when Info was built is added to the
search path. If you do not want this directory to be included, set
the <code>infopath-no-defaults</code> variable to <code>On</code>
(see <a href="Variables.html#infopath_002dno_002ddefaults">infopath-no-defaults</a>).
</p>
<p>If the list of directories contains the element <code>PATH</code>, that
element is replaced by a list of directories derived from the value of
the environment variable <code>PATH</code>. Each path element of the form
<var>dir/base</var> is replaced by <var>dir</var><code>/share/info</code> or
<var>dir</var><code>/info</code>, provided that directory exists.
</p>
</dd>
<dt><code>--dribble=<var>file</var></code></dt>
<dd><span id="index-_002d_002ddribble-command-line-option"></span>
<span id="index-keystrokes_002c-recording"></span>
<span id="index-remembering-user-keystrokes"></span>
<p>Specify a file where all user keystrokes will be recorded. This file
can be used later to replay the same sequence of commands, see the
‘<samp>--restore</samp>’ option below.
</p>
</dd>
<dt><code>--file <var>manual</var></code></dt>
<dt><code>-f <var>manual</var></code></dt>
<dd><span id="index-_002d_002dfile-_0028_002df_0029-command-line-option"></span>
<span id="index-Info-manual_002c-specifying-initial"></span>
<span id="index-initial-node_002c-specifying"></span>
<span id="index-startup-node_002c-specifying"></span>
<p>Specify a particular manual to visit without looking its name up in any
<samp>dir</samp> files.
</p>
<p>With this option, it starts by trying to visit
<code>(<var>manual</var>)Top</code>, i.e., the <code>Top</code> node in (typically)
<samp><var>manual</var>.info</samp>. As above, it tries various file extensions
to find the file. If no such file (or node) can be found, Info exits
without doing anything. As with the <samp>dir</samp> lookup described above,
any extra <var>menu-or-index-item</var> arguments are used to locate a node
within the loaded file.
</p>
<p>If <var>manual</var> is an absolute file name, or begins with <samp>./</samp> or
<samp>../</samp>, or contains an intermediate directory, Info will only look
for the file in the directory specified, and add this directory to
<code>INFOPATH</code>. (This is the same as what happens when <code>--file</code>
is not given.)
</p>
</dd>
<dt><code>--help</code></dt>
<dt><code>-h</code></dt>
<dd><span id="index-_002d_002dhelp-_0028_002dh_0029-command-line-option"></span>
<p>Output a brief description of the available Info command-line options.
</p>
</dd>
<dt><code>--index-search <var>string</var></code></dt>
<dd><span id="index-_002d_002dindex_002dsearch-command-line-option"></span>
<span id="index-index-search_002c-selecting-from-the-command-line"></span>
<span id="index-online-help_002c-using-Info-as"></span>
<p>After processing all command-line arguments, go to the index in the
selected Info file and search for index entries which match
<var>string</var>. If such an entry is found, the Info session begins with
displaying the node pointed to by the first matching index entry;
press <kbd>,</kbd> to step through the rest of the matching entries. If no
such entry exists, print ‘<samp>no entries found</samp>’ and exit with nonzero
status. This can be used from another program as a way to provide
online help, or as a quick way of starting to read an Info file at a
certain node when you don’t know the exact name of that node.
</p>
<p>When used with the <samp>--all</samp> option, <code>info</code>
displays a menu of matching index entries (just as the
<code>virtual-index</code> command does; see <a href="Index-Commands.html">Index Commands</a>).
</p>
<p>This command can also be invoked from inside Info; see <a href="Searching-Commands.html">Searching Commands</a>.
</p>
</dd>
<dt><code>--init-file <var>INIT-FILE</var></code></dt>
<dd><span id="g_t_002d_002dinit_002dfile"></span><span id="index-_002d_002dinit_002dfile-command-line-option"></span>
<p>Read key bindings and variable settings from <var>INIT-FILE</var> instead
of the <samp>.infokey</samp> file in your home directory. See <a href="Custom-Key-Bindings.html">Custom Key Bindings</a>.
</p>
</dd>
<dt><code>--node <var>nodename</var></code></dt>
<dt><code>-n <var>nodename</var></code></dt>
<dd><span id="index-_002d_002dnode-_0028_002dn_0029-command-line-option"></span>
<span id="index-node_002c-selecting-from-the-command-line"></span>
<p>Specify a particular node to visit in the initial file that Info
loads. You may specify <code>--node</code> multiple times: for an interactive
Info, each <var>nodename</var> is visited in its own window; for a
non-interactive Info (such as when <code>--output</code> is given) each
<var>nodename</var> is processed sequentially.
</p>
<p>You can specify both the file and node to the <code>--node</code> option
using the usual Info syntax, but don’t forget to escape the open and
close parentheses and whitespace from the shell; for example:<br>
<tt>info --node "(emacs)Buffers"</tt>
</p>
</dd>
<dt><code>--output <var>file</var></code></dt>
<dt><code>-o <var>file</var></code></dt>
<dd><span id="index-_002d_002doutput-_0028_002do_0029-command-line-option"></span>
<span id="index-file_002c-outputting-to"></span>
<span id="index-outputting-to-a-file"></span>
<p>Direct output to <var>file</var>. Each node that Info visits will be
output to <var>file</var> instead of interactively viewed. A value of
<code>-</code> for <var>file</var> means standard output.
</p>
</dd>
<dt><code>--no-raw-escapes</code></dt>
<dt><code>--raw-escapes, -R</code></dt>
<dd><span id="g_t_002d_002draw_002descapes"></span><span id="index-_002d_002draw_002descapes-_0028_002dR_0029-command-line-option"></span>
<span id="index-colors-in-documents"></span>
<span id="index-ANSI-escape-sequences-in-documents"></span>
<p>By default, Info passes SGR terminal control sequences (also known as
ANSI escape sequences) found in documents directly through to the
terminal. If you use the <code>--no-raw-escapes</code> options, these
sequences are displayed as other control characters are; for example, an
<kbd>ESC</kbd> byte is displayed as ‘<samp>^[</samp>’. The <code>--raw-escapes</code> and
<code>-R</code> options do not do anything, but are included for completeness.
</p>
<span id="index-man-pages_002c-bold-and-underline"></span>
<span id="index-GROFF_005fSGR"></span>
<p>Some versions of Groff (see <cite><a href="../groff/index.html#Top">Groff</a></cite>) produce man pages
with ANSI escape sequences for bold, italics, and underlined
characters, and for colorized text. If your <code>man</code> command
uses a version of Groff that does this (original GNU Groff does), and
your terminal supports these sequences, Info will display any bold or
underlined text in man pages. Some distributions have modified Groff
to require setting the <code>GROFF_SGR</code> environment variable to get
these sequences. See <a href="../groff/Invoking-grotty.html#Invoking-grotty">Invoking grotty</a> in <cite>Groff</cite>.
</p>
</dd>
<dt><code>--restore=<var>dribble-file</var></code></dt>
<dd><span id="index-_002d_002drestore-command-line-option"></span>
<span id="index-replaying-recorded-keystrokes"></span>
<p>Read keystrokes from <var>dribble-file</var>, presumably recorded during
previous Info session (see the description of the ‘<samp>--dribble</samp>’
option above). When the keystrokes in the files are all read, Info
reverts its input to the usual interactive operation.
</p>
</dd>
<dt><code>--show-malformed-multibytes</code></dt>
<dt><code>--no-show-malformed-multibytes</code></dt>
<dd><span id="index-_002d_002dshow_002dmalformed_002dmultibytes-command-line-option"></span>
<span id="index-malformed-multibyte-sequences_002c-showing"></span>
<p>Show malformed multibyte sequences in the output. By default, such
sequences are dropped.
</p>
<span id="g_t_002d_002dshow_002doptions"></span></dd>
<dt><code>--show-options</code></dt>
<dt><code>--usage</code></dt>
<dt><code>-O</code></dt>
<dd><span id="index-_002d_002dshow_002doptions-_0028_002d_002dusage_002c-_002dO_0029-command-line-option"></span>
<span id="index-command_002dline-options_002c-how-to-find"></span>
<span id="index-invocation-description_002c-how-to-find"></span>
<p>Tell Info to look for the node that describes how to invoke the
program and its command-line options, and begin the session by
displaying that node. It is provided to make it easier to find the
most important usage information in a manual without navigating
through menu hierarchies. The effect is similar to the <code>M-x
goto-invocation</code> command (see <a href="Node-Commands.html#goto_002dinvocation">goto-invocation</a>) from inside Info.
</p>
</dd>
<dt><code>--speech-friendly</code></dt>
<dt><code>-b</code></dt>
<dd><span id="index-_002d_002dspeech_002dfriendly-_0028_002db_0029-command-line-option"></span>
<span id="index-speech-synthesizers"></span>
<p>On MS-DOS/MS-Windows only, this option causes Info to use standard
file I/O functions for screen writes. (By default, Info uses direct
writes to the video memory on these systems, for faster operation and
colored display support.) This allows the speech synthesizers used by
blind persons to catch the output and convert it to audible speech.
</p>
</dd>
<dt><code>--strict-node-location</code></dt>
<dd><span id="index-_002d_002dstrict_002dnode_002dlocation-command-line-option"></span>
<p>This option causes Info not to search “nearby” to locate nodes, and
instead strictly use the information provided in the Info file. The
practical use for this option is for debugging programs that write
Info files, to check that they are outputting the correct locations.
Due to bugs and malfeasances in the various Info writing programs over
the years and versions, it is not advisable to ever use this option
when just trying to read documentation.
</p>
</dd>
<dt><code>--subnodes</code></dt>
<dd><span id="index-_002d_002dsubnodes_002c-command-line-option"></span>
<p>This option only has meaning when given in conjunction with
<code>--output</code>. It means to recursively output the nodes appearing in
the menus of each node being output. Menu items which resolve to
external Info files are not output, and neither are menu items which are
members of an index. Each node is only output once.
</p>
<span id="variable_002dassignment"></span></dd>
<dt><code>-v <var>name</var>=<var>value</var></code></dt>
<dt><code>--variable=<var>name</var>=<var>value</var></code></dt>
<dd><span id="index-_002d_002dvariable-_0028_002dv_0029-command-line-option"></span>
<span id="index-variable-assignment"></span>
<p>Set the <code>info</code> variable <var>name</var> to <var>value</var>.
See <a href="Variables.html">Variables</a>.
</p>
</dd>
<dt><code>--version</code></dt>
<dd><span id="index-_002d_002dversion-command-line-option"></span>
<span id="index-version-information"></span>
<p>Prints the version information of Info and exits.
</p>
<span id="g_t_002d_002dvi_002dkeys"></span></dd>
<dt><code>--vi-keys</code></dt>
<dd><span id="index-_002d_002dvi_002dkeys-command-line-option"></span>
<span id="index-vi_002dlike-key-bindings"></span>
<span id="index-Less_002dlike-key-bindings"></span>
<p>This option binds functions to keys differently, to emulate the key
bindings of <code>vi</code> and Less. The bindings activated by this option
are documented in <a href="infokey-format.html"><tt>infokey</tt> format</a>. (See <a href="Custom-Key-Bindings.html">Custom Key Bindings</a>
for a more general way of altering GNU Info’s key bindings.)
</p>
</dd>
<dt><code>--where</code></dt>
<dt><code>--location</code></dt>
<dt><code>-w</code></dt>
<dd><span id="index-_002d_002dwhere-_0028_002d_002dlocation_002c-_002dw_0029-command-line-option"></span>
<span id="index-Info-manual-location"></span>
<span id="index-Where-is-an-Info-manual_003f"></span>
<p>Show the filename that would be read and exit, instead of actually
reading it and starting Info.
</p></dd>
</dl>
<p>Finally, Info defines many default key bindings and variables.
See <a href="Custom-Key-Bindings.html">Custom Key Bindings</a> for information on how to customize these
settings.
</p>
<div class="footnote">
<hr>
<h4 class="footnotes-heading">Footnotes</h4>
<h5><a id="FOOT1" href="#DOCF1">(1)</a></h3>
<p>On MS-DOS, Info allows for the Info
extension, such as <code>.inf</code>, and the short compressed file extensions,
such as <samp>.z</samp> and <samp>.gz</samp>, to be merged into a single extension,
since DOS doesn’t allow more than a single dot in the basename of
a file. Thus, on MS-DOS, if Info looks for <samp>bison</samp>, file names
like <samp>bison.igz</samp> and <samp>bison.inz</samp> will be found and decompressed
by <code>gunzip</code>.</p>
</div>
<hr>
<div class="header">
<p>
Next: <a href="Cursor-Commands.html" accesskey="n" rel="next">Cursor Commands</a>, Previous: <a href="Stand_002dalone-Info.html" accesskey="p" rel="prev">Stand-alone Info</a>, Up: <a href="index.html" accesskey="u" rel="up">Top</a> [<a href="index.html#SEC_Contents" title="Table of contents" rel="contents">Contents</a>][<a href="Index.html" title="Index" rel="index">Index</a>]</p>
</div>
</body>
</html>
AnonSec - 2021 | Recode By D7net