lynx_users_guide.html

一个可用于linux下的命令行音乐播放器

The process of moving within a hypertext web, selecting and displaying
links is known as "navigation." With Lynx almost all navigation can be
accomplished with the arrow keys and the numeric keypad.
<pre>
                                       +-------+-------+-------+
                                       | TOP   |  /|\  | Page  |
              arrow keys               | of    |   |   | UP    |
                                       | text 7|   |  8|      9|
              +---------+              +-------+-------+-------+
              | SELECT  |              |       |       |       |
              | prev /|\|              | &lt;---  |       |  ---&gt; |
              | link  | |              |      4|      5|      6|
    +---------+---------+---------+    +-------+-------+-------+
    |    BACK | SELECT  | DISPLAY |    | END   |   |   | Page  |
    |&lt;-- prev | next  | | sel. --&gt;|    | of    |   |   | DOWN  |
    |    doc. | link \|/| link    |    | text 1|  \|/ 2|      3|
    +---------+---------+---------+    +-------+-------+-------+
</pre>

There are also a few other keyboard commands to aid in navigation.  The
Control and Function keys used for navigation within the current document
are described in <A
HREF="#MiscKeys"><em>Scrolling and Other useful commands</em></A>.  Some
additional commands depend on the fact that Lynx keeps a list of each
link you visited to reach the current document, called the <a
href="keystrokes/history_help.html">History Page</a>, and a
list of all links visited during the current Lynx session, called the <a
href="keystrokes/visited_help.html">Visited Links Page</a>.  The
HISTORY keystroke command, normally mapped to <em>Backspace</em> or
<em>Delete</em>, will show you the <em>History Page</em> of links leading to
your access of the current document.  Any of the previous documents shown in
the list may be revisited by selecting them from the history screen.  The
VLINKS keystroke command, normally mapped to uppercase '<em>V</em>', will
show the <em>Visited Links Page</em>, and you similarly can select links in
that list.  The MAIN_MENU keystroke command, normally mapped to '<em>m</em>'
and '<em>M</em>', will take you back to the starting document unless you
specified the <em>-homepage=URL</em> option at the command line.  Also, the
LIST and ADDRLIST keystroke commands, normally mapped to '<em>l</em>' and
<em>A</em>' respectively, will create a compact lists of all the links in
the current document, and they can be selected via those lists.

<p>The '<em>i</em>' key presents an index of documents.  The default index
offered contains many useful links, but can be changed in <em>lynx.cfg</em>
or on the command line using the <em>-index=URL</em> switch.

<p>If you choose a link to a server with active access authorization, Lynx
will automatically prompt for a username and a password. If you give the
correct information, you will then be served the requested information.
Lynx will automatically send your username and password to the same server
if it is needed again. [<A HREF="#ToC-IntraDocNav">ToC</A>]

<h2 ID="Disposing"><A NAME="Disposing"
><em>Printing, Mailing, and Saving rendered files to disk.</em></A></h2>

Rendered HTML documents, and plain text files, may be printed using the
'<em>p</em>' command while viewing the document.  After pressing the
'<em>p</em>' key a menu of <em>Print Options</em> will be displayed.  The
menu will vary according to several factors.  First, some sites set up
special accounts to let users run Lynx to access local information systems.
Typically these accounts require no passwords and do not require users to
identify themselves.  As a result such accounts are called "anonymous"
accounts, and their users are considered "anonymous" users.  In most
configurations, all Lynx users (including anonymous users) are able to
mail files to themselves and print the entire file to the screen.

<p>Additional print options are available for users who are using
Lynx from their own accounts (that is, so-called "non-anonymous
users").  In particular, the <em>Save to a local file</EM>
option allows you to save the document into a file on your disk
space.  Additional print options may also be
available as configured in the <A HREF="#lynx.cfg">lynx.cfg</A> file.

<p>Some options, such as <em>Save to a local file</em>, involve prompting
for an output filename.  All output filename entries are saved in a
circular buffer, and any previous entries can be retrieved for re-use by
pressing the <em>up-arrow</em> or <em>down-arrow</em> keys at the prompt.

<p>Note that if you want exact copies of text files without any expansions
of TAB characters to spaces you should use the
<a href="#RemoteSource">Download</a> options.
[<A HREF="#ToC-Disposing">ToC</A>]

<h2 ID="LocalSource"><A NAME="LocalSource"
><em>Viewing the HTML document source and editing documents</em></A></h2>

When viewing HTML documents it is possible to retrieve and display the
unrendered (i.e., the original HTML) source of the document by pressing
the '<em>\</em>' (backslash) key.  Lynx usually caches only the rendering
of the document and doesn't keep the source (unless it is configured to do
so in the <A HREF="#lynx.cfg">lynx.cfg</A> file), so to display the source
unrendered, Lynx must reload it from the server or disk.
When viewing unrendered documents you may print them as any normal document.

