option_help.html

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

recover from errors, but there is no universally correct way for doing
this.  As a result, there are two parsing modes:
"<DFN>SortaSGML</DFN>" attempts to enforce valid nesting of most tags
at an earlier stage of processing, while "<DFN>TagSoup</DFN>" relies
more on the HTML rendering stage to mimic the behavior of some other
browsers.
You can also switch between these modes with the CTRL-V key, and the
default can be changed in lynx.cfg or with the -tagsoup command line
switch.

<P>
The "SortaSGML" mode will often appear to be more strict, and makes
some errors apparent that are otherwise unnoticeable.  One particular
difference is the handling of block elements or
&lt;li&gt;..&lt;/li&gt; inside &lt;a HREF="some.url"&gt;..&lt;/a&gt;.
Invalid nesting like this may turn anchors into hidden links which
cannot be easily followed, this is avoided in "TagSoup" mode.  See the
<a href="follow_help.html">help on following links by
number</a> for more information on hidden links.  Often pages may be
more readable in "TagSoup" mode, but sometimes the opposite is true.
Most documents with valid HTML, and documents with only minor errors,
should be rendered the same way in both modes.

<P>
If you are curious about what goes on behind the scenes, but find that
the information from the -trace switch is just too much, Lynx can be
started with the -preparsed switch; going into SOURCE mode ('\' key)
and toggling the parsing mode (with CTRL-V) should then show some of
the differences.

<!--
LP's version - for reference - TD

While the proper HTML markup should be canonical, badly nested HTML pages
may be recovered in different ways.  There are two error recovery modes
in Lynx: SortaSGML with the recovery at SGML stage and TagSoup mode
with the recovery at HTML parsing stage, the latter gives more
recovery and was the default in Lynx 2.7.2 and before,
and the first may be useful for page validation purposes.
One particular difference is known for &lt;li&gt;..&lt;/li&gt;
or similar strong markup inside &lt;a HREF="some.url"&gt;..&lt;/a&gt;
anchor text - those links are not reachable in SortaSGML
(such markup should be placed outside &lt;a&gt;..&lt;/a&gt; indeed).
Default recovery mode can also be switched with CTRL-V key,
from lynx.cfg or command line switch.
-->


<H1><A NAME="SI">Show Images</A></H1>

This option combines the effects of the `*' &amp; `[' keys as follows:
<pre>
     <em>ignore</em> all images which lack an ALT= text string,
     <em>show labels</em>, e.g. [INLINE] -- see `Verbose Images' below -- ,
     <em>use links</em> for every image, enabling downloading.
</pre><p>
This option setting cannot be saved between sessions.
See <A HREF="../Lynx_users_guide.html#Images">Users Guide</A>
&amp; <em>lynx.cfg</em> for more details.

<H1><A NAME="VB">Verbose Images</A></H1>

This allows you to replace [LINK], [INLINE] and [IMAGE]
-- for images without ALT -- with filenames:
this can be helpful by revealing which images are important
&amp; which are merely decoration, e.g. <em>button.gif</em>, <em>line.gif</em>.
See <A HREF="../Lynx_users_guide.html#Images">Users Guide</A>
&amp; <em>lynx.cfg</em> for more details.


<H1><A NAME="VI">VI keys</A></H1>

If set to 'ON' then the lowercase h, j, k and l keys will be mapped
to left-arrow, down-arrow, up-arrow and right-arrow respectively.
<p>The uppercase H, J, K, and L keys remain mapped to their configured bindings
(normally HELP, JUMP, KEYMAP and LIST, respectively).
<p>Note: setting vi keys does not affect the line-editor bindings.

<H1><A NAME="DC">Display Character set</A></H1>

This allows you to set up the default character set for your specific terminal.
The display character set provides a mapping from the character encodings
of viewed documents and from HTML entities into viewable characters.
It should be set according to your terminal's character set
so that characters other than 7-bit ASCII can be displayed correctly,
using approximations if necessary,
<A HREF="test_display.html">try the test here</A>.
Since Lynx now supports a wide range of platforms
it may be useful to note that cpXXX codepages are used within IBM PC computers,
and windows-xxxx within native MS-Windows applications.

<H1><A NAME="DV">X DISPLAY variable</A></H1>

This option is only relevant to X Window users. It specifies
the DISPLAY (Unix) or DECW$DISPLAY (VMS) variable.  It is picked up
automatically from the environment if it has been previously set.

<H1><A NAME="MB">Multi-bookmarks</A></H1>

Manage multiple bookmark files:
<ul>
<li>When OFF, the default bookmark file is used for the 'v'iew-bookmarks
and 'a'dd-bookmark link commands.
<li>If set to STANDARD, a menu of available
bookmarks is always invoked when you seek to view a bookmark file
or add a link, and you select the bookmark file by its letter token
in that menu.
<li>If set to ADVANCED, you are instead prompted for the letter
of the desired bookmark file, but can enter '=' to invoke the STANDARD
selection menu, or RETURN for the default bookmark file.
</ul>

<H1><A NAME="BF">Bookmark file</A></H1>

Manage the default bookmark file:
<ul>
<li>If non-empty and multi-bookmarks is OFF,
it specifies your default '<A HREF="bookmark_help.html">Bookmark file</A>'.
<li>If multi-bookmarks is STANDARD or ADVANCED,
entering 'B' will invoke a menu in which you can specify
filepaths and descriptions of up to 26 bookmark files.
</ul>
The filepaths must be from your home directory and begin with  './'
if subdirectories are included (e.g., './BM/lynx_bookmarks.html').
<P>
Lynx will create bookmark files when you first 'a'dd a link,
but any subdirectories in the filepath must already exist.

<H1><A NAME="VP">Visited Pages</A></H1>

This allows you to change the appearance of the
<a href="visited_help.html">Visited Links Page</a>

Normally it shows a list, in reverse order of the pages visited.
The popup menu allows you these choices:
<dl>
<dt><EM>By First Visit</EM>:
The default appearance, shows the pages based on when they were first visited.
The list is shown in reverse order, to make the current page (usually) at
the top of the list.
<dt><EM>By First Visit Reversed</EM>
The default appearance, shows the pages based on when they were first visited.
The list is shown in order, to make the current page (usually) at
the bottom of the list.
<dt><EM>As Visit Tree</EM>
Combines the first/last visited information, showing the list in order of
the first visit, but using the indentation level of the page immediately
previous to determine indentation of new entries.
That gives a clue to the order of visiting pages when moving around in
the History or Visited Pages lists.
<dt><EM>By Last Visit</EM>
The default appearance, shows the pages based on when they were last visited.
The list is shown in reverse order, to make the current page (usually) at
the top of the list.
<dt><EM>By Last Visit Reversed</EM>
The default appearance, shows the pages based on when they were last visited.
The list is shown in order, to make the current page (usually) at
the bottom of the list.
</dl>

<H1><A NAME="FT">FTP sort criteria</A></H1>

This allows you to specify how files will be sorted within FTP listings.
The current options include
`By&nbsp;Filename', `By&nbsp;Size', `By&nbsp;Type', `By&nbsp;Date'.

<H1><A NAME="LD">List directory style</A></H1>

Applies to Directory Editing.
Files and directories can be presented in the following ways:
<dl>
<dt><EM>Mixed style</EM>: Files and directories are listed together
in alphabetical order.
<dt><EM>Directories first</EM>: Files and directories are separated
into 2 alphabetical lists: directories are listed first.
<dt><EM>Files first</EM>: Files and directories are separated
into 2 alphabetical lists: files are listed first.
</dl>

<H1><A NAME="DF">Show dot files</A></H1>

If display/creation of hidden (dot) files/directories is enabled,
you can turn the feature on or off via this setting.

<H1><A NAME="PC">Preferred Document Charset</A></H1>

The character set you prefer if sets in addition to ISO-8859-1 and US-ASCII
are available from servers.  Use MIME notation (e.g., ISO-8859-2)
and do not include ISO-8859-1 or US-ASCII, since those values are always
assumed by default.  Can be a comma-separated list, which may be interpreted
by servers as descending order of preferences; you can make your order
of preference explicit by using `q factors' as defined by the HTTP protocol,
for servers which understand it: e.g., <kbd>iso-8859-5, utf-8;q=0.8</kbd>.

<H1><A NAME="PL">Preferred Document Language</A></H1>

The language you prefer if multi-language files are available from servers.
Use RFC 1766 tags, e.g., `en' English, `fr' French.  Can be a comma-separated
list, and you can use `q factors' (see previous help item):
e.g., <kbd>da, en-gb;q=0.8, en;q=0.7</kbd> .

<H1><A NAME="UA">User Agent</A></H1>

The header string which Lynx sends to servers to indicate the User-Agent
is displayed here.  Changes may be disallowed via the -restrictions switch.
Otherwise, the header can be changed temporarily to e.g., L_y_n_x/2.8.3
for access to sites which discriminate against Lynx based on checks
for the presence of `Lynx' in the header.  If changed during a Lynx session,
the default User-Agent header can be restored by deleting the modified string
in the Options Menu.  Whenever the User-Agent header is changed, the current
document is reloaded, with the no-cache flags set, on exit from Options Menu.
Changes of the header are not saved in the .lynxrc file.
<P>
NOTE Netscape Communications Corp. has claimed that false transmissions
of `Mozilla' as the User-Agent are a copyright infringement, which will
be prosecuted.  DO NOT misrepresent Lynx as Mozilla.  The Options Menu issues
a warning about possible copyright infringement whenever the header is changed
to one which does not include `Lynx' or `lynx'.

</BODY>
</HTML>