diff options
| author | Thomas E. Dickey <dickey@invisible-island.net> | 2012-02-01 00:05:07 -0500 |
|---|---|---|
| committer | Thomas E. Dickey <dickey@invisible-island.net> | 2012-02-01 00:05:07 -0500 |
| commit | 21dd45fc8fe8ba9b7bb06f34f5b7d73597594220 (patch) | |
| tree | 83b30982738da178b9807f86221ebd04f86018dd /lynx_help/keystrokes | |
| parent | f72f57417250699efc900813c898c900e5b5fd9e (diff) | |
| download | lynx-snapshots-21dd45fc8fe8ba9b7bb06f34f5b7d73597594220.tar.gz | |
snapshot of project "lynx", label v2-8-8dev_9f
Diffstat (limited to 'lynx_help/keystrokes')
| -rw-r--r-- | lynx_help/keystrokes/alt_edit_help.html | 52 | ||||
| -rw-r--r-- | lynx_help/keystrokes/bashlike_edit_help.html | 139 | ||||
| -rw-r--r-- | lynx_help/keystrokes/bookmark_help.html | 58 | ||||
| -rw-r--r-- | lynx_help/keystrokes/cookie_help.html | 101 | ||||
| -rw-r--r-- | lynx_help/keystrokes/dired_help.html | 40 | ||||
| -rw-r--r-- | lynx_help/keystrokes/edit_help.html | 52 | ||||
| -rw-r--r-- | lynx_help/keystrokes/environments.html | 33 | ||||
| -rw-r--r-- | lynx_help/keystrokes/follow_help.html | 344 | ||||
| -rw-r--r-- | lynx_help/keystrokes/gopher_types_help.html | 142 | ||||
| -rw-r--r-- | lynx_help/keystrokes/history_help.html | 78 | ||||
| -rw-r--r-- | lynx_help/keystrokes/keystroke_help.html | 98 | ||||
| -rw-r--r-- | lynx_help/keystrokes/movement_help.html | 33 | ||||
| -rw-r--r-- | lynx_help/keystrokes/option_help.html | 938 | ||||
| -rw-r--r-- | lynx_help/keystrokes/other_help.html | 71 | ||||
| -rw-r--r-- | lynx_help/keystrokes/print_help.html | 86 | ||||
| -rw-r--r-- | lynx_help/keystrokes/scrolling_help.html | 33 | ||||
| -rw-r--r-- | lynx_help/keystrokes/test_display.html | 2 | ||||
| -rw-r--r-- | lynx_help/keystrokes/visited_help.html | 73 | ||||
| -rw-r--r-- | lynx_help/keystrokes/xterm_help.html | 76 |
19 files changed, 1366 insertions, 1083 deletions
diff --git a/lynx_help/keystrokes/alt_edit_help.html b/lynx_help/keystrokes/alt_edit_help.html index ab577a16..690537a0 100644 --- a/lynx_help/keystrokes/alt_edit_help.html +++ b/lynx_help/keystrokes/alt_edit_help.html @@ -1,28 +1,38 @@ -<!DOCTYPE html PUBLIC "-//IETF//DTD HTML 3.0//EN"> +<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 3.2//EN"> +<!-- $LynxId: alt_edit_help.html,v 1.9 2012/01/31 23:22:53 tom Exp $ --> + <html> <head> -<title>Lynx Line Editor Alternative Key Binding</title> -<link rev="made" href="mailto:lynx-dev@nongnu.org"> -<link rel="Sibling" title="Default Binding" href="edit_help.html"> -<link rel="Sibling" title="Bash-Like Binding" href="bashlike_edit_help.html"> -<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1"> + <meta name="generator" content= + "HTML Tidy for Linux/x86 (vers 6 November 2007), see www.w3.org"> + + <title>Lynx Line Editor Alternative Key Binding</title> + <link rev="made" href="mailto:lynx-dev@nongnu.org"> + <link rel="Sibling" title="Default Binding" href= + "edit_help.html"> + <link rel="Sibling" title="Bash-Like Binding" href= + "bashlike_edit_help.html"> + <meta http-equiv="Content-Type" content= + "text/html; charset=us-ascii"> </head> -<body> -<h1>+++ALTERNATIVE BINDING+++</h1> -Lynx invokes a built-in <em>Line Editor</em> for entering strings in -response to prompts, in forms, and for email messages if an external editor -has not been defined. Additional alternative key-bindings can be offered -by configuring with --enable-alt-bindings or by adding them in -LYEditmap.c before compiling Lynx. If available, -they may be selected via the 'o'ptions menu, or by editing lineedit_mode in -the '.lynxrc' file. +<body> + <h1>ALTERNATIVE BINDING</h1> -<p>Note: setting emacs/vi keys ON has no direct effect on line-editor bindings. + <p>Lynx invokes a built-in <em>Line Editor</em> for entering + strings in response to prompts, in forms, and for email messages + if an external editor has not been defined. Additional + alternative key-bindings can be offered by configuring with + --enable-alt-bindings or by adding them in LYEditmap.c before + compiling Lynx. If available, they may be selected via the + 'o'ptions menu, or by editing lineedit_mode in the '.lynxrc' + file.</p> -<p>This is the <em>Alternative Binding</em> keymap: + <p>Note: setting emacs/vi keys ON has no direct effect on + line-editor bindings.</p> -<pre> + <p>This is the <em>Alternative Binding</em> keymap:</p> + <pre> ENTER Input complete - RETURN TAB Input complete - TAB, Do ABORT Input cancelled - Ctrl-G, Ctrl-O, (Ctrl-C on some systems) @@ -46,7 +56,8 @@ the '.lynxrc' file. LKCMD Invoke cmd prompt - Ctrl-V (in form text fields, only) [2] -<A NAME="TASpecial">Special commands for use only in textarea fields</A>[3]: +<a name= +"TASpecial">Special commands for use only in textarea fields</a>[3]: Textarea external edit - Ctrl-X e Insert file in textarea - Ctrl-X i @@ -61,8 +72,7 @@ the '.lynxrc' file. [3] For other key combinations using Ctrl-X as a prefix key, see the Help page for the <a rel="Sibling" title="Bash-Like Binding" - href="bashlike_edit_help.html" - >Bash-Like</a> Binding. +href="bashlike_edit_help.html">Bash-Like</a> Binding. </pre> </body> </html> diff --git a/lynx_help/keystrokes/bashlike_edit_help.html b/lynx_help/keystrokes/bashlike_edit_help.html index 79a8c2c6..14a3a4ff 100644 --- a/lynx_help/keystrokes/bashlike_edit_help.html +++ b/lynx_help/keystrokes/bashlike_edit_help.html @@ -1,28 +1,40 @@ -<!DOCTYPE html PUBLIC "-//IETF//DTD HTML 3.0//EN"> +<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 3.2//EN"> +<!-- $LynxId: bashlike_edit_help.html,v 1.8 2012/01/31 23:21:55 tom Exp $ --> + <html> <head> -<title>Lynx Line Editor Bash-Like Key Binding</title> -<link rev="made" href="mailto:lynx-dev@nongnu.org"> -<link rel="Sibling" title="Default Binding" href="edit_help.html"> -<link rel="Sibling" title="Alternative Binding" href="alt_edit_help.html"> -<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1"> + <meta name="generator" content= + "HTML Tidy for Linux/x86 (vers 6 November 2007), see www.w3.org"> + + <title>Lynx Line Editor Bash-Like Key Binding</title> + <link rev="made" href="mailto:lynx-dev@nongnu.org"> + <link rel="Sibling" title="Default Binding" href= + "edit_help.html"> + <link rel="Sibling" title="Alternative Binding" href= + "alt_edit_help.html"> + <meta http-equiv="Content-Type" content= + "text/html; charset=us-ascii"> </head> + <body> -<h1>+++BASH-LIKE BINDING+++</h1> + <h1>BASH-LIKE BINDING</h1> -Lynx invokes a built-in <em>Line Editor</em> for entering strings in -response to prompts, in forms, and for email messages if an external editor -has not been defined. Several sets of key-bindings can be offered -by configuring with --enable-alt-bindings or by adding them in -LYEditmap.c before compiling Lynx. If available, -they may be selected via the 'o'ptions menu, or by editing lineedit_mode in -the '.lynxrc' file. + <p>Lynx invokes a built-in <em>Line Editor</em> for entering + strings in response to prompts, in forms, and for email messages + if an external editor has not been defined. Several sets of + key-bindings can be offered by configuring with + --enable-alt-bindings or by adding them in LYEditmap.c before + compiling Lynx. If available, they may be selected via the + 'o'ptions menu, or by editing lineedit_mode in the '.lynxrc' + file.</p> -<p>Note: setting emacs/vi keys ON has no direct effect on line-editor bindings. + <p>Note: setting emacs/vi keys ON has no direct effect on + line-editor bindings.</p> -<p>This is the <em>Bash-like Binding</em> keymap.</p> -<h2>Basic commands</h2> -<pre> + <p>This is the <em>Bash-like Binding</em> keymap.</p> + + <h2>Basic commands</h2> + <pre> ENTER Input complete - Enter, RETURN TAB Completion [2]/ Next - TAB, Do ABORT Cancel / Undo Change - C-g, C-_ @@ -48,21 +60,25 @@ the '.lynxrc' file. LKCMD Invoke cmd prompt - C-v [FORM] SWMAP Switch input keymap - C-^ (if compiled in) -<A NAME="TASpecial">Special commands for use in textarea fields</A> [FORM]: +<a name= +"TASpecial">Special commands for use in textarea fields</a> [FORM]: PASS! Textarea external edit - C-e C-e [4], C-x e PASS! Insert file in textarea - C-x i PASS! Grow textarea - C-x g - </pre> -Here is a little textarea for practice:<BR> -<FORM action=""><TEXTAREA name="practice" cols=40 ROWS=5> + + <p>Here is a little textarea for practice:<br></p> + + <form action=""> + <textarea name="practice" cols="40" rows="5"> This text cannot be submitted. Normally lines like these would be part of a form that is filled out and then submitted. You can move around here and delete or add text as you like, using the Line-Editor keys. -</TEXTAREA><INPUT TYPE=reset VALUE="[reset content]"></FORM> -<pre> +</textarea><input type="reset" value="[reset content]"> + </form> + <pre> Advanced emacs-like commands: @@ -72,32 +88,39 @@ Advanced emacs-like commands: KILLREG Kill region between mark and position - C-x C-w [3] YANK Insert text last killed (with KILLREG) - C-y </pre> -<h2>Notes</h2> -<P><samp> - <DFN>C-</DFN><strong>key</strong> means Control+<strong><kbd>key</kbd></strong>. <DFN - ><code>C-x </code></DFN><strong>key</strong> means first Control+<kbd>x</kbd>, then - <strong><kbd>key</kbd></strong>. - <DFN - >M-</DFN>key means Meta+<strong><kbd>key</kbd></strong>, where Meta - is a modifier that can be entered in a variety of ways: -</samp></P><UL> -<LI>First ESC, then the <strong><kbd>key</kbd></strong>. - This doesn't work with all systems or on all connections, and if it - does may not work for some keys (because the ESC character is also - part of code sequences for "normal" function keys). -<LI>Alt+<strong><kbd>key</kbd></strong>. - This works if the terminal, console, or comm program is set up to - interpret Alt as a modifier to send ESC. The Linux console acts - like that by default for most keys; Kermit can be set up to do it, - xterm can be for some keys, and so on. But the same caveats as for - the previous item apply. - This Alt mapping may also be possible, independent of the ESC character, - for some keys in Lynx for DOS/i386 or for Win32. -<LI>C-x <strong><kbd>key</kbd></strong>. - Actually, currently the same internal table is used for Meta and the - C-x prefix. Therefore all M-<strong><kbd>key</kbd></strong> combinations can - also be typed as C-x <strong><kbd>key</kbd></strong>, and vice versa. -</UL><pre> + + <h2>Notes</h2> + + <p><samp><dfn>C-</dfn><strong>key</strong> means + Control+<strong><kbd>key</kbd></strong>. + <dfn><code>C-x</code></dfn> <strong>key</strong> means first + Control+<kbd>x</kbd>, then <strong><kbd>key</kbd></strong>. + <dfn>M-</dfn>key means Meta+<strong><kbd>key</kbd></strong>, + where Meta is a modifier that can be entered in a variety of + ways:</samp></p> + + <ul> + <li>First ESC, then the <strong><kbd>key</kbd></strong>. This + doesn't work with all systems or on all connections, and if it + does may not work for some keys (because the ESC character is + also part of code sequences for "normal" function keys).</li> + + <li>Alt+<strong><kbd>key</kbd></strong>. This works if the + terminal, console, or comm program is set up to interpret Alt + as a modifier to send ESC. The Linux console acts like that by + default for most keys; Kermit can be set up to do it, xterm can + be for some keys, and so on. But the same caveats as for the + previous item apply. This Alt mapping may also be possible, + independent of the ESC character, for some keys in Lynx for + DOS/i386 or for Win32.</li> + + <li>C-x <strong><kbd>key</kbd></strong>. Actually, currently + the same internal table is used for Meta and the C-x prefix. + Therefore all M-<strong><kbd>key</kbd></strong> combinations + can also be typed as C-x <strong><kbd>key</kbd></strong>, and + vice versa.</li> + </ul> + <pre> [1] "next" means the character "under" a box or underline style cursor; it means "to the immediate right of" an I-beam (between characters) type cursor. @@ -123,7 +146,6 @@ Advanced emacs-like commands: the benefit of those where this doesn't apply. [FORM] In form text fields, only. Ignored by Line Editor elsewhere. - More notes When a text input field, including a textarea line, is selected, @@ -131,14 +153,13 @@ More notes If a key has no function defined in the Line Editor binding, it can either be ignored, or passed on for normal key command handling, where modifiers like C-x or Meta currently have no effect (see the - <A HREF="LYNXKEYMAP:" - >Key Map Page</A> accessible with the key <kbd>K</kbd> for current information). - - + <a href= +"LYNXKEYMAP:">Key Map Page</a> accessible with the key <kbd>K</kbd> for current information). </pre> -<h2>Additional details on other keys, for the curious -(very much subject to change)</h2> -<pre> + + <h2>Additional details on other keys, for the curious (very much + subject to change)</h2> + <pre> Normal key action when used in form fields, subject to remapping with KEYMAP: [FORM (except Up-Arrow, Down-Arrow)] C-l [3], C-o, C-z [5], C-\ [5], C-] [5] @@ -204,8 +225,8 @@ Meta + other (mostly, printable character) keys: control (C1) range if appropriate according to Display Character Set. - [emacskey] Normal key action subject to emacs_keys setting. + [!] Action of key with Meta modifier follows action of key without Meta. If you manage to enter the Meta key while Line-Editor Binding is not set to Bash-Like, and the unmodified binding diff --git a/lynx_help/keystrokes/bookmark_help.html b/lynx_help/keystrokes/bookmark_help.html index f51ba9c0..df5adad1 100644 --- a/lynx_help/keystrokes/bookmark_help.html +++ b/lynx_help/keystrokes/bookmark_help.html @@ -1,22 +1,38 @@ -<!DOCTYPE html PUBLIC "-//IETF//DTD HTML 3.0//EN"> -<HTML> -<HEAD> -<TITLE>Lynx Bookmark Help</TITLE> -<LINK rev="made" href="mailto:lynx-dev@nongnu.org"> -<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1"> -</HEAD> -<BODY> -<h1>+++ Bookmark Help +++</h1> +<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 3.2//EN"> +<!-- $LynxId: bookmark_help.html,v 1.6 2012/01/31 11:00:10 tom Exp $ --> -The <em>Bookmark files</em> are documents that resides on your local -machine and you are able to edit and change. The append feature, -invoked by pressing an '<em>a</em>' while viewing a document will add -the current document or the currently highlighted link to your default -<em>Bookmark file</em>, or to one you select if multiple bookmarks are -enabled. The remove feature, invoked by pressing an '<em>r</em>' when -a <em>Bookmark file</em> is being displayed, will remove the currently -highlighted link. You may set and modify the paths and names of your -<em>Bookmark files</em> and enable or disable multiple bookmarks -in the <A HREF="option_help.html">Options Menu</A>. -</BODY> -</HTML> +<html> +<head> + <meta name="generator" content= + "HTML Tidy for Linux/x86 (vers 6 November 2007), see www.w3.org"> + + <title>Lynx Bookmark Help</title> + <link rev="made" href="mailto:lynx-dev@nongnu.org"> + <meta http-equiv="Content-Type" content= + "text/html; charset=us-ascii"> +</head> + +<body> + <h1>Bookmark Help</h1> + + <p><em>Bookmark files</em> are documents that reside on your + local machine and you are able to edit and change:</p> + + <ul> + <li>The append feature, invoked by pressing an '<em>a</em>' + while viewing a document will add the current document or the + currently highlighted link to your default <em>Bookmark + file</em>, or to one you select if multiple bookmarks are + enabled.</li> + + <li>The remove feature, invoked by pressing an '<em>r</em>' + when a <em>Bookmark file</em> is being displayed, will remove + the currently highlighted link.</li> + + <li>You may set and modify the paths and names of your + <em>Bookmark files</em> and enable or disable multiple + bookmarks in the <a href="option_help.html">Options + Menu</a>.</li> + </ul> +</body> +</html> diff --git a/lynx_help/keystrokes/cookie_help.html b/lynx_help/keystrokes/cookie_help.html index ed74c77c..ad4c4240 100644 --- a/lynx_help/keystrokes/cookie_help.html +++ b/lynx_help/keystrokes/cookie_help.html @@ -1,49 +1,60 @@ -<!DOCTYPE html PUBLIC "-//IETF//DTD HTML 3.0//EN"> -<HTML> -<HEAD> -<TITLE>Help on the Cookie Jar Page</TITLE> -<LINK rev="made" href="mailto:lynx-dev@nongnu.org"> -<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1"> -</HEAD> -<BODY> -<h1>+++ Cookie Jar Page Help +++</h1> +<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 3.2//EN"> +<!-- $LynxId: cookie_help.html,v 1.7 2012/01/31 23:19:37 tom Exp $ --> -The Cookie Jar Page displays all of the unexpired cookies you have -accumulated in the hypothetical <em>Cookie Jar</em>. The cookies are -obtained via <em>Set-Cookie</em> MIME headers in replies from http servers, -and are used for <A HREF="../Lynx_users_guide.html#Cookies">State Management</A> -across successive requests to the servers. +<html> +<head> + <meta name="generator" content= + "HTML Tidy for Linux/x86 (vers 6 November 2007), see www.w3.org"> -<p>The cookies are listed by <em>domain</em> (server's Fully Qualified -Domain Name, or site-identifying portion of the FQDN), and in order -of decreasing specificity (number of slash-separated symbolic elements -in the <em>path</em> attribute of the cookie). When Lynx sends requests -to an http server whose address tail-matches a <em>domain</em> in the -<em>Cookie Jar</em>, all its cookies with a <em>path</em> which -head-matches the path in the URL for that request are included as a -<em>Cookie</em> MIME header. The 'allow' setting for accepting cookies -from each domain (always, never, or via prompt) also is indicated in the -listing. + <title>Help on the Cookie Jar Page</title> + <link rev="made" href="mailto:lynx-dev@nongnu.org"> + <meta http-equiv="Content-Type" content= + "text/html; charset=us-ascii"> +</head> -<p>The listing also shows the <em>port</em> (normally 80) of the URL -for the request which caused the cookie to be sent, and whether the -<em>secure</em> flag is set for the cookie, in which case it will be -sent only via secure connections (presently, only SSL). The -<em>Maximum Gobble Date</em>, i.e., when the cookie is intended to -expire, also is indicated. Also, a server may change the expiration date, -or cause the cookie to be deleted, in its replies to subsequent requests -from Lynx. If the server included any explanatory comments in its -<em>Set-Cookie</em> MIME headers, those also are displayed in the listing. +<body> + <h1>Cookie Jar Page Help</h1> -<p>The <em>domain</em>=value pairs, and each cookie's name=value, are -links in the listing. Activating a <em>domain</em>=value link will -invoke a prompt asking whether all cookies in that <em>domain</em> -should be <em>Gobbled</em> (deleted from the <em>Cookie Jar</em>), -and/or whether the <em>domain</em> entry should be <em>Gobbled</em> -if all of its cookies have been <em>Gobbled</em>, or whether to change -the 'allow' setting for that <em>domain</em>. Activating a cookie's -name=value link will cause that particular cookie to be <em>Gobbled</em>. -You will be prompted for confirmations of deletions, to avoid any -accidental <em>Gobbling</em>. -</BODY> -</HTML> + <p>The Cookie Jar Page displays all of the unexpired cookies you + have accumulated in the hypothetical <em>Cookie Jar</em>. The + cookies are obtained via <em>Set-Cookie</em> MIME headers in + replies from http servers, and are used for <a href= + "../Lynx_users_guide.html#Cookies">State Management</a> across + successive requests to the servers.</p> + + <p>The cookies are listed by <em>domain</em> (server's Fully + Qualified Domain Name, or site-identifying portion of the FQDN), + and in order of decreasing specificity (number of slash-separated + symbolic elements in the <em>path</em> attribute of the cookie). + When Lynx sends requests to an http server whose address + tail-matches a <em>domain</em> in the <em>Cookie Jar</em>, all + its cookies with a <em>path</em> which head-matches the path in + the URL for that request are included as a <em>Cookie</em> MIME + header. The 'allow' setting for accepting cookies from each + domain (always, never, or via prompt) also is indicated in the + listing.</p> + + <p>The listing also shows the <em>port</em> (normally 80) of the + URL for the request which caused the cookie to be sent, and + whether the <em>secure</em> flag is set for the cookie, in which + case it will be sent only via secure connections (presently, only + SSL). The <em>Maximum Gobble Date</em>, i.e., when the cookie is + intended to expire, also is indicated. Also, a server may change + the expiration date, or cause the cookie to be deleted, in its + replies to subsequent requests from Lynx. If the server included + any explanatory comments in its <em>Set-Cookie</em> MIME headers, + those also are displayed in the listing.</p> + + <p>The <em>domain</em>=value pairs, and each cookie's name=value, + are links in the listing. Activating a <em>domain</em>=value link + will invoke a prompt asking whether all cookies in that + <em>domain</em> should be <em>Gobbled</em> (deleted from the + <em>Cookie Jar</em>), and/or whether the <em>domain</em> entry + should be <em>Gobbled</em> if all of its cookies have been + <em>Gobbled</em>, or whether to change the 'allow' setting for + that <em>domain</em>. Activating a cookie's name=value link will + cause that particular cookie to be <em>Gobbled</em>. You will be + prompted for confirmations of deletions, to avoid any accidental + <em>Gobbling</em>.</p> +</body> +</html> diff --git a/lynx_help/keystrokes/dired_help.html b/lynx_help/keystrokes/dired_help.html index 953caae8..a692c1b9 100644 --- a/lynx_help/keystrokes/dired_help.html +++ b/lynx_help/keystrokes/dired_help.html @@ -1,17 +1,24 @@ -<!DOCTYPE html PUBLIC "-//IETF//DTD HTML 3.0//EN"> +<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 3.2//EN"> +<!-- $LynxId: dired_help.html,v 1.7 2012/01/31 23:19:02 tom Exp $ --> + <html> <head> -<title>Lynx Dired Help</title> -<link rev="made" href="mailto:lynx-dev@nongnu.org"> -<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1"> + <meta name="generator" content= + "HTML Tidy for Linux/x86 (vers 6 November 2007), see www.w3.org"> + + <title>Lynx Dired Help</title> + <link rev="made" href="mailto:lynx-dev@nongnu.org"> + <meta http-equiv="Content-Type" content= + "text/html; charset=us-ascii"> </head> + <body> -<h1>+++DIRED HELP+++</h1> + <h1>DIRED HELP</h1> -Lynx changes into Dired mode when you use a URL of the type -<em>file://localhost/path/</em>. While in Dired mode, some keys are -remapped to do the following functions: -<pre> + <p>Lynx changes into Dired mode when you use a URL of the type + <em>file://localhost/path/</em>. While in Dired mode, some keys + are remapped to do the following functions:</p> + <pre> C)reate - Create a new, empty file in the current directory. You will be prompted to enter @@ -37,18 +44,19 @@ remapped to do the following functions: U)pload - Upload a file to the current directory using one of the options listed in the upload screen. </pre> -Some other keys useful in Dired mode: -<pre> + + <p>Some other keys useful in Dired mode:</p> + <pre> D)ownload - Download selection using options listed in the download options screen. - E)dit - Spawn the editor defined in the <a - href="option_help.html">Options Menu</a> + E)dit - Spawn the editor defined in the <a href= +"option_help.html">Options Menu</a> and load selection for editing. </pre> -<em>Note:</em> Dired mode must be activated at compile time. -Otherwise, the above commands will not be available -and Lynx will treat a directory listing as an HTML file. + <p><em>Note:</em> Dired mode must be activated at compile time. + Otherwise, the above commands will not be available and Lynx will + treat a directory listing as an HTML file.</p> </body> </html> diff --git a/lynx_help/keystrokes/edit_help.html b/lynx_help/keystrokes/edit_help.html index 1421ef31..d18eb255 100644 --- a/lynx_help/keystrokes/edit_help.html +++ b/lynx_help/keystrokes/edit_help.html @@ -1,30 +1,38 @@ -<!DOCTYPE html PUBLIC "-//IETF//DTD HTML 3.0//EN"> +<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 3.2//EN"> +<!-- $LynxId: edit_help.html,v 1.13 2012/01/31 23:17:33 tom Exp $ --> + <html> <head> -<title>Lynx Line Editor Default Key Binding</title> -<link rev="made" href="mailto:lynx-dev@nongnu.org"> -<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1"> + <meta name="generator" content= + "HTML Tidy for Linux/x86 (vers 6 November 2007), see www.w3.org"> + + <title>Lynx Line Editor Default Key Binding</title> + <link rev="made" href="mailto:lynx-dev@nongnu.org"> + <meta http-equiv="Content-Type" content= + "text/html; charset=us-ascii"> </head> -<body> -<h1>+++DEFAULT BINDING+++</h1> -Lynx invokes a built-in <em>Line Editor</em> for entering strings in -response to prompts, in forms, and for email messages if an external editor -has not been defined. Alternative key bindings can be offered -by configuring with --enable-alt-bindings or by adding them in LYEditmap.c -before compiling Lynx. If available, they may -be selected via the 'o'ptions menu, or by editing lineedit_mode in the -'.lynxrc' file. +<body> + <h1>DEFAULT BINDING</h1> -<p>Two such alternative key bindings, which may be available on your system, -are the <A HREF="alt_edit_help.html">Alternative Binding</A> keymap and the -<A HREF="bashlike_edit_help.html">Bash-like Binding</A> keymap. + <p>Lynx invokes a built-in <em>Line Editor</em> for entering + strings in response to prompts, in forms, and for email messages + if an external editor has not been defined. Alternative key + bindings can be offered by configuring with --enable-alt-bindings + or by adding them in LYEditmap.c before compiling Lynx. If + available, they may be selected via the 'o'ptions menu, or by + editing lineedit_mode in the '.lynxrc' file.</p> -<p>Note: setting emacs/vi keys ON has no effect on line-editor bindings. + <p>Two such alternative key bindings, which may be available on + your system, are the <a href="alt_edit_help.html">Alternative + Binding</a> keymap and the <a href= + "bashlike_edit_help.html">Bash-like Binding</a> keymap.</p> -<p>This is the <em>Default Binding</em> keymap: + <p>Note: setting emacs/vi keys ON has no effect on line-editor + bindings.</p> -<pre> + <p>This is the <em>Default Binding</em> keymap:</p> + <pre> ENTER Input complete - RETURN TAB Input complete - TAB, Do ABORT Input cancelled - Ctrl-G, Ctrl-O, (Ctrl-C on some systems) @@ -49,7 +57,8 @@ are the <A HREF="alt_edit_help.html">Alternative Binding</A> keymap and the LKCMD Invoke cmd prompt - Ctrl-V (in form text fields, only) [2] SWMAP Switch input keymap - Ctrl-^ (if compiled in) -<A NAME="TASpecial">Special commands for use only in textarea fields</A>[3]: +<a name= +"TASpecial">Special commands for use only in textarea fields</a>[3]: Textarea external edit - Ctrl-X e Insert file in textarea - Ctrl-X i @@ -64,8 +73,7 @@ are the <A HREF="alt_edit_help.html">Alternative Binding</A> keymap and the [3] For other key combinations using Ctrl-X as a prefix key, see the Help page for the <a rel="Sibling" title="Bash-Like Binding" - href="bashlike_edit_help.html" - >Bash-Like</a> Binding. +href="bashlike_edit_help.html">Bash-Like</a> Binding. </pre> </body> </html> diff --git a/lynx_help/keystrokes/environments.html b/lynx_help/keystrokes/environments.html index 24c71daf..c6988b0c 100644 --- a/lynx_help/keystrokes/environments.html +++ b/lynx_help/keystrokes/environments.html @@ -1,29 +1,38 @@ -<!DOCTYPE html PUBLIC "-//IETF//DTD HTML 3.0//EN"> -<!-- $LynxId: environments.html,v 1.13 2007/05/13 22:47:50 Chuck.Houpt Exp $ --> +<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 3.2//EN"> +<!-- $LynxId: environments.html,v 1.14 2012/01/31 23:25:10 tom Exp $ --> + <html> <head> -<title>Help on Environment variables</title> -<LINK rev="made" href="mailto:lynx-dev@nongnu.org"> -<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1"> + <meta name="generator" content= + "HTML Tidy for Linux/x86 (vers 6 November 2007), see www.w3.org"> + + <title>Help on Environment variables</title> + <link rev="made" href="mailto:lynx-dev@nongnu.org"> + <meta http-equiv="Content-Type" content= + "text/html; charset=us-ascii"> </head> + <body> -<pre> + <pre> <em>ENVIRONMENT</em> In addition to various "standard" environment variables such as HOME, PATH, USER, DISPLAY, TMPDIR, etc, Lynx utilizes - several Lynx-specific environment variables, <a href="#env">if they exist</a>. + several Lynx-specific environment variables, <a href= +"#env">if they exist</a>. Others may be created or modified by Lynx to pass data to an external program, or for other reasons. These are listed separately <a href="#setenv">below</a>. - See also the sections on <a href="#cgi">SIMULATED CGI SUPPORT</a> and + See also the sections on <a href= +"#cgi">SIMULATED CGI SUPPORT</a> and <a href="#language">NATIVE LANGUAGE SUPPORT</a>, below. Note: Not all environment variables apply to all types of platforms supported by Lynx, though most do. Feedback on - platform dependencies is solicited. See also <a href="#dos">win32/dos</a> specific + platform dependencies is solicited. See also <a href= +"#dos">win32/dos</a> specific variables. <a name="env"><em> @@ -132,7 +141,8 @@ Environment Variables Used By Lynx: the form PROTOCOL_proxy (literally: http_proxy, ftp_proxy, gopher_proxy, etc), to "http://some.server.dom:port/". - See <a href="#proxy">Proxy details and examples</a>. + See <a href= +"#proxy">Proxy details and examples</a>. WWW_access_GATEWAY Lynx still supports use of gateway @@ -144,7 +154,8 @@ Environment Variables Used By Lynx: discontinued. Note that you do not include a terminal '/' for gateways, but do for proxies specified by PROTOCOL_proxy - environment variables. See <a href="#proxy">Proxy details</a>. + environment variables. See <a href= +"#proxy">Proxy details</a>. WWW_HOME This variable, if set, will override diff --git a/lynx_help/keystrokes/follow_help.html b/lynx_help/keystrokes/follow_help.html index 8f0cea51..394b3553 100644 --- a/lynx_help/keystrokes/follow_help.html +++ b/lynx_help/keystrokes/follow_help.html @@ -1,181 +1,187 @@ -<!DOCTYPE html PUBLIC "-//IETF//DTD HTML 3.0//EN"> -<HTML> -<HEAD> -<TITLE>Help on the Follow link (or page) number feature</TITLE> -<LINK rev="made" href="mailto:lynx-dev@nongnu.org"> -<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1"> -</HEAD> -<BODY> -<h1>+++ Follow link (or goto link or page) number Help +++<br> -+++ Select option (or page) number Help +++</h1> +<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01//EN"> +<!-- $LynxId: follow_help.html,v 1.10 2012/01/31 23:16:38 tom Exp $ --> -If a user has set <em>Keypad mode</em> to <em>Links are numbered</em>, -or <em>Form fields are numbered</em>, -or <em>Links and form fields are numbered</em> -as the default or for the current session via the <em>Options menu</em>, -then hypertext links -(and form fields, depending on the keypad mode) -are prefixed with numbers in square brackets. Entering a keyboard -or keypad number is treated as an <em>F_LINK_NUM</em> command, and should -invoke the <em>Follow link (or goto link or page) number:</em> statusline -prompt for a -potentially multiple digit number corresponding to an indicated link -number. If RETURN is pressed to terminate the number entry (e.g., -<em>123</em>) and it corresponds to a hypertext link, Lynx will retrieve -the document for that link as if you had paged or used other navigation -commands to make it the current link and then ACTIVATE-ed it. The prompt -can be invoked via '<em>0</em>', but it will not be treated as the lead -digit for the number entry, whereas '<em>1</em>' through '<em>9</em>' both -invoke the prompt and are treated as the first digit. -In <em>Form fields are numbered</em> -or <em>Links and form fields are numbered</em> mode, -if the number corresponds to a form -field you will be positioned on that field, but if it is a submit button -it will not be ACTIVATE-ed. +<html> +<head> + <meta name="generator" content= + "HTML Tidy for Linux/x86 (vers 6 November 2007), see www.w3.org"> -<p>If the number entered at the prompt has a '<em>g</em>' suffix (e.g., -<em>123g</em>), then Lynx will make the link corresponding to that number -the current link, paging as appropriate if the link does not appear in -the currently displayed page. The '<em>g</em>' suffix is inferred (need -not be entered) for form fields in -<em>Form fields are numbered</em> or -<em>Links and form fields are numbered</em> mode. + <title>Help on the Follow link (or page) number feature</title> + <link rev="made" href="mailto:lynx-dev@nongnu.org"> + <meta http-equiv="Content-Type" content= + "text/html; charset=us-ascii"> +</head> -<p>Alternatively, if the number is given a '<em>p</em>' suffix (e.g., -<em>123p</em>), Lynx will make the page corresponding to that number -the currently displayed page, and the first link on that page, if any, -the current link. The '<em>g</em>' and '<em>p</em>' suffixes thus -convert the -<em>Follow link (or goto link or page) number:</em> feature to an advanced -navigation aid. +<body> + <h1>Follow link (or goto link or page) number Help<br> + Select option (or page) number Help</h1> -<p>Finally, a user may add a <em>+</em> or <em>-</em> suffix to a number -command to indicate jumping forward or back relative to the current link or -page. -For example, typing <em>1g+</em> followed by RETURN will move the current -link to the next numbered link, skipping any intervening pages -or unnumbered links; <em>1g-</em> goes to the preceding numbered link. -On a page without links, <em>3g+</em> goes to the 3rd link <em>following</em> -the page. <em>5p+</em> skips ahead 5 pages, and so on. -You can also enter <em>5+</em> or <em>5-</em>, which will activate -the 5th link ahead/behind where you are currently positioned. -Note that typing <em>1g+</em> is different from typing a down arrow -in that <em>1g+</em> skips pages containing no links, or -intervening non-numbered links, such as form fields when -form fields are not numbered. It also differs from -the <em><tab></em> command in that <em>1g+</em> -does not skip over whole textareas, unless form fields -are not numbered. + <p>If a user has set <em>Keypad mode</em> to <em>Links are + numbered</em>, or <em>Form fields are numbered</em>, or <em>Links + and form fields are numbered</em> as the default or for the + current session via the <em>Options menu</em>, then hypertext + links (and form fields, depending on the keypad mode) are + prefixed with numbers in square brackets. Entering a keyboard or + keypad number is treated as an <em>F_LINK_NUM</em> command, and + should invoke the <em>Follow link (or goto link or page) + number:</em> statusline prompt for a potentially multiple digit + number corresponding to an indicated link number. If RETURN is + pressed to terminate the number entry (e.g., <em>123</em>) and it + corresponds to a hypertext link, Lynx will retrieve the document + for that link as if you had paged or used other navigation + commands to make it the current link and then ACTIVATE-ed it. The + prompt can be invoked via '<em>0</em>', but it will not be + treated as the lead digit for the number entry, whereas + '<em>1</em>' through '<em>9</em>' both invoke the prompt and are + treated as the first digit. In <em>Form fields are numbered</em> + or <em>Links and form fields are numbered</em> mode, if the + number corresponds to a form field you will be positioned on that + field, but if it is a submit button it will not be + ACTIVATE-ed.</p> -<p> -<em>NOTE:</em> <em>1+g 1-g 1+p 1-p</em> are all recognized as equivalent -to <em>1g+ 1g- 1p+ 1p-</em> . Any other (mistyped) characters end -the formula: e.g. <em>1gh+</em> is treated as <em>1g</em>. + <p>If the number entered at the prompt has a '<em>g</em>' suffix + (e.g., <em>123g</em>), then Lynx will make the link corresponding + to that number the current link, paging as appropriate if the + link does not appear in the currently displayed page. The + '<em>g</em>' suffix is inferred (need not be entered) for form + fields in <em>Form fields are numbered</em> or <em>Links and form + fields are numbered</em> mode.</p> -<p>If the user has set <em>Keypad mode</em> to <em>Numbers act as arrows</em>, -then only '<em>0</em>', rather than every number, will be treated as an -<em>F_LINK_NUM</em> command for invoking the <em>Follow link (or goto link or page) -number:</em> prompt. The '<em>0</em>' will not be treated as the first -digit for the number, or number plus suffix, entry. + <p>Alternatively, if the number is given a '<em>p</em>' suffix + (e.g., <em>123p</em>), Lynx will make the page corresponding to + that number the currently displayed page, and the first link on + that page, if any, the current link. The '<em>g</em>' and + '<em>p</em>' suffixes thus convert the <em>Follow link (or goto + link or page) number:</em> feature to an advanced navigation + aid.</p> -<p>Numbers are associated with form fields only when -<em>Form fields are numbered</em> or -<em>Links and form fields are numbered</em> mode has been selected. -If you have selected -<em>Numbers act as arrows</em> or <em>Links are numbered</em> mode, you -can seek form fields in the document via WHEREIS searches for strings in -their displayed values. If they are INPUT or TEXTAREA fields with no -values as yet, you can use two or more underscores as the search string, -because underscores are used as placeholders for form fields in the -displayed document. + <p>Finally, a user may add a <em>+</em> or <em>-</em> suffix to a + number command to indicate jumping forward or back relative to + the current link or page. For example, typing <em>1g+</em> + followed by RETURN will move the current link to the next + numbered link, skipping any intervening pages or unnumbered + links; <em>1g-</em> goes to the preceding numbered link. On a + page without links, <em>3g+</em> goes to the 3rd link + <em>following</em> the page. <em>5p+</em> skips ahead 5 pages, + and so on. You can also enter <em>5+</em> or <em>5-</em>, which + will activate the 5th link ahead/behind where you are currently + positioned. Note that typing <em>1g+</em> is different from + typing a down arrow in that <em>1g+</em> skips pages containing + no links, or intervening non-numbered links, such as form fields + when form fields are not numbered. It also differs from the + <em><tab></em> command in that <em>1g+</em> does not skip + over whole textareas, unless form fields are not numbered.</p> -<p ID="select-option">When you have invoked a popup window for a list of -OPTIONs in a form's SELECT block, each OPTION is associated with a number, -and that number will be displayed in -<em>Form fields are numbered</em> or -<em>Links and form fields are numbered</em> mode. -In any keypad mode, the <em>F_LINK_NUM</em> -('<em>0</em>') command will invoke a <em>Select option (or page) -number:</em> prompt, and you can enter a number, and optionally a -'<em>g</em>' or '<em>p</em>' suffix, to select or seek an OPTION in that -list. If only a number is entered at the prompt, the corresponding OPTION -will be selected and the popup will be retracted. If the '<em>g</em>' -suffix is included, then you will be positioned on the corresponding OPTION -in the list, paging through the list if necessary, but it will not be -treated as selected unless you enter the ACTIVATE (RETURN or right-arrow) -command when positioned on the OPTION. For purposes of paging (e.g., in -conjunction with the '<em>p</em>' suffix), a <em>page</em> is defined as -the number of OPTIONs displayed within the vertical dimension of the popup -window. -Finally, the <em>+</em> and <em>-</em> suffixes can be used -to move forward or back from the current option or page in -a popup menu, -similarly to the way they are used for links For example, -while viewing a popup window, the user can type -<em>3p+</em> and RETURN -to skip ahead 3 pages, and <em>50g-</em> will move the -current selection back 50 options. -This will work whether or not <em>keypad mode</em> is -<em>Form fields are numbered</em> or -<em>Links and form fields are numbered</em> since options -are numbered internally. If form field numbering is -turned off, the option numbers won't appear on screen, -but the user can still navigate using these commands. + <p><em>NOTE:</em> <em>1+g 1-g 1+p 1-p</em> are all recognized as + equivalent to <em>1g+ 1g- 1p+ 1p-</em> . Any other (mistyped) + characters end the formula: e.g. <em>1gh+</em> is treated as + <em>1g</em>.</p> -<p>Note that HTML can be structured so that it includes <em>hidden -links</em>, i.e., without a visible link name intended for ACTIVATE-ing -the link. Such links may be created, for example, by making an IMG element -the sole content of an Anchor element, and including an ALT="" attribute -name/value pair to suppress access to the link when the browser does not -have support for image handling available. They also can be created by -having truly empty Anchor content, in cases for which the value of an -Anchor's HREF attribute is intended as a navigation aid for robots -(typically indexers) and not as content for a browser's rendition of the -document. With the <em>-ismap</em> command line switch, Lynx will -additionally treat a link to a server-side image maps as hidden if -there also is a client-side map for the same image. -Finally, in some cases links that are not intended to be hidden -may effectively become <em>hidden links</em> because of bad HTML. -The <em>hidden links</em> differ from Anchors that have only a -NAME or ID attribute name/value pair (intended as positioning targets from -other links which do have HREF attributes and values that include a -fragment). + <p>If the user has set <em>Keypad mode</em> to <em>Numbers act as + arrows</em>, then only '<em>0</em>', rather than every number, + will be treated as an <em>F_LINK_NUM</em> command for invoking + the <em>Follow link (or goto link or page) number:</em> prompt. + The '<em>0</em>' will not be treated as the first digit for the + number, or number plus suffix, entry.</p> -<p>Lynx respects instructions for <em>hidden links</em> and normally does -not include them in the rendition of the document. However, if the command -line switch <em>-hiddenlinks=merge</em> is used, such links will still be -numbered in sequence with other links which are not hidden, and if <em>Links -are numbered</em> mode is also on, link numbers will appear for them in the -displayed text (except for links to image maps which are hidden because of -<em>-ismap</em>). If <em>-hiddenlinks=listonly</em> or -<em>-hiddenlinks=ignore</em> is in effect, <em>hidden links</em> will not be -shown in the text even in <em>links are numbered</em> mode. Not using a -<em>-hiddenlinks</em> flag at all is equivalent to -<em>-hiddenlinks=listonly</em>. + <p>Numbers are associated with form fields only when <em>Form + fields are numbered</em> or <em>Links and form fields are + numbered</em> mode has been selected. If you have selected + <em>Numbers act as arrows</em> or <em>Links are numbered</em> + mode, you can seek form fields in the document via WHEREIS + searches for strings in their displayed values. If they are INPUT + or TEXTAREA fields with no values as yet, you can use two or more + underscores as the search string, because underscores are used as + placeholders for form fields in the displayed document.</p> -<p>If a document includes -<em>hidden links</em>, they will be reported, with appropriate labeling, -in the menus created for the LIST ('<em>l</em>') or ADDRLIST ('<em>A</em>') -commands, unless <em>-hiddenlinks=ignore</em> is used. They can then be -ACTIVATE-ed via those menus. Also, if a link was hidden because of an ALT -attribute in an IMG element, it will be converted to a <em>visible link</em> -whenever the IMAGE_TOGGLE ('<em>*</em>') command is used to create links -for SRC attribute values of IMG elements, because this indicates that the -user does have some form of image handling enabled via a helper application, -or wishes to download files for subsequent use with a graphic browser or -other suitable software. + <p id="select-option">When you have invoked a popup window for a + list of OPTIONs in a form's SELECT block, each OPTION is + associated with a number, and that number will be displayed in + <em>Form fields are numbered</em> or <em>Links and form fields + are numbered</em> mode. In any keypad mode, the + <em>F_LINK_NUM</em> ('<em>0</em>') command will invoke a + <em>Select option (or page) number:</em> prompt, and you can + enter a number, and optionally a '<em>g</em>' or '<em>p</em>' + suffix, to select or seek an OPTION in that list. If only a + number is entered at the prompt, the corresponding OPTION will be + selected and the popup will be retracted. If the '<em>g</em>' + suffix is included, then you will be positioned on the + corresponding OPTION in the list, paging through the list if + necessary, but it will not be treated as selected unless you + enter the ACTIVATE (RETURN or right-arrow) command when + positioned on the OPTION. For purposes of paging (e.g., in + conjunction with the '<em>p</em>' suffix), a <em>page</em> is + defined as the number of OPTIONs displayed within the vertical + dimension of the popup window. Finally, the <em>+</em> and + <em>-</em> suffixes can be used to move forward or back from the + current option or page in a popup menu, similarly to the way they + are used for links For example, while viewing a popup window, the + user can type <em>3p+</em> and RETURN to skip ahead 3 pages, and + <em>50g-</em> will move the current selection back 50 options. + This will work whether or not <em>keypad mode</em> is <em>Form + fields are numbered</em> or <em>Links and form fields are + numbered</em> since options are numbered internally. If form + field numbering is turned off, the option numbers won't appear on + screen, but the user can still navigate using these commands.</p> -<p>HTML forms also may have fields with a HIDDEN attribute, indicating that -a name/value pair for the fields should be included in the content submitted -for the form, but the value should not be displayed in the rendered form. -Lynx respects this attribute as well, and neither displays the HIDDEN field, -nor assigns it a number for the F_LINK_NUM ('<em>0</em>') command and -<em>Form fields are numbered</em> or -<em>Links and form fields are numbered</em> keypad mode handling, nor -includes an entry for it in the menus created for the LIST ('<em>l</em>') -or ADDRLIST ('<em>A</em>') -commands. However, the HIDDEN name/value pairs are included in any displays -of submitted form content in the <em>Information about the current -document</em> that is invoked by the INFO ('<em>=</em>') command. -</BODY> -</HTML> + <p>Note that HTML can be structured so that it includes + <em>hidden links</em>, i.e., without a visible link name intended + for ACTIVATE-ing the link. Such links may be created, for + example, by making an IMG element the sole content of an Anchor + element, and including an ALT="" attribute name/value pair to + suppress access to the link when the browser does not have + support for image handling available. They also can be created by + having truly empty Anchor content, in cases for which the value + of an Anchor's HREF attribute is intended as a navigation aid for + robots (typically indexers) and not as content for a browser's + rendition of the document. With the <em>-ismap</em> command line + switch, Lynx will additionally treat a link to a server-side + image maps as hidden if there also is a client-side map for the + same image. Finally, in some cases links that are not intended to + be hidden may effectively become <em>hidden links</em> because of + bad HTML. The <em>hidden links</em> differ from Anchors that have + only a NAME or ID attribute name/value pair (intended as + positioning targets from other links which do have HREF + attributes and values that include a fragment).</p> + + <p>Lynx respects instructions for <em>hidden links</em> and + normally does not include them in the rendition of the document. + However, if the command line switch <em>-hiddenlinks=merge</em> + is used, such links will still be numbered in sequence with other + links which are not hidden, and if <em>Links are numbered</em> + mode is also on, link numbers will appear for them in the + displayed text (except for links to image maps which are hidden + because of <em>-ismap</em>). If <em>-hiddenlinks=listonly</em> or + <em>-hiddenlinks=ignore</em> is in effect, <em>hidden links</em> + will not be shown in the text even in <em>links are numbered</em> + mode. Not using a <em>-hiddenlinks</em> flag at all is equivalent + to <em>-hiddenlinks=listonly</em>.</p> + + <p>If a document includes <em>hidden links</em>, they will be + reported, with appropriate labeling, in the menus created for the + LIST ('<em>l</em>') or ADDRLIST ('<em>A</em>') commands, unless + <em>-hiddenlinks=ignore</em> is used. They can then be + ACTIVATE-ed via those menus. Also, if a link was hidden because + of an ALT attribute in an IMG element, it will be converted to a + <em>visible link</em> whenever the IMAGE_TOGGLE ('<em>*</em>') + command is used to create links for SRC attribute values of IMG + elements, because this indicates that the user does have some + form of image handling enabled via a helper application, or + wishes to download files for subsequent use with a graphic + browser or other suitable software.</p> + + <p>HTML forms also may have fields with a HIDDEN attribute, + indicating that a name/value pair for the fields should be + included in the content submitted for the form, but the value + should not be displayed in the rendered form. Lynx respects this + attribute as well, and neither displays the HIDDEN field, nor + assigns it a number for the F_LINK_NUM ('<em>0</em>') command and + <em>Form fields are numbered</em> or <em>Links and form fields + are numbered</em> keypad mode handling, nor includes an entry for + it in the menus created for the LIST ('<em>l</em>') or ADDRLIST + ('<em>A</em>') commands. However, the HIDDEN name/value pairs are + included in any displays of submitted form content in the + <em>Information about the current document</em> that is invoked + by the INFO ('<em>=</em>') command.</p> +</body> +</html> diff --git a/lynx_help/keystrokes/gopher_types_help.html b/lynx_help/keystrokes/gopher_types_help.html index ea886d29..5af38dbd 100644 --- a/lynx_help/keystrokes/gopher_types_help.html +++ b/lynx_help/keystrokes/gopher_types_help.html @@ -1,59 +1,83 @@ -<!DOCTYPE html PUBLIC "-//IETF//DTD HTML 3.0//EN"> -<HTML> -<HEAD> -<TITLE>Listing of Gopher types</TITLE> -<LINK rev="made" href="mailto:lynx-dev@nongnu.org"> -<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1"> -</HEAD> -<BODY> -<h1>+++ Gopher Types +++</h1> - -<dl compact> -<dt>(FILE) -<dd>An ASCII file - -<dt>(DIR) -<dd>A directory listing - -<dt>(CSO) -<dd>The Computing Services Organizations -nameserver interface - -<dt>(BIN) -<dd>A binary file with one of the following meanings -<ul> -<li>A Binary file with PC extensions -<li>A Binary file with UNIX extensions -</ul> - -<dt>(HQX) -<dd>A Macintosh file that has been BinHexed - -<dt>(?) -<dd>A searchable database - - -<dt>(IMG) -<dd>An unknown image type<br> -You must have an <A HREF="xterm_help.html">X terminal</A> to -view images - -<dt>(GIF) -<dd>An image in Graphics Interchange Format<br> -You must have an <A HREF="xterm_help.html">X terminal</A> to -view images - -<dt>(HTML) -<dd>A World Wide Web hypertext file - -<dt>(TEL) -<dd>The link will open a connection to another host using telnet - -<dt>(3270) -<dd>The link will open a connection to another host using tn3270 - -<dt>(UKN) -<dd>An unknown or unsupported type -</dl> -</BODY> -</HTML> +<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 3.2//EN"> +<!-- $LynxId: gopher_types_help.html,v 1.7 2012/01/31 23:15:38 tom Exp $ --> + +<html> +<head> + <meta name="generator" content= + "HTML Tidy for Linux/x86 (vers 6 November 2007), see www.w3.org"> + + <title>Listing of Gopher types</title> + <link rev="made" href="mailto:lynx-dev@nongnu.org"> + <meta http-equiv="Content-Type" content= + "text/html; charset=us-ascii"> +</head> + +<body> + <h1>Gopher Types</h1> + + <dl compact> + <dt>(FILE)</dt> + + <dd>An ASCII file</dd> + + <dt>(DIR)</dt> + + <dd>A directory listing</dd> + + <dt>(CSO)</dt> + + <dd>The Computing Services Organizations nameserver + interface</dd> + + <dt>(BIN)</dt> + + <dd> + A binary file with one of the following meanings + + <ul> + <li>A Binary file with PC extensions</li> + + <li>A Binary file with UNIX extensions</li> + </ul> + </dd> + + <dt>(HQX)</dt> + + <dd>A Macintosh file that has been BinHexed</dd> + + <dt>(?)</dt> + + <dd>A searchable database</dd> + + <dt>(IMG)</dt> + + <dd>An unknown image type<br> + You must have an <a href="xterm_help.html">X terminal</a> to + view images</dd> + + <dt>(GIF)</dt> + + <dd>An image in Graphics Interchange Format<br> + You must have an <a href="xterm_help.html">X terminal</a> to + view images</dd> + + <dt>(HTML)</dt> + + <dd>A World Wide Web hypertext file</dd> + + <dt>(TEL)</dt> + + <dd>The link will open a connection to another host using + telnet</dd> + + <dt>(3270)</dt> + + <dd>The link will open a connection to another host using + tn3270</dd> + + <dt>(UKN)</dt> + + <dd>An unknown or unsupported type</dd> + </dl> +</body> +</html> diff --git a/lynx_help/keystrokes/history_help.html b/lynx_help/keystrokes/history_help.html index aab4dcac..f8f4566a 100644 --- a/lynx_help/keystrokes/history_help.html +++ b/lynx_help/keystrokes/history_help.html @@ -1,38 +1,48 @@ -<!DOCTYPE html PUBLIC "-//IETF//DTD HTML 3.0//EN"> -<HTML> -<HEAD> -<TITLE>Help on the History Page</TITLE> -<LINK rev="made" href="mailto:lynx-dev@nongnu.org"> -<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1"> -</HEAD> -<BODY> -<h1>+++ History Page Help +++</h1> +<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 3.2//EN"> +<!-- $LynxId: history_help.html,v 1.5 2012/01/31 23:14:48 tom Exp $ --> -The History Page displays all of the links that you have traveled through -to reach your current point, including any temporary menu or list files -that included links, bookmark files, and any documents associated with -POST content. If you entered a document and then left it by using the -<em>left-arrow</em> key, it will <em>not</em> be in the history stack. -If you entered a document and left it by selecting another link within -that document, it <em>will</em> be in the history stack. +<html> +<head> + <meta name="generator" content= + "HTML Tidy for Linux/x86 (vers 6 November 2007), see www.w3.org"> -<p>You may <A HREF="movement_help.html">select</A> any link on the History -Page to review a document that you have previously visited. That link, -and any subsequent to it, will not be removed from the history stack if you -return to it via the History Page. You thus should use a History Page link, -rather than the <em>left-arrow</em> key, if you wish to review previous -documents without needing to remember and repeat the series of selections -for reaching your currently displayed document. + <title>Help on the History Page</title> + <link rev="made" href="mailto:lynx-dev@nongnu.org"> + <meta http-equiv="Content-Type" content= + "text/html; charset=us-ascii"> +</head> -<p>Upon using <em>left-arrow</em> in the document selected via the History -Page, you will be returned to the document from which you initially went to -the History Page. +<body> + <h1>History Page Help</h1> -<p>If a previously visited link has been removed from the history stack, -and it was not a temporary menu or list file, bookmark file, or document -associated with POST content, it can still be selected conveniently via -the <A HREF="visited_help.html">Visited Links Page</A>. The latter also -will include links which were '<em>d</em>'ownloaded or passed to a helper -application, and thus were not included in the history stack. -</BODY> -</HTML> + <p>The History Page displays all of the links that you have + traveled through to reach your current point, including any + temporary menu or list files that included links, bookmark files, + and any documents associated with POST content. If you entered a + document and then left it by using the <em>left-arrow</em> key, + it will <em>not</em> be in the history stack. If you entered a + document and left it by selecting another link within that + document, it <em>will</em> be in the history stack.</p> + + <p>You may <a href="movement_help.html">select</a> any link on + the History Page to review a document that you have previously + visited. That link, and any subsequent to it, will not be removed + from the history stack if you return to it via the History Page. + You thus should use a History Page link, rather than the + <em>left-arrow</em> key, if you wish to review previous documents + without needing to remember and repeat the series of selections + for reaching your currently displayed document.</p> + + <p>Upon using <em>left-arrow</em> in the document selected via + the History Page, you will be returned to the document from which + you initially went to the History Page.</p> + + <p>If a previously visited link has been removed from the history + stack, and it was not a temporary menu or list file, bookmark + file, or document associated with POST content, it can still be + selected conveniently via the <a href="visited_help.html">Visited + Links Page</a>. The latter also will include links which were + '<em>d</em>'ownloaded or passed to a helper application, and thus + were not included in the history stack.</p> +</body> +</html> diff --git a/lynx_help/keystrokes/keystroke_help.html b/lynx_help/keystrokes/keystroke_help.html index 239cb53c..01855e3d 100644 --- a/lynx_help/keystrokes/keystroke_help.html +++ b/lynx_help/keystrokes/keystroke_help.html @@ -1,22 +1,29 @@ -<!DOCTYPE html PUBLIC "-//IETF//DTD HTML 3.0//EN"> -<HTML> -<HEAD> -<TITLE>Help on Lynx Keystroke Commands</TITLE> -<LINK rev="made" href="mailto:lynx-dev@nongnu.org"> -<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1"> -</HEAD> -<BODY> -<h1>+++ Keystroke Commands +++</h1> -<PRE> - <A HREF="movement_help.html" - >MOVEMENT</A>: Down arrow - Highlight next topic +<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 3.2//EN"> +<!-- $LynxId: keystroke_help.html,v 1.17 2012/01/31 23:25:43 tom Exp $ --> + +<html> +<head> + <meta name="generator" content= + "HTML Tidy for Linux/x86 (vers 6 November 2007), see www.w3.org"> + + <title>Help on Lynx Keystroke Commands</title> + <link rev="made" href="mailto:lynx-dev@nongnu.org"> + <meta http-equiv="Content-Type" content= + "text/html; charset=us-ascii"> +</head> + +<body> + <h1>Keystroke Commands</h1> + <pre> + <a href= +"movement_help.html">MOVEMENT</a>: Down arrow - Highlight next topic Up arrow - Highlight previous topic Right arrow, - Jump to highlighted topic Return, Enter - Follow selected link Left arrow - Return to previous topic - <A HREF="scrolling_help.html" - >SCROLLING</A>: + - Scroll down to next page (Page-Down) + <a href= +"scrolling_help.html">SCROLLING</a>: + - Scroll down to next page (Page-Down) - - Scroll up to previous page (Page-Up) SPACE - Scroll down to next page (Page-Down) b - Scroll up to previous page (Page-Up) @@ -34,7 +41,8 @@ > - Go to the next link in the current column # - Go to Toolbar or Banner in the current document - <A HREF="dired_help.html">DIRED</A>: c - Create a new file + <a href= +"dired_help.html">DIRED</a>: c - Create a new file d - Download selected file e - Edit selected file f - Show a full menu of options for current file @@ -43,15 +51,16 @@ t - Tag highlighted file u - Upload a file into the current directory - <A HREF="other_help.html">OTHER</A>: ? (or h) - Help (this screen) + <a href= +"other_help.html">OTHER</a>: ? (or h) - Help (this screen) a - Add the current link to a bookmark file c - Send a comment to the document owner d - Download the current link e - Edit the current file E - Edit the current link's URL (or ACTION) and use that as a goto URL. - g - Goto a user specified <a - href="../lynx_url_support.html">URL</a> or file + g - Goto a user specified <a href= +"../lynx_url_support.html">URL</a> or file G - Edit the current document's URL and use that as a goto URL. i - Show an index of documents @@ -59,22 +68,23 @@ k - Show list of actual key mappings l - List references (links) in current document m - Return to main screen - o - Set your <A HREF="option_help.html">options</A> - p - <a href="print_help.html" - >Print</a> to a file, mail, printers, or other + o - Set your <a href= +"option_help.html">options</a> + p - <a href= +"print_help.html">Print</a> to a file, mail, printers, or other q - Quit (Capital 'Q' for quick quit) / - Search for a string within the current document s - Enter a search string for an external search n - Go to the next search string N - Go to the previous search string - v - View a <A HREF="bookmark_help.html" - >bookmark file</A> - V - Go to the <A HREF="visited_help.html" - >Visited Links Page</A> + v - View a <a href= +"bookmark_help.html">bookmark file</a> + V - Go to the <a href= +"visited_help.html">Visited Links Page</a> x - Force submission of form or link with no-cache z - Cancel transfer in progress - [backspace] - Go to the <A HREF="history_help.html" - >History Page</A> + [backspace] - Go to the <a href= +"history_help.html">History Page</a> = - Show info about current document, URL and link \ - Toggle document source/rendered view ! - Spawn your default shell @@ -100,12 +110,12 @@ CTRL-L - Refresh the screen CTRL-V - Outside of a text input line or field, - switch to <A HREF="option_help.html#tagsoup" - >alternative parsing</A> of HTML. + switch to <a href= +"option_help.html#tagsoup">alternative parsing</a> of HTML. - In a form text input field, CTRL-V prompts for a key command (allows - <A HREF="../Lynx_users_guide.html#CtrlVNote" - >escaping</A> from the field). + <a href= +"../Lynx_users_guide.html#CtrlVNote">escaping</a> from the field). Note that on most UNIX hosts, CTRL-V is bound via stty to the lnext (literal-next) code but @@ -115,8 +125,8 @@ keystroke. CTRL-U - Inside text input line or field, - erase input line (<a href="edit_help.html" - >more input line commands</a>) + erase input line (<a href= +"edit_help.html">more input line commands</a>) - Outside of text input or field, undo returning to previous topic. @@ -124,17 +134,17 @@ CTRL-T - Toggle trace mode on and off ; - View the Lynx Trace Log for the current session - CTRL-K - Invoke the <A HREF="cookie_help.html" - >Cookie Jar Page</A> - CTRL-X - Invoke the <A HREF="../Lynx_users_guide.html#Cache" - >Cache Jar Page</A> + CTRL-K - Invoke the <a href= +"cookie_help.html">Cookie Jar Page</a> + CTRL-X - Invoke the <a href= +"../Lynx_users_guide.html#Cache">Cache Jar Page</a> numbers - Invoke the prompt - <a href="follow_help.html" - >Follow link (or goto link or page) number:</a> + <a href= +"follow_help.html">Follow link (or goto link or page) number:</a> or the - <a href="follow_help.html#select-option" - >Select option (or page) number:</a> + <a href= +"follow_help.html#select-option">Select option (or page) number:</a> prompt -</PRE> -</BODY> -</HTML> +</pre> +</body> +</html> diff --git a/lynx_help/keystrokes/movement_help.html b/lynx_help/keystrokes/movement_help.html index 70eaa2ca..a08534b9 100644 --- a/lynx_help/keystrokes/movement_help.html +++ b/lynx_help/keystrokes/movement_help.html @@ -1,13 +1,20 @@ -<!DOCTYPE html PUBLIC "-//IETF//DTD HTML 3.0//EN"> -<HTML> -<HEAD> -<TITLE>Help on Lynx Movement commands</TITLE> -<LINK rev="made" href="mailto:lynx-dev@nongnu.org"> -<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1"> -</HEAD> -<BODY> -<H1>+++ MOVEMENT HELP +++</H1> -<PRE> +<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 3.2//EN"> +<!-- $LynxId: movement_help.html,v 1.6 2012/01/31 23:24:18 tom Exp $ --> + +<html> +<head> + <meta name="generator" content= + "HTML Tidy for Linux/x86 (vers 6 November 2007), see www.w3.org"> + + <title>Help on Lynx Movement commands</title> + <link rev="made" href="mailto:lynx-dev@nongnu.org"> + <meta http-equiv="Content-Type" content= + "text/html; charset=us-ascii"> +</head> + +<body> + <h1>MOVEMENT HELP</h1> + <pre> Down arrow, - Move to the next hypertext link, TAB or scroll down if there are no more links on the page to move to. @@ -45,6 +52,6 @@ 1 2 3 3 - page down 2 - down arrow 1 - moves to the end of a document -</PRE> -</BODY> -</HTML> +</pre> +</body> +</html> diff --git a/lynx_help/keystrokes/option_help.html b/lynx_help/keystrokes/option_help.html index 7a68a609..7854b8af 100644 --- a/lynx_help/keystrokes/option_help.html +++ b/lynx_help/keystrokes/option_help.html @@ -1,257 +1,318 @@ -<!DOCTYPE html PUBLIC "-//IETF//DTD HTML 3.0//EN"> -<HTML> -<HEAD> -<TITLE>Form-based Options Menu : Help</TITLE> -<LINK rev="made" href="mailto:lynx-dev@nongnu.org"> -<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1"> -</HEAD> -<BODY> -<h1>FORM-BASED OPTIONS MENU : HELP</h1> - -The Options Menu allows you to set and modify many Lynx features.<BR> -Note: some options appear on the screen only if they have been -compiled in or chosen in `lynx.cfg': - -<UL> - -<LI>General Preferences -<UL> -<LI><A HREF="#UM">User Mode</A> -<LI><A HREF="#ED">Editor</A> -<LI><A HREF="#ST">Searching type</A> -<LI><A HREF="#CK">Cookies</A> -</UL> - -<LI>Keyboard Input -<UL> -<LI><A HREF="#KM">Keypad mode</A> -<LI><A HREF="#EM">Emacs keys</A> -<LI><A HREF="#VI">VI keys</A> -<LI><A HREF="#LE">Line edit style</A> -</UL> - -<LI>Display and Character Set -<UL> -<LI><A HREF="#DC">Display Character set</A> -<LI><A HREF="#AD">Assumed document character set</A> -<LI><A HREF="#JK">Raw 8-bit or CJK mode</A> -<LI><A HREF="#DV">X DISPLAY variable</A> -</UL> - -<LI>Document Appearance -<UL> -<LI><A HREF="#SC">Show color</A> -<LI><A HREF="#CL">Show cursor for current link or option</A> -<LI><A HREF="#PU">Pop-ups for select fields</A> -<LI><A HREF="#tagsoup">HTML error recovery</A> -<LI><A HREF="#SI">Show Images</A> -<LI><A HREF="#VB">Verbose Images</A> -</UL> - -<LI>Headers Transferred to Remote Servers -<UL> -<LI><A HREF="#PM">Personal Mail Address</A> -<LI><A HREF="#PC">Preferred Document Charset</A> -<LI><A HREF="#PL">Preferred Document Language</A> -<LI><A HREF="#UA">User Agent</A> -</UL> - -<LI>Listing and Accessing Files -<UL> -<LI><A HREF="#FT">FTP sort criteria</A> -<LI><A HREF="#LD">Local directory sort criteria</A> -<LI><A HREF="#DF">Show dot files</A> -<LI><A HREF="#LL">Execution links</A> -</UL> - -<LI>Special Files and Screens -<UL> -<LI><A HREF="#MB">Multi-bookmarks</A> -<LI><A HREF="#BF">Bookmark file</A> -<LI><A HREF="#VP">Visited Pages</A> -</UL> - -</UL> - -<H1><A NAME="CK">Cookies</A></H1> - -This can be set to accept or reject all cookies or to ask each time. -See the Users Guide for details of <A HREF="../Lynx_users_guide.html#Cookies" ->cookie usage</A>. - -<H1><A NAME="ED">Editor</A></H1> - -This is the editor to be invoked when editing browsable files, -sending mail or comments, or filling form's textarea (multiline input field). -The full pathname of the editor command should be specified when possible. -It is assumed the text editor supports the same character set -you have for "display character set" in Lynx. - -<H1><A NAME="EM">Emacs keys</A></H1> - -If set to 'ON' then the CTRL-P, CTRL-N, CTRL-F and CTRL-B keys will be mapped -to up-arrow, down-arrow, right-arrow and left-arrow respectively. Otherwise, -they remain mapped to their configured bindings (normally UP_TWO lines, -DOWN_TWO lines, NEXT_PAGE and PREV_PAGE respectively). -<p>Note: setting emacs keys does not affect the line-editor bindings. - -<H1><A NAME="LL">Execution links</A></H1> - -If set to 'ALWAYS ON', Lynx will locally execute commands contained -inside any links. This can be HIGHLY DANGEROUS, so it is recommended -that they remain 'ALWAYS OFF' or 'FOR LOCAL FILES ONLY'. - -<H1><A NAME="KM">Keypad mode</A></H1> - -This gives the choice between navigating with the keypad (as arrows; -see Lynx Navigation) and having every link numbered (numbered links) -so that the links may be selected by numbers instead of moving to them -with the arrow keys. You can also number form fields. - -<H1><A NAME="LE">Line edit style</A></H1> - -This allows you to set alternate key bindings for the built-in line editor, -if <A HREF="alt_edit_help.html">Alternate Bindings</A> have been installed. -Otherwise, Lynx uses the <A HREF="edit_help.html">Default Binding</A>. - -<H1><A NAME="PM">Personal Mail Address</A></H1> - -You may set your mail address here so that when mailing messages -to other people or mailing files to yourself, your email address can be -automatically filled in. Your email address will also be sent -to HTTP servers in a `from:' field. - -<H1><A NAME="PU">Pop-ups for select fields</A></H1> - -Lynx normally uses a pop-up window for the OPTIONs in form SELECT fields -when the field does not have the MULTIPLE attribute specified, and thus -only one OPTION can be selected. The use of pop-up windows can be disabled -by changing this setting to OFF, in which case the OPTIONs will be rendered -as a list of radio buttons. Note that if the SELECT field does have -the MULTIPLE attribute specified, the OPTIONs always are rendered -as a list of checkboxes. - -<H1><A NAME="ST">Searching type</A></H1> - -If set to 'case sensitive', user searches invoked by '/' will be -case-sensitive substring searches. Default is 'Case Insensitive'. - -<H1><A NAME="SC">Show color</A></H1> - -This will be present if color support is available. -<ul> -<li>If set to ON or ALWAYS, -color mode will be forced on if possible. If (n)curses color support -is available but cannot be used for the current terminal type, selecting ON -is rejected with a message. -<li>If set to OFF or NEVER, color mode will be -turned off. -<li>ALWAYS and NEVER are not offered in anonymous accounts. -If saved to a '.lynxrc' file in non-anonymous accounts, ALWAYS will cause Lynx -to set color mode on at startup if supported. -</ul> -If Lynx is built with slang, -this is equivalent to having included the -color command line switch -or having the COLORTERM environment variable set. If color support is -provided by curses or ncurses, this is equivalent to the default behavior -of using color when the terminal type supports it. If (n)curses color support -is available but cannot be used for the current terminal type, the preference -can still be saved but will have no effect. - -<p>A saved value of NEVER will -cause Lynx to assume a monochrome terminal at start-up. It is similar -to the -nocolor switch, but (when the slang library is used) can be overridden -with the -color switch. If the setting is OFF or ON when the current options -are saved to a '.lynxrc' file, the default start-up behavior is retained, -such that color mode will be turned on at startup only if the terminal info -indicates that you have a color-capable terminal, or (when slang is used) -if forced on via the -color switch or COLORTERM variable. This default -behavior always is used in anonymous accounts, or if the 'option'_save -restriction is set explicitly. If for any reason the start-up color mode -is incorrect for your terminal, set it appropriately on or off via this option. - -<H1><A NAME="CL">Show cursor for current link or option</A></H1> - -Lynx normally hides the cursor by positioning it to the right and if possible -the very bottom of the screen, so that the current link or OPTION is indicated -solely by its highlighting or color. If show cursor is set to ON, the cursor -will be positioned at the left of the current link or OPTION. This is helpful -when Lynx is being used with a speech or braille interface. It is also useful -for sighted users when the terminal cannot distinguish the character attributes -used to distinguish the current link or OPTION from the others in the display. - -<H1><A NAME="UM">User Mode</A></H1> - -<dl> -<dt><EM>Novice</EM>: Shows 2 extra lines of help at the bottom of the screen -for beginners. -<dt><EM>Intermediate (normal)</EM>: Normal status-line messages appear. -<dt><EM>Advanced</EM>: The URL is shown on the status line. -</dl> - -<H1><A NAME="AD">Assumed document character set</A></H1> - -This changes the handling of documents which do not explicitly specify -a charset. Normally Lynx assumes that 8-bit characters in those documents -are encoded according to iso-8859-1 (the official default for HTTP protocol). -Unfortunately, many non-English web pages forget to include proper charset -info; this option helps you browse those broken pages if you know somehow -what the charset is. When the value given here or by an -assume_charset -command-line flag is in effect, Lynx will treat documents as if they were -encoded accordingly. Option is active when 'Raw 8-bit or CJK Mode' is OFF. - -<H1><A NAME="JK">Raw 8-bit or CJK mode</A></H1> - -This is set automatically, but can be toggled manually in certain cases: -it toggles whether 8-bit characters are assumed to correspond with the display -character set and therefore are processed without translation -via the chartrans conversion tables. ON by default when the display -character set is one of the Asian (CJK) sets and the 8-bit characters -are Kanji multibytes. OFF for the other display character sets, -but can be turned ON when the document's charset is unknown -(e.g., is not ISO-8859-1 and no charset parameter was specified -in a reply header from an HTTP server to indicate what it is), -but you have no better idea than viewing it as from display character set -(see 'assumed document character set' for best choice). Should be OFF -when an Asian (CJK) set is selected but the document is ISO-8859-1 -or another 'assumed document character set'. The setting can also be toggled -via the RAW_TOGGLE command, normally mapped to '@', and at startup -via the -raw switch. - -<H1><A NAME="tagsoup">HTML error recovery</A></H1> - -Lynx often has to deal with invalid HTML markup. It always tries to -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 -<li>..</li> inside <a HREF="some.url">..</a>. -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. - -<!-- +<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 3.2//EN"> +<!-- $LynxId: option_help.html,v 1.24 2012/01/31 23:12:34 tom Exp $ --> + +<html> +<head> + <meta name="generator" content= + "HTML Tidy for Linux/x86 (vers 6 November 2007), see www.w3.org"> + + <title>Form-based Options Menu : Help</title> + <link rev="made" href="mailto:lynx-dev@nongnu.org"> + <meta http-equiv="Content-Type" content= + "text/html; charset=us-ascii"> +</head> + +<body> + <h1>FORM-BASED OPTIONS MENU : HELP</h1> + + <p>The Options Menu allows you to set and modify many Lynx + features.<br> + Note: some options appear on the screen only if they have been + compiled in or chosen in `lynx.cfg':</p> + + <ul> + <li>General Preferences + + <ul> + <li><a href="#UM">User Mode</a></li> + + <li><a href="#ED">Editor</a></li> + + <li><a href="#ST">Searching type</a></li> + + <li><a href="#CK">Cookies</a></li> + </ul> + </li> + + <li>Keyboard Input + + <ul> + <li><a href="#KM">Keypad mode</a></li> + + <li><a href="#EM">Emacs keys</a></li> + + <li><a href="#VI">VI keys</a></li> + + <li><a href="#LE">Line edit style</a></li> + </ul> + </li> + + <li>Display and Character Set + + <ul> + <li><a href="#DC">Display Character set</a></li> + + <li><a href="#AD">Assumed document character set</a></li> + + <li><a href="#JK">Raw 8-bit or CJK mode</a></li> + + <li><a href="#DV">X DISPLAY variable</a></li> + </ul> + </li> + + <li>Document Appearance + + <ul> + <li><a href="#SC">Show color</a></li> + + <li><a href="#CL">Show cursor for current link or + option</a></li> + + <li><a href="#PU">Pop-ups for select fields</a></li> + + <li><a href="#tagsoup">HTML error recovery</a></li> + + <li><a href="#SI">Show Images</a></li> + + <li><a href="#VB">Verbose Images</a></li> + </ul> + </li> + + <li>Headers Transferred to Remote Servers + + <ul> + <li><a href="#PM">Personal Mail Address</a></li> + + <li><a href="#PC">Preferred Document Charset</a></li> + + <li><a href="#PL">Preferred Document Language</a></li> + + <li><a href="#UA">User Agent</a></li> + </ul> + </li> + + <li>Listing and Accessing Files + + <ul> + <li><a href="#FT">FTP sort criteria</a></li> + + <li><a href="#LD">Local directory sort criteria</a></li> + + <li><a href="#DF">Show dot files</a></li> + + <li><a href="#LL">Execution links</a></li> + </ul> + </li> + + <li>Special Files and Screens + + <ul> + <li><a href="#MB">Multi-bookmarks</a></li> + + <li><a href="#BF">Bookmark file</a></li> + + <li><a href="#VP">Visited Pages</a></li> + </ul> + </li> + </ul> + + <h1><a name="CK">Cookies</a></h1> + + <p>This can be set to accept or reject all cookies or to ask each + time. See the Users Guide for details of <a href= + "../Lynx_users_guide.html#Cookies">cookie usage</a>.</p> + + <h1><a name="ED">Editor</a></h1> + + <p>This is the editor to be invoked when editing browsable files, + sending mail or comments, or filling form's textarea (multiline + input field). The full pathname of the editor command should be + specified when possible. It is assumed the text editor supports + the same character set you have for "display character set" in + Lynx.</p> + + <h1><a name="EM">Emacs keys</a></h1> + + <p>If set to 'ON' then the CTRL-P, CTRL-N, CTRL-F and CTRL-B keys + will be mapped to up-arrow, down-arrow, right-arrow and + left-arrow respectively. Otherwise, they remain mapped to their + configured bindings (normally UP_TWO lines, DOWN_TWO lines, + NEXT_PAGE and PREV_PAGE respectively).</p> + + <p>Note: setting emacs keys does not affect the line-editor + bindings.</p> + + <h1><a name="LL">Execution links</a></h1> + + <p>If set to 'ALWAYS ON', Lynx will locally execute commands + contained inside any links. This can be HIGHLY DANGEROUS, so it + is recommended that they remain 'ALWAYS OFF' or 'FOR LOCAL FILES + ONLY'.</p> + + <h1><a name="KM">Keypad mode</a></h1> + + <p>This gives the choice between navigating with the keypad (as + arrows; see Lynx Navigation) and having every link numbered + (numbered links) so that the links may be selected by numbers + instead of moving to them with the arrow keys. You can also + number form fields.</p> + + <h1><a name="LE">Line edit style</a></h1> + + <p>This allows you to set alternate key bindings for the built-in + line editor, if <a href="alt_edit_help.html">Alternate + Bindings</a> have been installed. Otherwise, Lynx uses the + <a href="edit_help.html">Default Binding</a>.</p> + + <h1><a name="PM">Personal Mail Address</a></h1> + + <p>You may set your mail address here so that when mailing + messages to other people or mailing files to yourself, your email + address can be automatically filled in. Your email address will + also be sent to HTTP servers in a `from:' field.</p> + + <h1><a name="PU">Pop-ups for select fields</a></h1> + + <p>Lynx normally uses a pop-up window for the OPTIONs in form + SELECT fields when the field does not have the MULTIPLE attribute + specified, and thus only one OPTION can be selected. The use of + pop-up windows can be disabled by changing this setting to OFF, + in which case the OPTIONs will be rendered as a list of radio + buttons. Note that if the SELECT field does have the MULTIPLE + attribute specified, the OPTIONs always are rendered as a list of + checkboxes.</p> + + <h1><a name="ST">Searching type</a></h1> + + <p>If set to 'case sensitive', user searches invoked by '/' will + be case-sensitive substring searches. Default is 'Case + Insensitive'.</p> + + <h1><a name="SC">Show color</a></h1> + + <p>This will be present if color support is available.</p> + + <ul> + <li>If set to ON or ALWAYS, color mode will be forced on if + possible. If (n)curses color support is available but cannot be + used for the current terminal type, selecting ON is rejected + with a message.</li> + + <li>If set to OFF or NEVER, color mode will be turned off.</li> + + <li>ALWAYS and NEVER are not offered in anonymous accounts. If + saved to a '.lynxrc' file in non-anonymous accounts, ALWAYS + will cause Lynx to set color mode on at startup if + supported.</li> + </ul>If Lynx is built with slang, this is equivalent to having + included the -color command line switch or having the COLORTERM + environment variable set. If color support is provided by curses + or ncurses, this is equivalent to the default behavior of using + color when the terminal type supports it. If (n)curses color + support is available but cannot be used for the current terminal + type, the preference can still be saved but will have no effect. + + <p>A saved value of NEVER will cause Lynx to assume a monochrome + terminal at start-up. It is similar to the -nocolor switch, but + (when the slang library is used) can be overridden with the + -color switch. If the setting is OFF or ON when the current + options are saved to a '.lynxrc' file, the default start-up + behavior is retained, such that color mode will be turned on at + startup only if the terminal info indicates that you have a + color-capable terminal, or (when slang is used) if forced on via + the -color switch or COLORTERM variable. This default behavior + always is used in anonymous accounts, or if the 'option'_save + restriction is set explicitly. If for any reason the start-up + color mode is incorrect for your terminal, set it appropriately + on or off via this option.</p> + + <h1><a name="CL">Show cursor for current link or option</a></h1> + + <p>Lynx normally hides the cursor by positioning it to the right + and if possible the very bottom of the screen, so that the + current link or OPTION is indicated solely by its highlighting or + color. If show cursor is set to ON, the cursor will be positioned + at the left of the current link or OPTION. This is helpful when + Lynx is being used with a speech or braille interface. It is also + useful for sighted users when the terminal cannot distinguish the + character attributes used to distinguish the current link or + OPTION from the others in the display.</p> + + <h1><a name="UM">User Mode</a></h1> + + <dl> + <dt><em>Novice</em>: Shows 2 extra lines of help at the bottom + of the screen for beginners.</dt> + + <dt><em>Intermediate (normal)</em>: Normal status-line messages + appear.</dt> + + <dt><em>Advanced</em>: The URL is shown on the status + line.</dt> + </dl> + + <h1><a name="AD">Assumed document character set</a></h1> + + <p>This changes the handling of documents which do not explicitly + specify a charset. Normally Lynx assumes that 8-bit characters in + those documents are encoded according to iso-8859-1 (the official + default for HTTP protocol). Unfortunately, many non-English web + pages forget to include proper charset info; this option helps + you browse those broken pages if you know somehow what the + charset is. When the value given here or by an -assume_charset + command-line flag is in effect, Lynx will treat documents as if + they were encoded accordingly. Option is active when 'Raw 8-bit + or CJK Mode' is OFF.</p> + + <h1><a name="JK">Raw 8-bit or CJK mode</a></h1> + + <p>This is set automatically, but can be toggled manually in + certain cases: it toggles whether 8-bit characters are assumed to + correspond with the display character set and therefore are + processed without translation via the chartrans conversion + tables. ON by default when the display character set is one of + the Asian (CJK) sets and the 8-bit characters are Kanji + multibytes. OFF for the other display character sets, but can be + turned ON when the document's charset is unknown (e.g., is not + ISO-8859-1 and no charset parameter was specified in a reply + header from an HTTP server to indicate what it is), but you have + no better idea than viewing it as from display character set (see + 'assumed document character set' for best choice). Should be OFF + when an Asian (CJK) set is selected but the document is + ISO-8859-1 or another 'assumed document character set'. The + setting can also be toggled via the RAW_TOGGLE command, normally + mapped to '@', and at startup via the -raw switch.</p> + + <h1><a name="tagsoup">HTML error recovery</a></h1> + + <p>Lynx often has to deal with invalid HTML markup. It always + tries to 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> + + <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 + <li>..</li> inside <a + HREF="some.url">..</a>. 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> + + <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 @@ -266,180 +327,205 @@ anchor text - those links are not reachable in SortaSGML (such markup should be placed outside <a>..</a> indeed). Default recovery mode can also be switched with CTRL-V key, from lynx.cfg or command line switch. ---> - +--></p> -<H1><A NAME="SI">Show Images</A></H1> + <h1><a name="SI">Show Images</a></h1> -This option combines the effects of the `*' & `[' keys as follows: -<pre> + <p>This option combines the effects of the `*' & `[' keys as + follows:</p> + <pre> <em>ignore</em> all images which lack an ALT= text string, - <em>show labels</em>, e.g. [INLINE] -- see `Verbose Images' below -- , + <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> -& <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 -& 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> -& <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 Filename', `By Size', `By Type', `By 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> +</pre> + + <p>This option setting cannot be saved between sessions. See + <a href="../Lynx_users_guide.html#Images">Users Guide</a> & + <em>lynx.cfg</em> for more details.</p> + + <h1><a name="VB">Verbose Images</a></h1> + + <p>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 & 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> & + <em>lynx.cfg</em> for more details.</p> + + <h1><a name="VI">VI keys</a></h1> + + <p>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> + + <p>The uppercase H, J, K, and L keys remain mapped to their + configured bindings (normally HELP, JUMP, KEYMAP and LIST, + respectively).</p> + + <p>Note: setting vi keys does not affect the line-editor + bindings.</p> + + <h1><a name="DC">Display Character set</a></h1> + + <p>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.</p> + + <h1><a name="DV">X DISPLAY variable</a></h1> + + <p>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.</p> + + <h1><a name="MB">Multi-bookmarks</a></h1> + + <p>Manage multiple bookmark files:</p> + + <ul> + <li>When OFF, the default bookmark file is used for the + 'v'iew-bookmarks and 'a'dd-bookmark link commands.</li> + + <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> + + <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.</li> + </ul> + + <h1><a name="BF">Bookmark file</a></h1> + + <p>Manage the default bookmark file:</p> + <ul> + <li>If non-empty and multi-bookmarks is OFF, it specifies your + default '<a href="bookmark_help.html">Bookmark file</a>'.</li> + + <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.</li> + </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.</p> + + <h1><a name="VP">Visited Pages</a></h1> + + <p>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:</p> + + <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> + + <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> + + <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> + + <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> + + <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.</dt> + </dl> + + <h1><a name="FT">FTP sort criteria</a></h1> + + <p>This allows you to specify how files will be sorted within FTP + listings. The current options include `By Filename', + `By Size', `By Type', `By Date'.</p> + + <h1><a name="LD">List directory style</a></h1> + + <p>Applies to Directory Editing. Files and directories can be + presented in the following ways:</p> + + <dl> + <dt><em>Mixed style</em>: Files and directories are listed + together in alphabetical order.</dt> + + <dt><em>Directories first</em>: Files and directories are + separated into 2 alphabetical lists: directories are listed + first.</dt> + + <dt><em>Files first</em>: Files and directories are separated + into 2 alphabetical lists: files are listed first.</dt> + </dl> + + <h1><a name="DF">Show dot files</a></h1> + + <p>If display/creation of hidden (dot) files/directories is + enabled, you can turn the feature on or off via this setting.</p> + + <h1><a name="PC">Preferred Document Charset</a></h1> + + <p>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>.</p> + + <h1><a name="PL">Preferred Document Language</a></h1> + + <p>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> + .</p> + + <h1><a name="UA">User Agent</a></h1> + + <p>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> + + <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'.</p> +</body> +</html> diff --git a/lynx_help/keystrokes/other_help.html b/lynx_help/keystrokes/other_help.html index 8ca89e84..866c4d9a 100644 --- a/lynx_help/keystrokes/other_help.html +++ b/lynx_help/keystrokes/other_help.html @@ -1,15 +1,23 @@ -<!DOCTYPE html PUBLIC "-//IETF//DTD HTML 3.0//EN"> -<HTML> -<HEAD> -<TITLE>Help on Misc. Lynx Commands</TITLE> -<LINK rev="made" href="mailto:lynx-dev@nongnu.org"> -<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1"> -</HEAD> -<BODY> -<h1>+++ Other Commands +++</h1> -<PRE> +<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 3.2//EN"> +<!-- $LynxId: other_help.html,v 1.12 2012/01/31 23:23:40 tom Exp $ --> + +<html> +<head> + <meta name="generator" content= + "HTML Tidy for Linux/x86 (vers 6 November 2007), see www.w3.org"> + + <title>Help on Misc. Lynx Commands</title> + <link rev="made" href="mailto:lynx-dev@nongnu.org"> + <meta http-equiv="Content-Type" content= + "text/html; charset=us-ascii"> +</head> + +<body> + <h1>Other Commands</h1> + <pre> a - Places the link that you are currently positioned - on into a personal <A HREF="bookmark_help.html">bookmark file</A>. + on into a personal <a href= +"bookmark_help.html">bookmark file</a>. c - Allows you to send a mail message to the owner or maintainer of the data that you are currently @@ -28,7 +36,8 @@ E - Allows you to edit the current link's URL (or ACTION) and use that as a <em>goto</em> URL. - g - Allows you to enter any <a href="http://archive.ncsa.uiuc.edu/demoweb/url-primer.html">URL</a> or filename that + g - Allows you to enter any <a href= +"http://archive.ncsa.uiuc.edu/demoweb/url-primer.html">URL</a> or filename that you wish to view, and then <em>goto</em> it. G - Allows you to edit the current document's URL and use that @@ -54,31 +63,37 @@ m - Returns to the first screen and empties the history stack. - p - Brings up a list of <A HREF="print_help.html">print commands</A>. + p - Brings up a list of <a href= +"print_help.html">print commands</a>. - o - Brings up a list of settable <A HREF="option_help.html">options</A>. + o - Brings up a list of settable <a href= +"option_help.html">options</a>. q - Quits Lynx. ('Q' quits without asking) / - Search for a string of characters in the current document (case insensitive or case sensitive - depending on the <A HREF="option_help.html">options</A> set). + depending on the <a href= +"option_help.html">options</a> set). s - Search through an external searchable indexed document. n - Move to the next instance of a search string if you have searched previously. - v - View a <A HREF="bookmark_help.html">Bookmark file</A>. + v - View a <a href= +"bookmark_help.html">Bookmark file</a>. - V - Go to the <A HREF="visited_help.html">Visited Links Page</A> + V - Go to the <a href= +"visited_help.html">Visited Links Page</a> x - Force submission of form or link with no-cache. z - Abort a network transfer in progress. If any partial data has been transferred it will be displayed. - <backspace> - displays the <a href="history_help.html">History Page</A>. + <backspace> - displays the <a href= +"history_help.html">History Page</a>. = - Show information about the file and link that you are currently viewing. @@ -117,7 +132,7 @@ display character set, and otherwise off so that 8-bit characters will be translated by Lynx with respect to the Assumed document charset, using approximations if necessary - (see <A HREF="option_help.html">options</A>). + (see <a href="option_help.html">options</a>). [ - Toggles pseudo_inlines mode on and off. When on, inline images which have no ALT string specified will have an @@ -147,8 +162,8 @@ CTRL-V - Switches to an alternative way of parsing HTML documents. This may help to get a more readable rendering of some - documents with invalidly placed HTML tags, <A - HREF="option_help.html#tagsoup">more details</A>. + documents with invalidly placed HTML tags, <a href= +"option_help.html#tagsoup">more details</a>. CTRL-W - Resets or cleans up the display. @@ -164,11 +179,11 @@ numbers - Lynx offers other, advanced navigation features when numbers are used to invoke the - <a href="follow_help.html" - >Follow link (or goto link or page) number:</a> or - <a href="follow_help.html#select-option" - >Select option (or page) number:</a> + <a href= +"follow_help.html">Follow link (or goto link or page) number:</a> or + <a href= +"follow_help.html#select-option">Select option (or page) number:</a> prompts. -</PRE> -</BODY> -</HTML> +</pre> +</body> +</html> diff --git a/lynx_help/keystrokes/print_help.html b/lynx_help/keystrokes/print_help.html index 26ef1fee..b6f14003 100644 --- a/lynx_help/keystrokes/print_help.html +++ b/lynx_help/keystrokes/print_help.html @@ -1,37 +1,49 @@ -<!DOCTYPE html PUBLIC "-//IETF//DTD HTML 3.0//EN"> -<HTML> -<HEAD> -<TITLE>Lynx Print Help</TITLE> -<LINK rev="made" href="mailto:lynx-dev@nongnu.org"> -<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1"> -</HEAD> -<BODY> -<h1>+++ Printing Help +++</h1> - -After entering the 'p' command you will be presented with a list of -print options. In all cases the file will be printed in ASCII format -with the hypertext links removed. The number of options depends on the -level of printing that your system allows. The following print options -may be available: - -<dl> -<dt>Print to a local file: -<dd>This allows you to save the current file as ASCII text to your - local disk. You will be asked for a path and filename to save - the file to. If no path is given, the file will be saved to the - directory that you were in when you began Lynx. - -<dt>Print to the screen: -<dd>This option simply scrolls the entire document up the screen and - is intended for those who wish to capture the document with their - terminal. - -<dt>Mail the file to yourself: -<dd>This option allows you to mail the file, in ASCII form, to any - valid e-mail address. - -<dt>Custom print options: -<dd>Any number of custom print options may be defined in <em>lynx.cfg</em>. -</dl> -</BODY> -</HTML> +<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 3.2//EN"> +<!-- $LynxId: print_help.html,v 1.6 2012/01/31 11:56:00 tom Exp $ --> + +<html> +<head> + <meta name="generator" content= + "HTML Tidy for Linux/x86 (vers 6 November 2007), see www.w3.org"> + + <title>Lynx Print Help</title> + <link rev="made" href="mailto:lynx-dev@nongnu.org"> + <meta http-equiv="Content-Type" content= + "text/html; charset=us-ascii"> +</head> + +<body> + <h1>Printing Help</h1> + + <p>After entering the 'p' command you will be presented with a + list of print options. In all cases the file will be printed in + ASCII format with the hypertext links removed. The number of + options depends on the level of printing that your system allows. + The following print options may be available:</p> + + <dl> + <dt>Print to a local file:</dt> + + <dd>This allows you to save the current file as ASCII text to + your local disk. You will be asked for a path and filename to + save the file to. If no path is given, the file will be saved + to the directory that you were in when you began Lynx.</dd> + + <dt>Print to the screen:</dt> + + <dd>This option simply scrolls the entire document up the + screen and is intended for those who wish to capture the + document with their terminal.</dd> + + <dt>Mail the file to yourself:</dt> + + <dd>This option allows you to mail the file, in ASCII form, to + any valid e-mail address.</dd> + + <dt>Custom print options:</dt> + + <dd>Any number of custom print options may be defined in + <em>lynx.cfg</em>.</dd> + </dl> +</body> +</html> diff --git a/lynx_help/keystrokes/scrolling_help.html b/lynx_help/keystrokes/scrolling_help.html index db43f062..872991c5 100644 --- a/lynx_help/keystrokes/scrolling_help.html +++ b/lynx_help/keystrokes/scrolling_help.html @@ -1,13 +1,20 @@ -<!DOCTYPE html PUBLIC "-//IETF//DTD HTML 3.0//EN"> -<HTML> -<HEAD> -<TITLE>Lynx Scrolling Help</TITLE> -<LINK rev="made" href="mailto:lynx-dev@nongnu.org"> -<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1"> -</HEAD> -<BODY> -<H1>+++ SCROLLING HELP +++</H1> -<PRE> +<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 3.2//EN"> +<!-- $LynxId: scrolling_help.html,v 1.8 2012/01/31 11:53:58 tom Exp $ --> + +<html> +<head> + <meta name="generator" content= + "HTML Tidy for Linux/x86 (vers 6 November 2007), see www.w3.org"> + + <title>Lynx Scrolling Help</title> + <link rev="made" href="mailto:lynx-dev@nongnu.org"> + <meta http-equiv="Content-Type" content= + "text/html; charset=us-ascii"> +</head> + +<body> + <h1>SCROLLING HELP</h1> + <pre> + (or SPACE, - If the bottom of the screen informs you or CTRL-F) that there is 'more' to see, you may move to the next page (Page-Down). @@ -62,6 +69,6 @@ present in the current document. Use left-arrow to return from there to your previous position in the document. -</PRE> -</BODY> -</HTML> +</pre> +</body> +</html> diff --git a/lynx_help/keystrokes/test_display.html b/lynx_help/keystrokes/test_display.html index c9445ff3..51dbbedb 100644 --- a/lynx_help/keystrokes/test_display.html +++ b/lynx_help/keystrokes/test_display.html @@ -1,4 +1,6 @@ <!DOCTYPE html PUBLIC "-//IETF//DTD HTML 3.0//EN"> +<!-- $LynxId: test_display.html,v 1.7 2012/01/31 11:53:11 tom Exp $ --> +<!-- do not use tidy for this page --> <HTML> <HEAD> <TITLE>Quick test for identifying display character set</TITLE> diff --git a/lynx_help/keystrokes/visited_help.html b/lynx_help/keystrokes/visited_help.html index 4c52378c..891845ea 100644 --- a/lynx_help/keystrokes/visited_help.html +++ b/lynx_help/keystrokes/visited_help.html @@ -1,37 +1,46 @@ -<!DOCTYPE html PUBLIC "-//IETF//DTD HTML 3.0//EN"> -<HTML> -<HEAD> -<TITLE>Help on the Visited Links Page</TITLE> -<LINK rev="made" href="mailto:lynx-dev@nongnu.org"> -<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1"> -</HEAD> -<BODY> -<h1>+++ Visited Links Page Help +++</h1> +<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 3.2//EN"> +<!-- $LynxId: visited_help.html,v 1.7 2012/01/31 11:50:47 tom Exp $ --> -The Visited Links Page displays all of the links that you have traveled -through during the current Lynx session, except for any temporary menu -or list files, bookmark files, or any documents associated with POST -content. The VLINKS keystroke command for invoking this page normally -is mapped to uppercase '<em>V</em>'. The list of Visited Links is normally in -order of recency (most recently visited links first), without repetitions -in the list if a link was visited more than once during the session (unless -the URLs differ due to appended fragments), and is supplementary to the -<A HREF="history_help.html">History Page</A>. +<html> +<head> + <meta name="generator" content= + "HTML Tidy for Linux/x86 (vers 6 November 2007), see www.w3.org"> -<p>You may <A HREF="movement_help.html">select</A> any link on the Visited -Links Page to retrieve a document that you had previously visited, or you -can use this list to save such links in your <A HREF="bookmark_help.html" ->bookmark files</A>, or to <A HREF="../Lynx_users_guide.html#RemoteSource" ->Download</A> them. + <title>Help on the Visited Links Page</title> + <link rev="made" href="mailto:lynx-dev@nongnu.org"> + <meta http-equiv="Content-Type" content= + "text/html; charset=us-ascii"> +</head> -<p>In contrast to the History Page, the Visited Links Page includes any -links which were retrieved for '<em>d</em>'ownloading or were passed to -helper applications, i.e., not just the links that were rendered and -displayed by Lynx, itself. +<body> + <h1>Visited Links Page Help</h1> -<p>You may change the appearance of the Visited Links Page via a popup -menu on that page (which also appears on the -<A HREF="option_help.html#VP">Options Menu</A>). + <p>The Visited Links Page displays all of the links that you have + traveled through during the current Lynx session, except for any + temporary menu or list files, bookmark files, or any documents + associated with POST content. The VLINKS keystroke command for + invoking this page normally is mapped to uppercase '<em>V</em>'. + The list of Visited Links is normally in order of recency (most + recently visited links first), without repetitions in the list if + a link was visited more than once during the session (unless the + URLs differ due to appended fragments), and is supplementary to + the <a href="history_help.html">History Page</a>.</p> -</BODY> -</HTML> + <p>You may <a href="movement_help.html">select</a> any link on + the Visited Links Page to retrieve a document that you had + previously visited, or you can use this list to save such links + in your <a href="bookmark_help.html">bookmark files</a>, or to + <a href="../Lynx_users_guide.html#RemoteSource">Download</a> + them.</p> + + <p>In contrast to the History Page, the Visited Links Page + includes any links which were retrieved for + '<em>d</em>'ownloading or were passed to helper applications, + i.e., not just the links that were rendered and displayed by + Lynx, itself.</p> + + <p>You may change the appearance of the Visited Links Page via a + popup menu on that page (which also appears on the <a href= + "option_help.html#VP">Options Menu</a>).</p> +</body> +</html> diff --git a/lynx_help/keystrokes/xterm_help.html b/lynx_help/keystrokes/xterm_help.html index d2295c2f..e76674ca 100644 --- a/lynx_help/keystrokes/xterm_help.html +++ b/lynx_help/keystrokes/xterm_help.html @@ -1,33 +1,43 @@ -<!DOCTYPE html PUBLIC "-//IETF//DTD HTML 3.0//EN"> -<HTML> -<HEAD> -<TITLE>X Terminal Help</TITLE> -<LINK rev="made" href="mailto:lynx-dev@nongnu.org"> -<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1"> -</HEAD> -<BODY> -<h1>+++ X Terminal or X Server +++</h1> - -An X terminal is an electronic display terminal that communicates -with a host computer system using the X Window protocol developed at the -Massachusetts Institute of Technology. - -<p>The X Window protocol allows a program running on the host computer -system to display both formatted text and graphics on the X terminal. -Since the X Window protocol is defined to work over any TCP/IP network, -X terminals connected to the Internet can be connected to hosts -located anywhere on the Internet. - -<p>Personal computers (including both PCs and Macintoshes) can execute -programs, usually called X servers, that make them act like X Window -terminals and are frequently used as X terminals. - -<dl> -<dt>Note: -<dd>The terminology used to describe processes associated with X - terminals can be confusing. An X terminal is also known as - an "X display server," and the program running on the host - computer is usually known as the "X client." -</dl> -</BODY> -</HTML> +<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 3.2//EN"> +<!-- $LynxId: xterm_help.html,v 1.6 2012/01/31 11:49:45 tom Exp $ --> + +<html> +<head> + <meta name="generator" content= + "HTML Tidy for Linux/x86 (vers 6 November 2007), see www.w3.org"> + + <title>X Terminal Help</title> + <link rev="made" href="mailto:lynx-dev@nongnu.org"> + <meta http-equiv="Content-Type" content= + "text/html; charset=us-ascii"> +</head> + +<body> + <h1>X Terminal or X Server</h1> + + <p>An X terminal is an electronic display terminal that + communicates with a host computer system using the X Window + protocol developed at the Massachusetts Institute of + Technology.</p> + + <p>The X Window protocol allows a program running on the host + computer system to display both formatted text and graphics on + the X terminal. Since the X Window protocol is defined to work + over any TCP/IP network, X terminals connected to the Internet + can be connected to hosts located anywhere on the Internet.</p> + + <p>Personal computers (including both PCs and Macintoshes) can + execute programs, usually called X servers, that make them act + like X Window terminals and are frequently used as X + terminals.</p> + + <dl> + <dt>Note:</dt> + + <dd>The terminology used to describe processes associated with + X terminals can be confusing. An X terminal is also known as an + "X display server," and the program running on the host + computer is usually known as the "X client."</dd> + </dl> +</body> +</html> |