<p>Selecting the <em>Print to a local file</em> option from the Print Menu,
makes it possible to save the source of the document to disk so that you
may have a local copy of the document source, but it is better to <a
href="#RemoteSource">Download</a> the source.

<p>NOTE: When saving an HTML document it is important to name the
document with a <em>.html</em> or <em>.htm</em> extension, if you
want to read it with Lynx again later.

<p ID="FileEdit">Lynx can allow users to edit documents that reside on the
local system.  To enable editing, documents must be referenced using a
"file:" URL or by specifying a plain filename on the command line as
in the following two examples:

<dl>
<dt>Command
    <dd><code>lynx file://localhost/FULL/PATH/FILENAME</code>
    <dd><code>lynx path/filename.html</code>
</dl>

In addition, the user must also specify an editor in the
<em>Options Menu</em> so that Lynx knows which editor to use.  If the
file is specified correctly and an editor is defined, then you may edit
documents by using the '<em>e</em>' command.  When the '<em>e</em>'
command is entered your specified editor is spawned to edit the file.
After changes are completed, exit your editor and you will return to Lynx.
Lynx will reload and render the file so that changes can be immediately
examined. [<A HREF="#ToC-LocalSource">ToC</A>]

<h2 ID="RemoteSource"><A NAME="RemoteSource"><em>Downloading and Saving source files.</em></A></h2>

If the DOWNLOAD keystroke command ('<em>d</em>' or <em>D</em>) is
used when positioned on a link for an HTML, plain text, or binary
file, Lynx will transfer the file, without rendering, into a
temporary location and present the user with a list of options,
just as it does when a link for a binary file of a type for which
no viewer has been mapped is activated.

<P>There is a default <em>Download option</em> of <em>Save to
disk</em>.  This is disabled if Lynx is running in anonymous
mode.  Any number of download methods such as kermit and zmodem
may be defined in addition to this default in the
<em>lynx.cfg</em> file.  Using the <em>Save to disk</em> option
under the PRINT command after viewing the source of an HTML with
the VIEW SOURCE (<em>\</em>) command will result in a file which
differs from the original source in various ways such as tab
characters expanded to spaces.  Lynx formats the source presentation
in this mode.  On the other hand, if the DOWNLOAD command is used,
the only change will be that Lynx optionally puts
<blockquote>
&lt;!--X-URL: http://www.site.foo/path/to/file.html --&gt;<BR>
&lt;BASE href="http://www.site.foo/path/to/file.html"&gt;
</blockquote>
at the start of the file so that relative URLs in the document
will still work.

Even this modification can be prevented by setting
PREPEND_BASE_TO_SOURCE:FALSE in lynx.cfg.

<p>Some options, such as <em>Save to disk</em>, involve prompting for an
output filename.  All output filename entries are saved in a circular buffer,
and any previous entries can be retrieved for re-use by pressing the
<em>up-arrow</em> or <em>down-arrow</em> keys at the prompt.
[<A HREF="#ToC-RemoteSource">ToC</A>]

<h2 ID="ReDo"><A NAME="ReDo"
><em>Reloading files and refreshing the display</em></A></h2>

The RELOAD (<em>Control-R</em>) command will reload and re-render the file
that you are currently viewing.  The REFRESH (<em>Control-L</em> or
<em>Control-W</em>) command will refresh or wipe the screen to remove or
correct any errors that may be caused by operating system or other messages.

<p>The NOCACHE ('<em>x</em>' or '<em>X</em>') command can be used in lieu
of ACTIVATE (<em>Return</em> or <em>right-arrow</em>) to request an uncached
copy and new rendition for the current link, or resubmission of a FORM, if a
cache from a previous request or submission exits.  The request or submission
will include <em>Pragma: no-cache</em> and <em>Cache-Control: no-cache</em>
in its headers.  Note that FORMs with POST content will be resubmitted
regardless of whether the NOCACHE or ACTIVATE command is used (see <A
HREF="#Forms"><em>Lynx and HTML Forms</em></A>).
[<A HREF="#ToC-ReDo">ToC</A>]

<h2 ID="Search"><A NAME="Search"><em>Lynx searching commands</em></A></h2>

Two commands activate searching in Lynx: '<em>/</em>' and '<em>s</em>'.

<p>While viewing a normal document use the '<em>/</em>' command
to find a word or phrase within the current document.  The search
type will depend on the search option setting in the <a
href="#InteractiveOptions">Options Menu</a>.  The search options
are case sensitive and case insensitive.  These searches are
entirely local to Lynx.

<p>Some documents are designated <em>index documents</em> by virtue of an
ISINDEX element in their HEAD section.  These documents can be used to
retrieve additional information based on searches using words or phrases
submitted to an index server.  The Lynx statusline will indicate that you
are viewing such a document, and if so, the '<em>s</em>' key will invoke a
statusline prompt to enter a query string.  The prompt can be specified via
a PROMPT attribute in the ISINDEX element.  Otherwise, Lynx will use an
internally configured prompt.  The address for submitting the search can be
specified via an HREF or ACTION attribute.  Otherwise, Lynx will use the
current document's URL and append your query string as a <em>?searchpart</em>
(see <a href="lynx_url_support.html">Supported URLs</a>).

<p>All search words or strings which you have entered during a Lynx session
are saved in a circular buffer, and can be retrieved for re-use by pressing
the <em>up-arrow</em> or <em>down-arrow</em> keys at the prompt for a search
word or string.  Also, you can use the '<em>n</em>'ext command to repeat a
search with the last-entered search word or phrase, starting from the current
position in the document.  The word or phrase matches will be highlighted
throughout the document, but such highlighting will not persist for new
documents, or if the current document is reloaded.  The search cycles to the
top of the document if the word or phrase is not located below your current
position.

<p>Although <a href="#Forms">HTML Forms</a> have largely replaced index
documents for searches via http servers, they are still useful for performing
searches directly via WAIS or Gopher servers in conjunction with the internal
gateways for such servers.  For example, an HTML index document can act as a
<em>cover page</em> describing a WAIS database and how to formulate query
strings for searching it, and include an element such as:<BR>
<pre>
      <em>&lt;ISINDEX PROMPT="Enter WAIS query:"
               HREF="wais://net.bio.net/biologists-addresses"&gt;</em>
</pre>
for submitting a search of the Biologist's Addresses database directly
to the net.bio.net WAIS server. [<A HREF="#ToC-Search">ToC</A>]

<h2 ID="InteractiveOptions"><A NAME="InteractiveOptions"><em>Lynx Options Menu</em></A></h2>

The Lynx <em>Options Menu</em> may be accessed by pressing the '<em>o</em>'
key. It allows you to change options at runtime, if you need to.
Most changes are read from &amp; saved to your .lynxrc file; those which are not
are marked (!) in the form-based menu (as below). Many other options
are stored in the <A HREF="#lynx.cfg">lynx.cfg</A> file.

<p>Lynx supports two styles of Options Menu, key-based &amp; form-based.
The form-based menu shown below is an HTML file generated at runtime,
in which the user fills in choices as in any ordinary HTML form.
<pre>

                    Options Menu (Lynx Version 2.8.5dev.15)

      Accept Changes - Reset Changes Left Arrow cancels changes <A
HREF="keystrokes/option_help.html">HELP!</A>

                         Save options to disk: [_]
                (options marked with (!) will not be saved)

  General Preferences
  User mode                        : [Advanced....]
  Editor                           : __________________________________________
  Type of Search                   : [Case insensitive]

  Security and Privacy
  Cookies (!)                      : [ask user..]
  Invalid-Cookie Prompting (!)     : [prompt normally___]
  SSL Prompting (!)                : [prompt normally___]

  Keyboard Input