diff options
Diffstat (limited to 'lynx_help/keystrokes')
| -rw-r--r-- | lynx_help/keystrokes/alt_edit_help.html | 58 | ||||
| -rw-r--r-- | lynx_help/keystrokes/bashlike_edit_help.html | 145 | ||||
| -rw-r--r-- | lynx_help/keystrokes/bookmark_help.html | 21 | ||||
| -rw-r--r-- | lynx_help/keystrokes/cookie_help.html | 45 | ||||
| -rw-r--r-- | lynx_help/keystrokes/dired_help.html | 85 | ||||
| -rw-r--r-- | lynx_help/keystrokes/edit_help.html | 72 | ||||
| -rw-r--r-- | lynx_help/keystrokes/environments.html | 462 | ||||
| -rw-r--r-- | lynx_help/keystrokes/follow_help.html | 398 | ||||
| -rw-r--r-- | lynx_help/keystrokes/gopher_types_help.html | 8 | ||||
| -rw-r--r-- | lynx_help/keystrokes/history_help.html | 29 | ||||
| -rw-r--r-- | lynx_help/keystrokes/keystroke_help.html | 26 | ||||
| -rw-r--r-- | lynx_help/keystrokes/movement_help.html | 40 | ||||
| -rw-r--r-- | lynx_help/keystrokes/option_help.html | 706 | ||||
| -rw-r--r-- | lynx_help/keystrokes/other_help.html | 26 | ||||
| -rw-r--r-- | lynx_help/keystrokes/print_help.html | 27 | ||||
| -rw-r--r-- | lynx_help/keystrokes/scrolling_help.html | 98 | ||||
| -rw-r--r-- | lynx_help/keystrokes/test_display.html | 33 | ||||
| -rw-r--r-- | lynx_help/keystrokes/visited_help.html | 40 | ||||
| -rw-r--r-- | lynx_help/keystrokes/xterm_help.html | 8 |
19 files changed, 1449 insertions, 878 deletions
diff --git a/lynx_help/keystrokes/alt_edit_help.html b/lynx_help/keystrokes/alt_edit_help.html index 5eed64e5..2268a819 100644 --- a/lynx_help/keystrokes/alt_edit_help.html +++ b/lynx_help/keystrokes/alt_edit_help.html @@ -1,4 +1,4 @@ -<!-- $LynxId: alt_edit_help.html,v 1.10 2013/05/21 10:51:27 tom Exp $ --> +<!-- $LynxId: alt_edit_help.html,v 1.11 2014/01/08 00:56:30 tom Exp $ --> <!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01//EN"> <html> @@ -14,24 +14,29 @@ "bashlike_edit_help.html"> <meta http-equiv="Content-Type" content= "text/html; charset=us-ascii"> -</head> + <meta name="description" content= + "Describes an alternative set of line editor bindings for Lynx. This is one of the alternate bindings normally compiled-in"> + </head> <body> - <h1>ALTERNATIVE BINDING</h1> + <h2>Overview</h2> - <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><strong>Lynx</strong> invokes a built-in <a href= + "edit_help.html">Line Editor</a> 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 + <code>--enable-alt-bindings</code> or by adding them in + LYEditmap.c before compiling <strong>Lynx</strong>. 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> - <p>This is the <em>Alternative Binding</em> keymap:</p> + <p>This is the <em>Alternative Binding</em> keymap.</p> + + <h2>Table of key-bindings</h2> <pre> ENTER Input complete - RETURN TAB Input complete - TAB, Do @@ -46,7 +51,7 @@ EOL Go to end of line - Ctrl-E, End, Select DELP Delete prev char - Ctrl-H, DELETE, Remove - DELN Delete next [1] char - Ctrl-D + DELN Delete next char - Ctrl-D (<em>see note 1</em>) DELPW Delete prev word - Ctrl-R DELNW Delete next word - Ctrl-T DELEL Delete to end of line - Ctrl-K @@ -54,25 +59,30 @@ UPPER Upper case the line - Ctrl-^ LOWER Lower case the line - Ctrl-_ - LKCMD Invoke cmd prompt - Ctrl-V (in form text fields, only) [2] + LKCMD Invoke cmd prompt - Ctrl-V (in form text fields, only) (<em>see note 2</em>) <a name="TASpecial" id= -"TASpecial">Special commands for use only in textarea fields</a>[3]: +"TASpecial">Special commands for use only in textarea fields</a>(<em>see note 3</em>): Textarea external edit - Ctrl-X e Insert file in textarea - Ctrl-X i Grow textarea - Ctrl-X g +</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. + <h2>Notes</h2> -[2] Follow Ctrl-V with any recognized key command, to "escape" from a text - input field. + <ol> + <li>"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.</li> -[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. -</pre> + <li>Follow Ctrl-V with any recognized key command, to "escape" + from a text input field.</li> + + <li>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.</li> + </ol> </body> </html> diff --git a/lynx_help/keystrokes/bashlike_edit_help.html b/lynx_help/keystrokes/bashlike_edit_help.html index bb175990..b62e6cb3 100644 --- a/lynx_help/keystrokes/bashlike_edit_help.html +++ b/lynx_help/keystrokes/bashlike_edit_help.html @@ -1,4 +1,4 @@ -<!-- $LynxId: bashlike_edit_help.html,v 1.9 2013/05/22 00:25:19 tom Exp $ --> +<!-- $LynxId: bashlike_edit_help.html,v 1.10 2014/01/08 00:50:05 tom Exp $ --> <!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01//EN"> <html> @@ -14,45 +14,47 @@ "alt_edit_help.html"> <meta http-equiv="Content-Type" content= "text/html; charset=us-ascii"> -</head> + <meta name="description" content= + "Describes the bash-like line editor bindings for Lynx. This is one of the alternate bindings normally compiled-in"> + </head> <body> - <h1>BASH-LIKE BINDING</h1> + <h2>Overview</h2> - <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>Lynx invokes a built-in <a href="edit_help.html">Line + Editor</a> 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> - <p>This is the <em>Bash-like Binding</em> keymap.</p> + <p>This summarizes the <em>Bash-like Binding</em> keymap.</p> <h2>Basic commands</h2> <pre> ENTER Input complete - Enter, RETURN - TAB Completion [2]/ Next - TAB, Do + TAB Completion / Next - TAB, Do (<em>see note 2</em>) ABORT Cancel / Undo Change - C-g, C-_ ERASE Erase the line - M-k, C-x k BACK Cursor back char - Left-Arrow, C-b FORW Cursor forward char - Right-Arrow, C-f BACKW Cursor back word - M-b, C-r - FORWW Cursor forward word - M-f, C-s [5] + FORWW Cursor forward word - M-f, C-s (<em>see note 5</em>) BOL Go to begin of line - C-a, Home, Find - EOL Go to end of line - C-e [4], End, Select + EOL Go to end of line - C-e, End, Select (<em>see note 4</em>) DELP Delete prev char - C-h, Backspace, Rubout - DELN Delete next [1] char - C-d, Delete, Remove - DELPW Delete prev word - C-w [3], M-Backspace, M-Delete (?) + DELN Delete next char - C-d, Delete, Remove (<em>see note 1</em>) + DELPW Delete prev word - C-w, M-Backspace, M-Delete (?) (<em>see note 3</em>) DELNW Delete next word - M-d DELBL Delete to beg of line - C-u - DELEL Delete to end of line - C-k [4] + DELEL Delete to end of line - C-k (<em>see note 4</em>) UPPER Upper case the line - M-u LOWER Lower case the line - M-l @@ -63,11 +65,13 @@ <a name="TASpecial" id= "TASpecial">Special commands for use in textarea fields</a> [FORM]: - PASS! Textarea external edit - C-e C-e [4], C-x e + PASS! Textarea external edit - C-e C-e, C-x e (<em>see note 4</em>) PASS! Insert file in textarea - C-x i PASS! Grow textarea - C-x g </pre> + <h2>Try it yourself</h2> + <p>Here is a little textarea for practice:</p> <form action=""> @@ -79,18 +83,18 @@ 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]"></p> </form> - <pre> -Advanced emacs-like commands: + <h2>Advanced emacs-like commands</h2> + <pre> TPOS Transpose characters - C-t SETMARK Set mark at current position in line - C-@ XPMARK Exchange current position with mark - C-x C-x - KILLREG Kill region between mark and position - C-x C-w [3] + KILLREG Kill region between mark and position - C-x C-w (<em>see note 3</em>) YANK Insert text last killed (with KILLREG) - C-y </pre> - <h2>Notes</h2> + <h2>Comments on special keys</h2> <p><samp><dfn>C-</dfn><strong>key</strong> means Control+<strong><kbd>key</kbd></strong>. @@ -121,58 +125,69 @@ Advanced emacs-like commands: 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. -[2] For entering strings in response to prompts (that is, when not editing - form text fields), some keys have different actions: TAB tries to - complete input based on previous response; Up-Arrow and Down-Arrow - may offer previous response and next response, respectively, from - recall buffer for some prompts. -[3] C-w can only be used for editing functions if its default KEYMAP - to REFRESH is changed. This can be done in the lynx.cfg file, - for example with the line "KEYMAP:^W:DO_NOTHING". This also applies - for other keys: as long as the key's action is mapped to REFRESH, - either with an explicit KEYMAP in lynx.cfg or by default, the - key's Line Editor binding is disabled. -[4] These keys invoke special behavior when pressed twice in a row: - C-e C-e calls the external editor for changing the text in a - textarea (if available). C-k C-k will move to the next link, + + <h2>Notes</h2> + + <ol> + <li>"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.</li> + + <li>For entering strings in response to prompts (that is, when + not editing form text fields), some keys have different + actions: TAB tries to complete input based on previous + response; Up-Arrow and Down-Arrow may offer previous response + and next response, respectively, from recall buffer for some + prompts.</li> + + <li>C-w can only be used for editing functions if its default + KEYMAP to REFRESH is changed. This can be done in the lynx.cfg + file, for example with the line "KEYMAP:^W:DO_NOTHING". This + also applies for other keys: as long as the key's action is + mapped to REFRESH, either with an explicit KEYMAP in lynx.cfg + or by default, the key's Line Editor binding is disabled.</li> + + <li>These keys invoke special behavior when pressed twice in a + row: C-e C-e calls the external editor for changing the text in + a textarea (if available). C-k C-k will move to the next link, so that all lines in a textarea can be conveniently cleared by - repeating C-k. -[5] Key is likely unavailable for Lynx, because it is interpreted by - operating system, comm program, or curses library, or swallowed - as part of escape sequence recognition. Binding is provided for - 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, - the Line Editor functions get a first grab at the keys entered. - 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). -</pre> + repeating C-k.</li> + + <li>Key is likely unavailable for Lynx, because it is + interpreted by operating system, comm program, or curses + library, or swallowed as part of escape sequence recognition. + Binding is provided for the benefit of those where this doesn't + apply.</li> + + <li>where <strong>[FORM]</strong> is marked, indicates that the + binding is effective only in form text fields. It is ignored by + Line Editor elsewhere.</li> + </ol> + + <p>When a text input field, including a textarea line, is + selected, the Line Editor functions get a first grab at the keys + entered. 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).</p> <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] + C-l (<em>see note 3</em>) C-o, C-z [5], C-\ [5], C-] [5] (<em>see note 5</em>) C-n [emacskey], C-p [emacskey] - Up-Arrow [2], Down-Arrow [2] + Up-Arrow, Down-Arrow (<em>see note 2</em>) Page-Up, Page-Down, F1, Back-Tab Normal key command with Meta modifier ignored when used in form fields, subject to remapping with KEYMAP: [FORM (except Up-Arrow, Down-Arrow)] - M-C-l [3], M-C-o [!], M-C-z [5], M-C-\ [5], M-C-] [5] + M-C-l (<em>see note 3</em>) M-C-o [!], M-C-z [5], M-C-\ [5], M-C-] [5] (<em>see note 5</em>) M-C-u, M-/, M-n - M-Up-Arrow [2][!], M-Down-Arrow [2][!] + M-Up-Arrow [!], M-Down-Arrow [!] (<em>see note 2</em>) M-Page-Up [!], M-Page-Down [!], M-Home, M-End Passed as specific command: @@ -216,12 +231,12 @@ Modifier ignored, and duplicates function of other key(s): Key completely ignored: C-q, Insert - M-C-q, M-C-s [5], M-C-t, M-C-v, M-ESC + M-C-q, M-C-s [5], M-C-t, M-C-v, M-ESC (<em>see note 5</em>) M-C-@, M-C-_, M-Remove, M-Insert [!] Meta + other (mostly, printable character) keys: - Modifier ignored, or sequence swallowed (see [5]). - M-@, M-E...M-Z [5], M-\, M-^, M-_ attempt to interpret + Modifier ignored, or sequence swallowed (<em>see note 5</em>). + M-@, M-E...M-Z, M-\, M-^, M-_ attempt to interpret as 7-bit escape representation for character in 8-bit control (C1) range if appropriate according to Display Character Set. diff --git a/lynx_help/keystrokes/bookmark_help.html b/lynx_help/keystrokes/bookmark_help.html index 66eafbf6..87187fd1 100644 --- a/lynx_help/keystrokes/bookmark_help.html +++ b/lynx_help/keystrokes/bookmark_help.html @@ -1,4 +1,4 @@ -<!-- $LynxId: bookmark_help.html,v 1.7 2013/05/21 10:51:27 tom Exp $ --> +<!-- $LynxId: bookmark_help.html,v 1.8 2014/01/07 23:32:23 tom Exp $ --> <!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01//EN"> <html> @@ -6,17 +6,20 @@ <meta name="generator" content= "HTML Tidy for Linux (vers 25 March 2009), see www.w3.org"> - <title>Lynx Bookmark Help</title> + <title>Lynx Bookmark Help Summary</title> <link rev="made" href="mailto:lynx-dev@nongnu.org"> <meta http-equiv="Content-Type" content= "text/html; charset=us-ascii"> -</head> + <meta name="description" content= + "Lynx stores Bookmark files on your local machine. You can update these from within Lynx, or with a text editor"> + </head> <body> - <h1>Bookmark Help</h1> + <p><strong>Lynx</strong> stores <em>Bookmark files</em> on your + local machine. You can update these from within + <strong>Lynx</strong>, or with a text editor:</p> - <p><em>Bookmark files</em> are documents that reside on your - local machine and you are able to edit and change:</p> + <h2>Updating within Lynx</h2> <ul> <li>The append feature, invoked by pressing an '<em>a</em>' @@ -34,5 +37,11 @@ bookmarks in the <a href="option_help.html">Options Menu</a>.</li> </ul> + + <h2>Updating with a text editor</h2> + + <p>Lynx stores its bookmarks as an HTML file, using an unordered + list (<em>UL</em> and <em>LI</em> tags). It expects the list + items to be one per line, without wrapping.</p> </body> </html> diff --git a/lynx_help/keystrokes/cookie_help.html b/lynx_help/keystrokes/cookie_help.html index 60920128..0f7378b8 100644 --- a/lynx_help/keystrokes/cookie_help.html +++ b/lynx_help/keystrokes/cookie_help.html @@ -1,4 +1,4 @@ -<!-- $LynxId: cookie_help.html,v 1.8 2013/05/21 10:51:27 tom Exp $ --> +<!-- $LynxId: cookie_help.html,v 1.9 2014/01/07 09:14:46 tom Exp $ --> <!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01//EN"> <html> @@ -10,29 +10,33 @@ <link rev="made" href="mailto:lynx-dev@nongnu.org"> <meta http-equiv="Content-Type" content= "text/html; charset=us-ascii"> -</head> + <meta name="description" content= + "Lynx provides a page show shows information about all of the unexpired cookies, including their fully qualified domain name, expiration time and name/value pairs."> + </head> <body> - <h1>Cookie Jar Page Help</h1> + <h2>Overview</h2> - <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><strong>Lynx</strong>'s <em>Cookie Jar Page</em> 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> + When <strong>Lynx</strong> 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> + + <h2>Cookie Details Shown</h2> <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 @@ -41,9 +45,12 @@ 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> + replies to subsequent requests from <strong>Lynx</strong>. If the + server included any explanatory comments in its + <em>Set-Cookie</em> MIME headers, those also are displayed in the + listing.</p> + + <h2>Removing Cookies</h2> <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 diff --git a/lynx_help/keystrokes/dired_help.html b/lynx_help/keystrokes/dired_help.html index c5cb3dbc..bf5701be 100644 --- a/lynx_help/keystrokes/dired_help.html +++ b/lynx_help/keystrokes/dired_help.html @@ -1,4 +1,4 @@ -<!-- $LynxId: dired_help.html,v 1.8 2013/05/21 10:51:27 tom Exp $ --> +<!-- $LynxId: dired_help.html,v 1.9 2014/01/08 01:15:55 tom Exp $ --> <!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01//EN"> <html> @@ -6,57 +6,72 @@ <meta name="generator" content= "HTML Tidy for Linux (vers 25 March 2009), see www.w3.org"> - <title>Lynx Dired Help</title> + <title>Lynx Dired-mode Key Bindings</title> <link rev="made" href="mailto:lynx-dev@nongnu.org"> <meta http-equiv="Content-Type" content= "text/html; charset=us-ascii"> -</head> + <meta name="description" content= + "Lynx's dired-mode allows you to browse for file-URLs. This describes the key-bindings for dired-mode."> + </head> <body> - <h1>DIRED HELP</h1> + <h2>Overview</h2> - <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> + <p><strong>Lynx</strong> changes into <em>Dired mode</em> when + you use a URL of the type <em>file://localhost/path/</em>.</p> - C)reate - Create a new, empty file in the current - directory. You will be prompted to enter - a name for the file. + <h2>Key bindings</h2> - F)ull menu - Show a full menu of commands for currently - selected file or directory. + <p>While in Dired mode, some keys are remapped to do the + following functions:</p> - M)odify - Modify the name or location of selection. If - multiple files have been selected, you will - only be able to change the location. Choose - between changing the name or location and then - enter a new filename or path. + <blockquote> + <pre> - R)emove - Delete currently selected files. + C)reate - Create a new, empty file in the current + directory. You will be prompted to enter + a name for the file. - T)ag - Tag the highlighted file. Multiple files may - be tagged and all other commands except "Create" - will be performed on tagged files instead of the - one highlighted. Press '<em>t</em>' again to untag - a file. + F)ull menu - Show a full menu of commands for currently + selected file or directory. - U)pload - Upload a file to the current directory using - one of the options listed in the upload screen. + M)odify - Modify the name or location of selection. If + multiple files have been selected, you will + only be able to change the location. Choose + between changing the name or location and then + enter a new filename or path. + + R)emove - Delete currently selected files. + + T)ag - Tag the highlighted file. Multiple files may + be tagged and all other commands except "Create" + will be performed on tagged files instead of the + one highlighted. Press '<em>t</em>' again to untag + a file. + + U)pload - Upload a file to the current directory using + one of the options listed in the upload screen. </pre> + </blockquote> - <p>Some other keys useful in Dired mode:</p> - <pre> - D)ownload - Download selection using options listed in - the download options screen. + <p>Some other keys useful in <em>Dired mode</em>:</p> - E)dit - Spawn the editor defined in the <a href= + <blockquote> + <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> - and load selection for editing. + and load selection for editing. </pre> + </blockquote> + + <h2>Notes</h2> - <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> + <p><em>Dired mode</em> must be activated at compile time. + Otherwise, the above commands will not be available and + <strong>Lynx</strong> 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 9a9773fb..eb8b0c62 100644 --- a/lynx_help/keystrokes/edit_help.html +++ b/lynx_help/keystrokes/edit_help.html @@ -1,4 +1,4 @@ -<!-- $LynxId: edit_help.html,v 1.15 2013/10/16 22:44:55 tom Exp $ --> +<!-- $LynxId: edit_help.html,v 1.17 2014/01/08 21:24:50 tom Exp $ --> <!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01//EN"> <html> @@ -10,27 +10,43 @@ <link rev="made" href="mailto:lynx-dev@nongnu.org"> <meta http-equiv="Content-Type" content= "text/html; charset=us-ascii"> -</head> + <meta name="description" content= + " Describes Lynx's built-in line-editor, when it is used, and the keys used for the default binding. There are alternate and special bindings."> + </head> <body> - <h1>DEFAULT BINDING</h1> + <h2>Overview</h2> - <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 are normally available (unless Lynx was configured with + <p><strong>Lynx</strong> 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 are normally available (unless + <strong>Lynx</strong> was configured with <code>--disable-alt-bindings</code>). If available, they may be selected via the 'o'ptions menu, or by editing lineedit_mode in the '.lynxrc' file.</p> <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> + your system, are the</p> + + <ul> + <li><a href="alt_edit_help.html">Alternative Binding</a> keymap + and the</li> + + <li><a href="bashlike_edit_help.html">Bash-like Binding</a> + keymap.</li> + </ul> + + <p>You can always see the current set of key-bindings in + <strong>Lynx</strong> by opening the special URL <a href= + "LYNXEDITMAP:">LYNXEDITMAP:</a>. This page is provided for those + not using Lynx.</p> <p>Note: setting emacs/vi keys ON has no effect on line-editor bindings.</p> + <h2>Regular Keymap</h2> + <p>This is the <em>Default Binding</em> keymap:</p> <pre> ENTER Input complete - RETURN @@ -46,7 +62,7 @@ EOL Go to end of line - Ctrl-E, End, Select DELP Delete prev char - Ctrl-H, DELETE, Remove - DELN Delete next [1] char - Ctrl-D, Ctrl-R + DELN Delete next char - Ctrl-D, Ctrl-R (see note 1) DELPW Delete prev word - Ctrl-B DELNW Delete next word - Ctrl-F DELEL Delete to end of line - Ctrl-_ @@ -54,26 +70,36 @@ UPPER Upper case the line - Ctrl-T LOWER Lower case the line - Ctrl-K - LKCMD Invoke cmd prompt - Ctrl-V (in form text fields, only) [2] + LKCMD Invoke cmd prompt - Ctrl-V (in form text fields, only) (see note 2) SWMAP Switch input keymap - Ctrl-^ (if compiled in) -<a name="TASpecial" id= -"TASpecial">Special commands for use only in textarea fields</a>[3]: +</pre> + + <h2>Editing Keymap</h2> + + <p><a name="TASpecial" id="TASpecial">These are special commands + for use only in textarea fields</a> (see note 3):</p> + <pre> Textarea external edit - Ctrl-X e Insert file in textarea - Ctrl-X i Grow textarea - Ctrl-X g +</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. + <h2>Notes</h2> -[2] Follow Ctrl-V with any recognized key command, to "escape" from a text - input field. + <ol> + <li>"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.</li> -[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. -</pre> + <li>Follow Ctrl-V with any recognized key command, to "escape" + from a text input field.</li> + + <li>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.</li> + </ol> </body> </html> diff --git a/lynx_help/keystrokes/environments.html b/lynx_help/keystrokes/environments.html index e898ef47..68425cb4 100644 --- a/lynx_help/keystrokes/environments.html +++ b/lynx_help/keystrokes/environments.html @@ -1,4 +1,4 @@ -<!-- $LynxId: environments.html,v 1.15 2013/05/21 10:51:27 tom Exp $ --> +<!-- $LynxId: environments.html,v 1.16 2014/01/08 01:38:23 tom Exp $ --> <!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01//EN"> <html> @@ -6,22 +6,22 @@ <meta name="generator" content= "HTML Tidy for Linux (vers 25 March 2009), see www.w3.org"> - <title>Help on Environment variables</title> + <title>Help on Lynx's Environment variables</title> <link rev="made" href="mailto:lynx-dev@nongnu.org"> <meta http-equiv="Content-Type" content= "text/html; charset=us-ascii"> -</head> + <meta name="description" content= + "Describes environment variables used by Lynx. Some are specific to Lynx, others are common with similar programs."> + </head> <body> + <h2>ENVIRONMENT</h2> <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>. + such as HOME, PATH, USER, DISPLAY, TMPDIR, etc, <strong>Lynx</strong> utilizes + several <strong>Lynx</strong>-specific environment variables, <a href="#env">if they exist</a>. - Others may be created or modified by Lynx to pass data to + Others may be created or modified by <strong>Lynx</strong> to pass data to an external program, or for other reasons. These are listed separately <a href="#setenv">below</a>. @@ -30,19 +30,20 @@ <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 + platforms supported by <strong>Lynx</strong>, though most do. Feedback on platform dependencies is solicited. See also <a href= "#dos">win32/dos</a> specific variables. +</pre> -<a name="env" id="env"><em> -Environment Variables Used By Lynx: -</em></a> + <h2><a name="env" id="env">Environment Variables Used By + Lynx</a></h2> + <pre> COLORTERM If set, color capability for the terminal is forced on at startup time. The actual value assigned to the variable is ignored. - This variable is only meaningful if Lynx + This variable is only meaningful if <strong>Lynx</strong> was built using the slang screen-handling library. @@ -59,7 +60,7 @@ Environment Variables Used By Lynx: LYNX_HELPFILE If set, this variable overrides the compiled-in URL and configuration file - URL for the lynx help file. + URL for the <strong>Lynx</strong> help file. LYNX_LOCALEDIR If set, this variable overrides the @@ -69,9 +70,9 @@ Environment Variables Used By Lynx: LYNX_LSS This variable, if set, specifies the - location of the default Lynx character + location of the default <strong>Lynx</strong> character style sheet file. [Currently only - meaningful if Lynx was built using + meaningful if <strong>Lynx</strong> was built using experimental color style support.] LYNX_SAVE_SPACE @@ -89,7 +90,7 @@ Environment Variables Used By Lynx: be assigned to the TMPDIR variable. LYNX_TRACE - If set, causes Lynx to write a trace + If set, causes <strong>Lynx</strong> to write a trace file as if the -trace option were sup- plied. @@ -103,7 +104,7 @@ Environment Variables Used By Lynx: MAIL This variable specifies the default - inbox Lynx will check for new mail, if + inbox <strong>Lynx</strong> will check for new mail, if such checking is enabled in the lynx.cfg file. @@ -120,7 +121,7 @@ Environment Variables Used By Lynx: If set, this variable specifies the default NNTP server that will be used for USENET news reading and posting - with Lynx, via news: URL's. + with <strong>Lynx</strong>, via news: URL's. ORGANIZATION This variable, if set, provides the @@ -130,12 +131,12 @@ Environment Variables Used By Lynx: an /etc/organization file, if present. PROTOCOL_proxy - Lynx supports the use of proxy servers + <strong>Lynx</strong> supports the use of proxy servers that can act as firewall gateways and caching servers. They are preferable to the older gateway servers (see WWW_access_GATEWAY, below). - Each protocol used by Lynx (http, ftp, + Each protocol used by <strong>Lynx</strong> (http, ftp, gopher, etc), can be mapped separately by setting environment variables of the form PROTOCOL_proxy (literally: @@ -145,7 +146,7 @@ Environment Variables Used By Lynx: "#proxy">Proxy details and examples</a>. WWW_access_GATEWAY - Lynx still supports use of gateway + <strong>Lynx</strong> still supports use of gateway servers, with the servers specified via "WWW_access_GATEWAY" variables (where "access" is lower case and can @@ -160,13 +161,13 @@ Environment Variables Used By Lynx: WWW_HOME This variable, if set, will override the default startup URL specified in - any of the Lynx configuration files. - -<a name="setenv" id="setenv"><em> -Environment Variables Set or Modified By Lynx: -</em></a> + any of the <strong>Lynx</strong> configuration files. +</pre> - LYNX_PRINT_DATE This variable is set by the Lynx + <h2><a name="setenv" id="setenv">Environment Variables Set or + Modified By Lynx</a></h2> + <pre> + LYNX_PRINT_DATE This variable is set by the <strong>Lynx</strong> p(rint) function, to the Date: string seen in the document's "Information about" page (= cmd), if any. It is @@ -177,7 +178,7 @@ Environment Variables Set or Modified By Lynx: the variable is set to a null string under UNIX, or "No Date" under VMS. - LYNX_PRINT_LASTMOD This variable is set by the Lynx + LYNX_PRINT_LASTMOD This variable is set by the <strong>Lynx</strong> p(rint) function, to the Last Mod: string seen in the document's "Information about" page (= cmd), if any. @@ -188,7 +189,7 @@ Environment Variables Set or Modified By Lynx: the variable is set to a null string under UNIX, or "No LastMod" under VMS. - LYNX_PRINT_TITLE This variable is set by the Lynx + LYNX_PRINT_TITLE This variable is set by the <strong>Lynx</strong> p(rint) function, to the Linkname: string seen in the document's "Information about" page (= cmd), if any. @@ -199,7 +200,7 @@ Environment Variables Set or Modified By Lynx: the variable is set to a null string under UNIX, or "No Title" under VMS. - LYNX_PRINT_URL This variable is set by the Lynx + LYNX_PRINT_URL This variable is set by the <strong>Lynx</strong> p(rint) function, to the URL: string seen in the document's "Information about" page (= cmd), if any. It is @@ -210,10 +211,10 @@ Environment Variables Set or Modified By Lynx: the variable is set to a null string under UNIX, or "No URL" under VMS. - LYNX_VERSION This variable is always set by Lynx, + LYNX_VERSION This variable is always set by <strong>Lynx</strong>, and may be used by an external program to determine if it was invoked by - Lynx. See also the comments in the + <strong>Lynx</strong>. See also the comments in the distribution's sample mailcap file, for notes on usage in such a file. @@ -224,29 +225,29 @@ Environment Variables Set or Modified By Lynx: your file of trusted certificates. TERM Normally, this variable is used by - Lynx to determine the terminal type - being used to invoke Lynx. If, however, + <strong>Lynx</strong> to determine the terminal type + being used to invoke <strong>Lynx</strong>. If, however, it is unset at startup time (or has the value "unknown"), or if the -term command-line option is used, - Lynx will set or modify its value + <strong>Lynx</strong> will set or modify its value to the user specified terminal type - (for the Lynx execution environment). - Note: If set/modified by Lynx, the values of + (for the <strong>Lynx</strong> execution environment). + Note: If set/modified by <strong>Lynx</strong>, the values of the LINES and/or COLUMNS environment variables may also be changed. +</pre> + <h2><a name="cgi" id="cgi">SIMULATED CGI SUPPORT</a></h2> -<a name="cgi" id="cgi"><em> -SIMULATED CGI SUPPORT -</em></a> - If built with the cgi-links option enabled, Lynx allows - access to a cgi script directly without the need for an - http daemon. - - When executing such "lynxcgi scripts" (if enabled), the - following variables may be set for simulating a CGI environment: + <p>If built with the cgi-links option enabled, + <strong>Lynx</strong> allows access to a cgi script directly + without the need for an http daemon.</p> + <p>When executing such "lynxcgi scripts" (if enabled), the + following variables may be set for simulating a CGI + environment:</p> + <pre> CONTENT_LENGTH CONTENT_TYPE @@ -272,30 +273,31 @@ SIMULATED CGI SUPPORT REQUEST_METHOD SERVER_SOFTWARE +</pre> - Other environment variables are not inherited by the - script, unless they are provided via a LYNXCGI_ENVIRONMENT - statement in the configuration file. See the lynx.cfg - file, and the (draft) CGI 1.1 Specification - <http://Web.Golux.Com/coar/cgi/draft-coar-cgi-v11-00.txt> - for the definition and usage of these variables. - - The CGI Specification, and other associated documentation, - should be consulted for general information on CGI script - programming. - -<a name="language" id="language"><em> -NATIVE LANGUAGE SUPPORT -</em></a> - If configured and installed with Native Language Support, - Lynx will display status and other messages in your local - language. See the file ABOUT_NLS in the source distribution, - or at your local GNU site, for more information about - internationalization. - - The following environment variables may be used to alter - default settings: + <p>Other environment variables are not inherited by the script, + unless they are provided via a LYNXCGI_ENVIRONMENT statement in + the configuration file. See the lynx.cfg file, and the (draft) + CGI 1.1 Specification + <http://Web.Golux.Com/coar/cgi/draft-coar-cgi-v11-00.txt> + for the definition and usage of these variables.</p> + <p>The CGI Specification, and other associated documentation, + should be consulted for general information on CGI script + programming.</p> + + <h2><a name="language" id="language">NATIVE LANGUAGE + SUPPORT</a></h2> + + <p>If configured and installed with Native Language Support, + <strong>Lynx</strong> will display status and other messages in + your local language. See the file ABOUT_NLS in the source + distribution, or at your local GNU site, for more information + about internationalization.</p> + + <p>The following environment variables may be used to alter + default settings:</p> + <pre> LANG This variable, if set, will override the default message language. It is an ISO 639 two-letter code identifying @@ -322,159 +324,213 @@ NATIVE LANGUAGE SUPPORT NLSPATH This variable, if set, is used as the path prefix for message catalogs. +</pre> + + <h2><a name="proxy" id="proxy">Proxy details and + examples</a></h2> + + <p>To set your site's NTTP server as the default host for news + reading and posting via <strong>Lynx</strong>, set the + environment variable NNTPSERVER so that it points to its Internet + address. The variable "NNTPSERVER" is used to specify the host + which will be used as the default for news URLs.</p> + + <dl> + <dt>UNIX</dt> + + <dd> + <pre> +setenv NNTPSERVER "news.server.dom" +</pre> + </dd> -<a name="proxy" id="proxy"><em> -Proxy details and examples: -</em></a> - - To set your site's NTTP server as the default host for news reading - and posting via Lynx, set the environment variable NNTPSERVER so that - it points to its Internet address. The variable "NNTPSERVER" is used - to specify the host which will be used as the default for news URLs. - - UNIX - setenv NNTPSERVER "news.server.dom" - - VMS - define/system NNTPSERVER "news.server.dom" - - Lynx still supports use of gateway servers, with the servers specified - via the variables "WWW_access_GATEWAY", where "access" is lower case - and can be "http", "ftp", "gopher" or "wais". Most of the gateway - servers have been discontinued, but "http://www.w3.org:8001" is - available for wais searches (note that you do not include a - terminal '/' for gateways, but do for proxies; see below). - - Lynx version 2.2 and beyond supports the use of proxy servers that - can act as firewall gateways and caching servers. They are - preferable to the older gateway servers. Each protocol used by - Lynx can be mapped separately using PROTOCOL_proxy environment - variables of the form: - - UNIX - setenv http_proxy "http://some.server.dom:port/" - setenv https_proxy "http://some.server.dom:port/" - setenv ftp_proxy "http://some.server.dom:port/" - setenv gopher_proxy "http://some.server.dom:port/" - setenv news_proxy "http://some.server.dom:port/" - setenv newspost_proxy "http://some.server.dom:port/" - setenv newsreply_proxy "http://some.server.dom:port/" - setenv snews_proxy "http://some.server.dom:port/" - setenv snewspost_proxy "http://some.server.dom:port/" - setenv snewsreply_proxy "http://some.server.dom:port/" - setenv nntp_proxy "http://some.server.dom:port/" - setenv wais_proxy "http://some.server.dom:port/" - setenv finger_proxy "http://some.server.dom:port/" - setenv cso_proxy "http://some.server.dom:port/" - - VMS - define "http_proxy" "http://some.server.dom:port/" - define "https_proxy" "http://some.server.dom:port/" - define "ftp_proxy" "http://some.server.dom:port/" - define "gopher_proxy" "http://some.server.dom:port/" - define "news_proxy" "http://some.server.dom:port/" - define "newspost_proxy" "http://some.server.dom:port/" - define "newsreply_proxy" "http://some.server.dom:port/" - define "snews_proxy" "http://some.server.dom:port/" - define "snewspost_proxy" "http://some.server.dom:port/" - define "snewsreply_proxy" "http://some.server.dom:port/" - define "nntp_proxy" "http://some.server.dom:port/" - define "wais_proxy" "http://some.server.dom:port/" - define "finger_proxy" "http://some.server.dom:port/" - define "cso_proxy" "http://some.server.dom:port/" - (Encase *BOTH* strings in double-quotes to maintain - lower case for the PROTOCOL_proxy variable and for - the http access type; include /system if you want - proxying for all clients on your system.) - - If you wish to override the use of a proxy server for specific hosts or - entire domains you may use the "no_proxy" environment variable. - The no_proxy variable can be a comma-separated list of strings defining - no-proxy zones in the DNS domain name space. If a tail substring of the - domain-path for a host matches one of these strings, transactions with that - node will not be proxied. Here is an example use of "no_proxy": - - UNIX - setenv no_proxy "host.domain.dom, domain1.dom, domain2" - - VMS - define "no_proxy" "host.domain.dom, domain1.dom, domain2" - - You can include a port number in the no_proxy list to override use - of a proxy server for the host accessed via that port, but not via - other ports. For example, if you use "host.domain.dom:119" and/or - "host.domain.dom:210", then news (port 119) URLs and/or any wais - (port 210) searches on that host would be excluded, but http, ftp, - and gopher services (if normally proxied) would still be included, - as would any news or wais services on other hosts. - - Warning: Note that setting 'il' as an entry in this list - will block proxying for the .mil domain as well as the .il domain. - If the entry is '.il' this will not happen. - - If you wish to override the use of a proxy server completely (i.e., - globally override any existing proxy variables), set the value of - "no_proxy" to "*". This is the only allowed use of * in no_proxy. - - Note that Lynx treats file URLs on the local host as requests for - direct access to the file, and does not attempt ftp if that fails. - It treats both ftp URLs and file URLs on remote hosts as ftp URLs, - and does not attempt direct file access for either. If ftp URLs are - being proxied, file URLs on a remote host will be converted to ftp - URLs before submission by Lynx to the proxy server, so no special - procedure for inducing the proxy server to handle them is required. - Other WWW clients may require that the http server's configuration - file have "Map file:* ftp:*" in it to perform that conversion. - - If you have not set NNTPSERVER, proxy or no_proxy environment variables - you can set them at run time via the configuration file lynx.cfg - (this will not override external settings). - -<a name="dos" id="dos"><em> -Win32 (95/NT) and 386 DOS -</em></a> - (adapted from "readme.txt" by Wayne Buttles - and "readme.dos" by Doug Kaufman) - - Here are some environment variables that should be set, usually in a - batch file that runs the lynx executable. Make sure that you have enough - room left in your environment. You may need to change your "SHELL=" - setting in config.sys. In addition, lynx looks for a "SHELL" environment - variable when shelling to DOS. If you wish to preserve the environment - space when shelling, put a line like this in your AUTOEXEC.BAT file also - "SET SHELL=C:\COMMAND.COM /E:2048". It should match CONFIG.SYS. + <dt>VMS</dt> + <dd> + <pre> +define/system NNTPSERVER "news.server.dom" +</pre> + </dd> + </dl> + + <p><strong>Lynx</strong> still supports use of gateway servers, + with the servers specified via the variables + "WWW_access_GATEWAY", where "access" is lower case and can be + "http", "ftp", "gopher" or "wais". Most of the gateway servers + have been discontinued, but "http://www.w3.org:8001" is available + for wais searches (note that you do not include a terminal '/' + for gateways, but do for proxies; see below).</p> + + <p><strong>Lynx</strong> version 2.2 and beyond supports the use + of proxy servers that can act as firewall gateways and caching + servers. They are preferable to the older gateway servers. Each + protocol used by <strong>Lynx</strong> can be mapped separately + using PROTOCOL_proxy environment variables of the form:</p> + + <dl> + <dt>UNIX</dt> + + <dd> + <blockquote> + <pre> +setenv http_proxy "http://some.server.dom:port/" +setenv https_proxy "http://some.server.dom:port/" +setenv ftp_proxy "http://some.server.dom:port/" +setenv gopher_proxy "http://some.server.dom:port/" +setenv news_proxy "http://some.server.dom:port/" +setenv newspost_proxy "http://some.server.dom:port/" +setenv newsreply_proxy "http://some.server.dom:port/" +setenv snews_proxy "http://some.server.dom:port/" +setenv snewspost_proxy "http://some.server.dom:port/" +setenv snewsreply_proxy "http://some.server.dom:port/" +setenv nntp_proxy "http://some.server.dom:port/" +setenv wais_proxy "http://some.server.dom:port/" +setenv finger_proxy "http://some.server.dom:port/" +setenv cso_proxy "http://some.server.dom:port/" +</pre> + </blockquote> + </dd> + + <dt>VMS</dt> + + <dd> + <blockquote> + <pre> +define "http_proxy" "http://some.server.dom:port/" +define "https_proxy" "http://some.server.dom:port/" +define "ftp_proxy" "http://some.server.dom:port/" +define "gopher_proxy" "http://some.server.dom:port/" +define "news_proxy" "http://some.server.dom:port/" +define "newspost_proxy" "http://some.server.dom:port/" +define "newsreply_proxy" "http://some.server.dom:port/" +define "snews_proxy" "http://some.server.dom:port/" +define "snewspost_proxy" "http://some.server.dom:port/" +define "snewsreply_proxy" "http://some.server.dom:port/" +define "nntp_proxy" "http://some.server.dom:port/" +define "wais_proxy" "http://some.server.dom:port/" +define "finger_proxy" "http://some.server.dom:port/" +define "cso_proxy" "http://some.server.dom:port/" +</pre> + </blockquote> + + <p>(Encase *BOTH* strings in double-quotes to maintain lower + case for the PROTOCOL_proxy variable and for the http access + type; include /system if you want proxying for all clients on + your system.)</p> + </dd> + </dl> + + <p>If you wish to override the use of a proxy server for specific + hosts or entire domains you may use the "no_proxy" environment + variable. The no_proxy variable can be a comma-separated list of + strings defining no-proxy zones in the DNS domain name space. If + a tail substring of the domain-path for a host matches one of + these strings, transactions with that node will not be proxied. + Here is an example use of "no_proxy":</p> + + <dl> + <dt>UNIX</dt> + + <dd> + <pre> +setenv no_proxy "host.domain.dom, domain1.dom, domain2" +</pre> + </dd> + + <dt>VMS</dt> + + <dd> + <pre> +define "no_proxy" "host.domain.dom, domain1.dom, domain2" +</pre> + </dd> + </dl> + + <p>You can include a port number in the no_proxy list to override + use of a proxy server for the host accessed via that port, but + not via other ports. For example, if you use + "host.domain.dom:119" and/or "host.domain.dom:210", then news + (port 119) URLs and/or any wais (port 210) searches on that host + would be excluded, but http, ftp, and gopher services (if + normally proxied) would still be included, as would any news or + wais services on other hosts.</p> + + <p>Warning: Note that setting 'il' as an entry in this list will + block proxying for the .mil domain as well as the .il domain. If + the entry is '.il' this will not happen.</p> + + <p>If you wish to override the use of a proxy server completely + (i.e., globally override any existing proxy variables), set the + value of "no_proxy" to "*". This is the only allowed use of * in + no_proxy.</p> + + <p>Note that <strong>Lynx</strong> treats file URLs on the local + host as requests for direct access to the file, and does not + attempt ftp if that fails. It treats both ftp URLs and file URLs + on remote hosts as ftp URLs, and does not attempt direct file + access for either. If ftp URLs are being proxied, file URLs on a + remote host will be converted to ftp URLs before submission by + <strong>Lynx</strong> to the proxy server, so no special + procedure for inducing the proxy server to handle them is + required. Other WWW clients may require that the http server's + configuration file have "Map file:* ftp:*" in it to perform that + conversion.</p> + + <p>If you have not set NNTPSERVER, proxy or no_proxy environment + variables you can set them at run time via the configuration file + lynx.cfg (this will not override external settings).</p> + + <h2><a name="dos" id="dos">Win32 (95/NT) and 386 DOS</a></h2> + + <p>(adapted from "readme.txt" by Wayne Buttles<br> + and "readme.dos" by Doug Kaufman)</p> + + <p>Here are some environment variables that should be set, + usually in a batch file that runs the <strong>Lynx</strong> + executable. Make sure that you have enough room left in your + environment. You may need to change your "SHELL=" setting in + config.sys. In addition, <strong>Lynx</strong> looks for a + "SHELL" environment variable when shelling to DOS. If you wish to + preserve the environment space when shelling, put a line like + this in your AUTOEXEC.BAT file also "SET SHELL=C:\COMMAND.COM + /E:2048". It should match CONFIG.SYS.</p> + <pre> HOME Where to keep the bookmark file and personal config files. TEMP or TMP Bookmarks are kept here with no HOME. Temp files here. USER Set to your login name LYNX_CFG Set to the full path and filename for lynx.cfg +</pre> - 386 version only: + <p>386 version only:<br></p> + <pre> WATTCP.CFG Set to the full path for the WATTCP.CFG directory - (Depending on how you compiled libtcp.a, you may have to use WATCONF.) +</pre> + + <p>(Depending on how you compiled libtcp.a, you may have to use + WATCONF.)</p> - Define these in your batch file for running Lynx. For example, if your - application line is "D:\win32\lynx.bat", lynx.bat for Win32 may look like: + <p>Define these in your batch file for running + <strong>Lynx</strong>. For example, if your application line is + "D:\win32\lynx.bat", lynx.bat for Win32 may look like:</p> + <pre> @ECHO OFF set home=d:\win32 set temp=d:\tmp set lynx_cfg=d:\win32\lynx.cfg d:\win32\lynx.exe %1 %2 %3 %4 %5 - - In lynx_386, a typical batch file might look like: - +</pre>In lynx_386, a typical batch file might look like: + <pre> @echo off set HOME=f:/lynx2-8 set USER=your_login_name set LYNX_CFG=%HOME%/lynx.cfg set WATTCP.CFG=%HOME% f:\lynx2-8\lynx %1 %2 %3 %4 %5 %6 %7 %8 %9 - - You will also need to make sure that the WATTCP.CFG file has the - correct information for IP number, Gateway, Netmask, and Domain Name - Server. This can also be automated in the batch file. - - </pre> + + <p>You will also need to make sure that the WATTCP.CFG file has + the correct information for IP number, Gateway, Netmask, and + Domain Name Server. This can also be automated in the batch + file.</p> </body> </html> diff --git a/lynx_help/keystrokes/follow_help.html b/lynx_help/keystrokes/follow_help.html index ff3b8a66..4f18fc29 100644 --- a/lynx_help/keystrokes/follow_help.html +++ b/lynx_help/keystrokes/follow_help.html @@ -1,4 +1,4 @@ -<!-- $LynxId: follow_help.html,v 1.11 2013/05/21 10:51:27 tom Exp $ --> +<!-- $LynxId: follow_help.html,v 1.13 2014/01/07 01:38:19 tom Exp $ --> <!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01//EN"> <html> @@ -10,178 +10,254 @@ <link rev="made" href="mailto:lynx-dev@nongnu.org"> <meta http-equiv="Content-Type" content= "text/html; charset=us-ascii"> -</head> + <meta name="description" content= + " Lynx allows the user to select a link using a single-digit shortcut. There are several configuration choices which apply to this feature."> + </head> <body> - <h1>Follow link (or goto link or page) number Help<br> - Select option (or page) number Help</h1> + <h2>Overview</h2> - <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 + <p>If a user has set one of these modes, (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>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>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>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><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> + prefixed with numbers in square brackets:</p> + + <ul> + <li><em>Keypad mode</em> to <em>Links are numbered</em>, + or</li> + + <li><em>Form fields are numbered</em>, or</li> + + <li><em>Links and form fields are numbered</em></li> + </ul> + + <p>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.</p> + + <h2>Zero and other digits</h2> + + <p>The prompt can be invoked via typing a zero (<em>0</em>), but + it will not be treated as the lead digit for the number entry, + whereas digits 1 through 9 both invoke the prompt and are treated + as the first digit.</p> + + <p>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>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>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> + arrows</em>, then only a zero digit 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.</p> + + <h2>Suffixes</h2> + + <p>After accepting a number at the prompt, <strong>Lynx</strong> + accepts an optional suffix:</p> + + <dl> + <dt><em>RETURN</em> (activate)</dt> + + <dd>Without a suffix, e.g., If <em>RETURN</em> is pressed to + terminate the number entry (e.g., <em>123</em>) and it + corresponds to a hypertext link, <strong>Lynx</strong> 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.</dd> + + <dt><code><strong>g</strong></code> (go)</dt> + + <dd> + <p>If the number entered at the prompt has a '<em>g</em>' + suffix (e.g., <em>123g</em>), then <strong>Lynx</strong> 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> + </dd> + + <dt><code><strong>p</strong></code> (page)</dt> + + <dd> + <p>Alternatively, if the number is given a '<em>p</em>' + suffix (e.g., <em>123p</em>), <strong>Lynx</strong> 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> + </dd> + + <dt><code><strong>+</strong></code> or + <code><strong>-</strong></code> (jump)</dt> + + <dd> + <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><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> + </dd> + </dl> + + <h2>Specifics for Form Fields</h2> + + <p>Numbers are associated with form fields only when</p> + + <ul> + <li><em>Form fields are numbered</em> or</li> + + <li><em>Links and form fields are numbered</em> mode has been + selected.</li> + </ul> + + <p>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 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>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> + list of OPTIONs in a form's SELECT block:</p> + + <ul> + <li>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.</li> + + <li>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.</li> + + <li>If only a number is entered at the prompt, the + corresponding OPTION will be selected and the popup will be + retracted.</li> + + <li>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.</li> + + <li>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.</li> + + <li>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.</li> + </ul> + + <p>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> + + <h2>Hidden Links</h2> + + <p>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</p> + + <ul> + <li>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.</li> + + <li>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.</li> + + <li>using the <em>-ismap</em> command line switch, which makes + <strong>Lynx</strong> additionally treat a link to a + server-side image maps as hidden if there also is a client-side + map for the same image.</li> + + <li>bad HTML, which may produce <em>hidden links</em>.</li> + </ul> + + <p><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><strong>Lynx</strong> 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> + + <h2>Navigating to Hidden Links</h2> <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> + ACTIVATE-ed via those menus.</p> + + <p>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 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. <strong>Lynx</strong> 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 f524dd1d..d71ca008 100644 --- a/lynx_help/keystrokes/gopher_types_help.html +++ b/lynx_help/keystrokes/gopher_types_help.html @@ -1,4 +1,4 @@ -<!-- $LynxId: gopher_types_help.html,v 1.8 2013/05/21 10:59:47 tom Exp $ --> +<!-- $LynxId: gopher_types_help.html,v 1.11 2014/01/09 00:17:28 tom Exp $ --> <!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01//EN"> <html> @@ -10,10 +10,12 @@ <link rev="made" href="mailto:lynx-dev@nongnu.org"> <meta http-equiv="Content-Type" content= "text/html; charset=us-ascii"> -</head> + <meta name="description" content= + "This is a list of the file-types which are known to Lynx in its gopher interface."> + </head> <body> - <h1>Gopher Types</h1> + <h1>Listing of Gopher types</h1> <dl> <dt>(FILE)</dt> diff --git a/lynx_help/keystrokes/history_help.html b/lynx_help/keystrokes/history_help.html index f3728502..dd396093 100644 --- a/lynx_help/keystrokes/history_help.html +++ b/lynx_help/keystrokes/history_help.html @@ -1,4 +1,4 @@ -<!-- $LynxId: history_help.html,v 1.6 2013/05/21 10:51:27 tom Exp $ --> +<!-- $LynxId: history_help.html,v 1.7 2014/01/07 09:17:47 tom Exp $ --> <!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01//EN"> <html> @@ -10,19 +10,24 @@ <link rev="made" href="mailto:lynx-dev@nongnu.org"> <meta http-equiv="Content-Type" content= "text/html; charset=us-ascii"> -</head> + <meta name="description" content= + "Lynx provides a history page, showing all of the links which have been traversed to reach the current point. The user can revisit any of these links."> + </head> <body> - <h1>History Page Help</h1> - - <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> + <h2>Overview</h2> + + <p><strong>Lynx</strong>'s 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> + + <h2>Navigation</h2> <p>You may <a href="movement_help.html">select</a> any link on the History Page to review a document that you have previously diff --git a/lynx_help/keystrokes/keystroke_help.html b/lynx_help/keystrokes/keystroke_help.html index 05c94246..17912452 100644 --- a/lynx_help/keystrokes/keystroke_help.html +++ b/lynx_help/keystrokes/keystroke_help.html @@ -1,4 +1,4 @@ -<!-- $LynxId: keystroke_help.html,v 1.18 2013/05/21 10:51:27 tom Exp $ --> +<!-- $LynxId: keystroke_help.html,v 1.19 2014/01/07 01:45:02 tom Exp $ --> <!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01//EN"> <html> @@ -10,20 +10,24 @@ <link rev="made" href="mailto:lynx-dev@nongnu.org"> <meta http-equiv="Content-Type" content= "text/html; charset=us-ascii"> -</head> + <meta name="description" content= + "Lynx recognizes many single-character commands. This is an overview to their default bindings, with links to more detailed documentation."> + </head> <body> - <h1>Keystroke Commands</h1> + <p><strong>Lynx</strong> recognizes many single-character + commands. This is an overview to their default bindings, with + links to more detailed documentation.</p> <pre> - <a href= -"movement_help.html">MOVEMENT</a>: Down arrow - Highlight next topic + <a name="movement" href="movement_help.html" id= +"movement">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 name="scrolling" href="scrolling_help.html" id= +"scrolling">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) @@ -41,8 +45,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 name="dired" href="dired_help.html" id= +"dired">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 @@ -51,8 +55,8 @@ 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 name="other" href="other_help.html" id= +"other">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 diff --git a/lynx_help/keystrokes/movement_help.html b/lynx_help/keystrokes/movement_help.html index 7e7f7247..18277ee0 100644 --- a/lynx_help/keystrokes/movement_help.html +++ b/lynx_help/keystrokes/movement_help.html @@ -1,4 +1,4 @@ -<!-- $LynxId: movement_help.html,v 1.7 2013/05/21 10:51:27 tom Exp $ --> +<!-- $LynxId: movement_help.html,v 1.9 2014/01/08 21:36:06 tom Exp $ --> <!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01//EN"> <html> @@ -10,10 +10,17 @@ <link rev="made" href="mailto:lynx-dev@nongnu.org"> <meta http-equiv="Content-Type" content= "text/html; charset=us-ascii"> -</head> + <meta name="description" content= + " These are the Lynx keystroke-movement commands which are usable in all non-editing contexts, for traversing links."> + </head> <body> - <h1>MOVEMENT HELP</h1> + <h2>Keystroke Commands</h2> + + <p>These are the Lynx <a href= + "keystroke_help.html#movement">keystroke-movement</a> commands + which are usable in all non-editing contexts, for traversing + links.</p> <pre> Down arrow, - Move to the next hypertext link, TAB or scroll down if there are no more @@ -29,20 +36,28 @@ Left arrow - Retreat from a link. Go back to the previous topic. +</pre> + <h2>Notes</h2> - *note: If 'VI Keys' are enabled from the options menu or - from the '.lynxrc' file, lowercase h,j,k,l will - move left, down, up, and right, respectively. + <ol> + <li>If <em>VI Keys</em> are enabled from the options menu or + from the <code>.lynxrc</code> file, lowercase h,j,k,l will move + left, down, up, and right, respectively.</li> - *note: If 'Emacs Keys' are enabled from the options menu or - from the '.lynxrc' file, Ctrl-B, Ctrl-N, Ctrl-P, - Ctrl-F will move left, down, up, and right, respectively. + <li>If <em>Emacs Keys</em> are enabled from the options menu or + from the <code>.lynxrc</code> file, Ctrl-B, Ctrl-N, Ctrl-P, + Ctrl-F will move left, down, up, and right, respectively.</li> - *note: If the 'Num Lock' on your keyboard is on, Lynx will - translate the numbers of your keypad into movement - commands. The translation is as follows. + <li>If the <em>Num Lock</em> on your keyboard is on, + <strong>Lynx</strong> will translate the numbers of your keypad + into movement commands. The translation corresponds with the + labels on numeric keypad, but can be used from the main + keyboard. It is as follows.</li> + </ol> + <blockquote> + <pre> 9 - page up 8 - up arrow 7 8 9 7 - moves to the top of a document @@ -53,5 +68,6 @@ 2 - down arrow 1 - moves to the end of a document </pre> + </blockquote> </body> </html> diff --git a/lynx_help/keystrokes/option_help.html b/lynx_help/keystrokes/option_help.html index b9baf83d..b9148607 100644 --- a/lynx_help/keystrokes/option_help.html +++ b/lynx_help/keystrokes/option_help.html @@ -1,4 +1,4 @@ -<!-- $LynxId: option_help.html,v 1.25 2013/05/21 10:58:35 tom Exp $ --> +<!-- $LynxId: option_help.html,v 1.28 2014/01/08 22:28:11 tom Exp $ --> <!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01//EN"> <html> @@ -10,31 +10,46 @@ <link rev="made" href="mailto:lynx-dev@nongnu.org"> <meta http-equiv="Content-Type" content= "text/html; charset=us-ascii"> -</head> + <meta name="description" content= + "Lynx's options menu allows you to set and modify many features. Some features persist only during the current session unless specially enabled in lynx.cfg"> + </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> + <p>The <em>Options Menu</em> allows you to set and modify many + Lynx features.<br> + <strong>Lynx</strong>'s <em>Options Menu</em> is grouped visually + (by skipping a line) into sections. This description follows the + same arrangement. Some options appear on the screen only if they + have been compiled in or chosen in + <code><strong>lynx.cfg</strong></code>.</p> <ul> - <li>General Preferences + <li> + <a href="#GP">General Preferences</a> <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="#ST">Type of Search</a></li> + </ul> + </li> + + <li> + <a href="#SP">Security and Privacy</a> + <ul> <li><a href="#CK">Cookies</a></li> + + <li><a href="#IK">Invalid-Cookie Prompting</a></li> + + <li><a href="#SK">SSL Prompting</a></li> </ul> </li> - <li>Keyboard Input + <li> + <a href="#KI">Keyboard Input</a> <ul> <li><a href="#KM">Keypad mode</a></li> @@ -47,9 +62,14 @@ </ul> </li> - <li>Display and Character Set + <li> + <a href="#DP">Display and Character Set</a> <ul> + <li><a href="#LC">Use locale-based character set</a></li> + + <li><a href="#H5">Use HTML5 charset replacements</a></li> + <li><a href="#DC">Display Character set</a></li> <li><a href="#AD">Assumed document character set</a></li> @@ -60,47 +80,78 @@ </ul> </li> - <li>Document Appearance + <li> + <a href="#AP">Document Appearance</a> <ul> <li><a href="#SC">Show color</a></li> + <li><a href="#CS">Color style</a></li> + + <li><a href="#C0">Default colors</a></li> + <li><a href="#CL">Show cursor for current link or option</a></li> + <li><a href="#UK">Underline links</a></li> + + <li><a href="#SS">Show scrollbar</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="#BH">Bad HTML messages</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 + <li> + <a href="#HP">Headers Transferred to Remote Servers</a> <ul> - <li><a href="#PM">Personal Mail Address</a></li> + <li><a href="#PM">Personal mail address</a></li> + + <li><a href="#PN">Personal name for mail</a></li> + + <li><a href="#PW">Password for anonymous ftp</a></li> + + <li><a href="#PT">Preferred media type</a></li> + + <li><a href="#PE">Preferred encoding</a></li> <li><a href="#PC">Preferred Document Charset</a></li> <li><a href="#PL">Preferred Document Language</a></li> + <li><a href="#SA">Send User-Agent header</a></li> + <li><a href="#UA">User Agent</a></li> </ul> </li> - <li>Listing and Accessing Files + <li> + <a href="#LP">Listing and Accessing Files</a> <ul> + <li><a href="#PF">Use Passive FTP</a></li> + <li><a href="#FT">FTP sort criteria</a></li> <li><a href="#LD">Local directory sort criteria</a></li> + <li><a href="#LO">Local directory sort order</a></li> + <li><a href="#DF">Show dot files</a></li> + <li><a href="#PZ">Pause when showing message</a></li> + <li><a href="#LL">Execution links</a></li> + + <li><a href="#TX">Show transfer rate</a></li> </ul> </li> @@ -111,18 +162,31 @@ <li><a href="#BF">Bookmark file</a></li> + <li><a href="#AZ">Auto Session</a></li> + + <li><a href="#SZ">Session file</a></li> + <li><a href="#VP">Visited Pages</a></li> </ul> </li> </ul> - <h1><a name="CK" id="CK">Cookies</a></h1> + <h2><a name="GP" id="GP">General Preferences</a></h2> - <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> + <h3><a name="UM" id="UM">User Mode</a></h3> + + <dl> + <dt><em>Novice</em>: Shows 2 extra lines of help at the bottom + of the screen for beginners.</dt> - <h1><a name="ED" id="ED">Editor</a></h1> + <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> + + <h3><a name="ED" id="ED">Editor</a></h3> <p>This is the editor to be invoked when editing browsable files, sending mail or comments, or filling form's textarea (multiline @@ -131,7 +195,59 @@ the same character set you have for "display character set" in Lynx.</p> - <h1><a name="EM" id="EM">Emacs keys</a></h1> + <h3><a name="ST" id="ST">Type of Search</a></h3> + + <p>This allows you to tell Lynx whether to search the current + document ignoring case (case insensistive) or not.</p> + + <h2><a name="SP" id="SP">Security and Privacy</a></h2> + + <h3><a name="CK" id="CK">Cookies</a></h3> + + <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> + + <h3><a name="IK" id="IK">Invalid-Cookie Prompting</a></h3> + + <p>This allows you to tell how to handle invalid cookies:</p> + + <ul> + <li><em>prompt normally</em> to prompt for each cookie</li> + + <li><em>force yes-response</em> to reply "yes" to each + prompt</li> + + <li><em>force no-response</em> to reply "no" to each + prompt.</li> + </ul> + + <h3><a name="SK" id="SK">SSL Prompting</a></h3> + + <p>This allows you to tell how to handle errors detected in SSL + connections:</p> + + <ul> + <li><em>prompt normally</em> to prompt for each cookie</li> + + <li><em>force yes-response</em> to reply "yes" to each + prompt</li> + + <li><em>force no-response</em> to reply "no" to each + prompt.</li> + </ul> + + <h2><a name="KI" id="KI">Keyboard Input</a></h2> + + <h3><a name="KM" id="KM">Keypad mode</a></h3> + + <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> + + <h3><a name="EM" id="EM">Emacs keys</a></h3> <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 @@ -142,53 +258,93 @@ <p>Note: setting emacs keys does not affect the line-editor bindings.</p> - <h1><a name="LL" id="LL">Execution links</a></h1> + <h3><a name="VI" id="VI">VI keys</a></h3> - <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> + <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> - <h1><a name="KM" id="KM">Keypad mode</a></h1> + <p>The uppercase H, J, K, and L keys remain mapped to their + configured bindings (normally HELP, JUMP, KEYMAP and LIST, + respectively).</p> - <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> + <p>Note: setting vi keys does not affect the line-editor + bindings.</p> - <h1><a name="LE" id="LE">Line edit style</a></h1> + <h3><a name="LE" id="LE">Line edit style</a></h3> <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" id="PM">Personal Mail Address</a></h1> + <h2><a name="DP" id="DP">Display and Character Set</a></h2> - <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> + <h3><a name="LC" id="LC">Use locale-based character set</a></h3> - <h1><a name="PU" id="PU">Pop-ups for select fields</a></h1> + <p>This option allows you to request lynx to obtain a MIME name + from the operating system which corresponds to your locale + setting. If successful, it overrides the normal setting of the + display character set.</p> - <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> + <h3><a name="H5" id="H5">Use HTML5 charset replacements</a></h3> + + <p>This option allows lynx to treat pages with ISO-8859-1 + (Latin1) or ASCII encoding as if they were Windows 1252. That + allows a few punctuation characters to be shown.</p> + + <h3><a name="DC" id="DC">Display Character set</a></h3> - <h1><a name="ST" id="ST">Searching type</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>.</p> + + <h3><a name="AD" id="AD">Assumed document character set</a></h3> + + <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> + + <h3><a name="JK" id="JK">Raw 8-bit or CJK mode</a></h3> + + <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> - <p>If set to 'case sensitive', user searches invoked by '/' will - be case-sensitive substring searches. Default is 'Case - Insensitive'.</p> + <h3><a name="DV" id="DV">X DISPLAY variable</a></h3> - <h1><a name="SC" id="SC">Show color</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> + + <h2><a name="AP" id="AP">Document Appearance</a></h2> + + <h3><a name="SC" id="SC">Show color</a></h3> <p>This will be present if color support is available.</p> @@ -229,8 +385,23 @@ color mode is incorrect for your terminal, set it appropriately on or off via this option.</p> - <h1><a name="CL" id="CL">Show cursor for current link or - option</a></h1> + <h3><a name="CS" id="CS">Color style</a></h3> + + <p>At startup, Lynx identifies the available color-style + configuration files in the same directory as its default ".lss" + file. At runtime, you can switch between these files using this + options-menu feature.</p> + + <h3><a name="C0" id="C0">Default colors</a></h3> + + <p>Depending on the default foreground and background colors + which your terminal uses, some color-styles would look better if + Lynx did not use those in combination with the style for the + background. Use this option to enable/disable the default-color + feature.</p> + + <h3><a name="CL" id="CL">Show cursor for current link or + option</a></h3> <p>Lynx normally hides the cursor by positioning it to the right and if possible the very bottom of the screen, so that the @@ -242,52 +413,28 @@ character attributes used to distinguish the current link or OPTION from the others in the display.</p> - <h1><a name="UM" id="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> + <h3><a name="UK" id="UK">Underline links</a></h3> - <dt><em>Advanced</em>: The URL is shown on the status - line.</dt> - </dl> + <p>Use underline-attribute rather than bold for links.</p> - <h1><a name="AD" id="AD">Assumed document character set</a></h1> + <h3><a name="SS" id="SS">Show scrollbar</a></h3> - <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> + <p>This allows you to enable (show) or disable (hide) the + scrollbar on the right-margin of the display. This feature is + available with ncurses or slang libraries.</p> - <h1><a name="JK" id="JK">Raw 8-bit or CJK mode</a></h1> + <h3><a name="PU" id="PU">Pop-ups for select fields</a></h3> - <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> + <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="tagsoup" id="tagsoup">HTML error recovery</a></h1> + <h3><a name="tagsoup" id="tagsoup">HTML error recovery</a></h3> <p>Lynx often has to deal with invalid HTML markup. It always tries to recover from errors, but there is no universally correct @@ -316,24 +463,33 @@ find that the information from the -trace switch is just too much, Lynx can be started with the -preparsed switch; going into SOURCE mode ('\' key) and toggling the parsing mode (with CTRL-V) - should then show some of the differences. <!-- -LP's version - for reference - TD - -While the proper HTML markup should be canonical, badly nested HTML pages -may be recovered in different ways. There are two error recovery modes -in Lynx: SortaSGML with the recovery at SGML stage and TagSoup mode -with the recovery at HTML parsing stage, the latter gives more -recovery and was the default in Lynx 2.7.2 and before, -and the first may be useful for page validation purposes. -One particular difference is known for <li>..</li> -or similar strong markup inside <a HREF="some.url">..</a> -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" id="SI">Show Images</a></h1> + should then show some of the differences.</p> + + <h3><a name="BH" id="BH">Bad HTML messages</a></h3> + + <p>Suppress or redirect Lynx's messages about "Bad HTML":</p> + + <dl> + <dt>Ignore</dt> + + <dd>do not warn; no details are written to the trace-file.</dd> + + <dt>Add to trace-file</dt> + + <dd>add the detailed warning message to the trace-file.</dd> + + <dt>Add to LYNXMESSAGES</dt> + + <dd>add the detailed warning message to the message page at + "LYNXMESSAGES:".</dd> + + <dt>Warn, point to trace-file</dt> + + <dd>show a warning message on the status line; the complete + message is written to the trace-file.</dd> + </dl> + + <h3><a name="SI" id="SI">Show Images</a></h3> <p>This option combines the effects of the `*' & `[' keys as follows:</p> @@ -347,7 +503,7 @@ from lynx.cfg or command line switch. <a href="../Lynx_users_guide.html#Images">Users Guide</a> & <em>lynx.cfg</em> for more details.</p> - <h1><a name="VB" id="VB">Verbose Images</a></h1> + <h3><a name="VB" id="VB">Verbose Images</a></h3> <p>This allows you to replace [LINK], [INLINE] and [IMAGE] — for images without ALT — with filenames: this can @@ -357,41 +513,225 @@ from lynx.cfg or command line switch. "../Lynx_users_guide.html#Images">Users Guide</a> & <em>lynx.cfg</em> for more details.</p> - <h1><a name="VI" id="VI">VI keys</a></h1> + <h2><a name="HP" id="HP">Headers Transferred to Remote + Servers</a></h2> - <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> + <h3><a name="PM" id="PM">Personal Mail Address</a></h3> - <p>The uppercase H, J, K, and L keys remain mapped to their - configured bindings (normally HELP, JUMP, KEYMAP and LIST, - respectively).</p> + <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> - <p>Note: setting vi keys does not affect the line-editor - bindings.</p> + <h3><a name="PN" id="PN">Personal mail name</a></h3> - <h1><a name="DC" id="DC">Display Character set</a></h1> + <p>This mail name will be included as the "X-Personal_Name" field + in any mail or comments that you send if that header has not been + disabled via the NO_ANONYMOUS_EMAIL definition in + <em>lynx.cfg</em>.</p> - <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> + <h3><a name="PW" id="PW">Password for anonymous ftp</a></h3> - <h1><a name="DV" id="DV">X DISPLAY variable</a></h1> + <p>If this is blank, Lynx will use your personal mail address as + the anonymous ftp password. Though that is the convention, some + users prefer to use some other string which provides less + information. If the given value lacks a "@", Lynx also will use + your computer's hostname as part of the password. If both this + field and the personal mail address are blank, Lynx will use your + $USER environment variable, or "WWWuser" if even the environment + variable is unset.</p> - <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> + <h3><a name="PT" id="PT">Preferred media type</a></h3> + + <p>When doing a GET, lynx lists the MIME types which it knows how + to present (the "Accept:" string). Depending on your system + configuration, the mime.types or other data given by the + GLOBAL_EXTENSION_MAP may include many entries that lynx really + does not handle. Use this option to select one of the built-in + subsets of the MIME types that lynx could list in the Accept.</p> + + <dl> + <dt>Accept lynx's internal types</dt> + + <dd>list only the types that are compiled into lynx.</dd> + + <dt>Also accept lynx.cfg's types</dt> + + <dd>lists types defined in lynx.cfg, e.g., the VIEWER and Cern + RULE or RULESFILE settings.</dd> + + <dt>Also accept user's types</dt> + + <dd>lists types from the PERSONAL_EXTENSION_MAP setting in + lynx.cfg</dd> + + <dt>Also accept system's types</dt> + + <dd>lists types from the GLOBAL_EXTENSION_MAP setting in + lynx.cfg</dd> + + <dt>Accept all types</dt> + + <dd>adds the types that are in lynx's built-in tables for + external programs that may be used to present a document.</dd> + </dl> + + <h3><a name="PE" id="PE">Preferred encoding</a></h3> + + <p>When doing a GET, lynx tells what types of compressed data it + can decompress (the "Accept-Encoding:" string). This is + determined by compiled-in support for decompression or external + decompression programs. Use this option to select none, one or + all of the supported decompression types.</p> + + <h3><a name="PC" id="PC">Preferred Document Charset</a></h3> + + <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> + + <h3><a name="PL" id="PL">Preferred Document Language</a></h3> + + <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> + + <h3><a name="SA" id="SA">Send User-Agent header</a></h3> + + <p>This controls whether the user-agent string will be sent.</p> + + <h3><a name="UA" id="UA">User Agent header</a></h3> + + <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>Caveat: Netscape Communications Corp. (for example) claimed + that false transmissions of `Mozilla' as the User-Agent are a + copyright infringement, which would be prosecuted. The + <em>Options Menu</em> issues a warning about possible copyright + infringement whenever the header is changed to one which does not + include <strong>Lynx</strong> or <strong>lynx</strong>.</p> + + <h2><a name="LP" id="LP">Listing and Accessing Files</a></h2> - <h1><a name="MB" id="MB">Multi-bookmarks</a></h1> + <h3><a name="PF" id="PF">Use Passive FTP</a></h3> + + <p>This allows you to change whether Lynx uses passive ftp + connections.</p> + + <h3><a name="FT" id="FT">FTP sort criteria</a></h3> + + <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> + + <h3><a name="LD" id="LD">List directory style</a></h3> + + <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> + + <h3><a name="LO" id="LO">Local directory sort order</a></h3> + + <p>Lynx also allows you to sort by the file attributes:</p> + + <dl> + <dt>By name</dt> + + <dd>by filename (the default)</dd> + + <dt>By size</dt> + + <dd>by file size, in descending order</dd> + + <dt>By date</dt> + + <dd>by file modification time, in descending order</dd> + + <dt>By mode</dt> + + <dd>by file protection</dd> + + <dt>By type</dt> + + <dd>by filename suffix, e.g., the text beginning with '.'</dd> + + <dt>By user</dt> + + <dd>by file owner's user-id</dd> + + <dt>By group</dt> + + <dd>by file owner's group-id</dd> + </dl> + + <h3><a name="DF" id="DF">Show dot files</a></h3> + + <p>If display/creation of hidden (dot) files/directories is + enabled, you can turn the feature on or off via this setting.</p> + + <h3><a name="PZ" id="PZ">Pause when showing message</a></h3> + + <p>If set to "off", this overrides the INFOSECS setting in + lynx.cfg, to eliminate pauses when displaying informational + messages, like the "-nopause" command line option.</p> + + <h3><a name="LL" id="LL">Execution links</a></h3> + + <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> + + <h3><a name="TX" id="TX">Show transfer rate</a></h3> + + <p>This allows you to select the way in which Lynx shows its + progress in downloading large pages. It displays its progress in + the status line. These are the available selections:</p> + + <ul> + <li>Do not show rate</li> + + <li>Local directory sort order</li> + + <li>Show dot files</li> + + <li>Execution links</li> + + <li>Pause when showing message</li> + + <li>Show transfer rate</li> + </ul> + + <h3><a name="MB" id="MB">Multi-bookmarks</a></h3> <p>Manage multiple bookmark files:</p> @@ -410,7 +750,7 @@ from lynx.cfg or command line switch. file.</li> </ul> - <h1><a name="BF" id="BF">Bookmark file</a></h1> + <h3><a name="BF" id="BF">Bookmark file</a></h3> <p>Manage the default bookmark file:</p> @@ -430,7 +770,18 @@ from lynx.cfg or command line switch. <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" id="VP">Visited Pages</a></h1> + <h3><a name="AZ" id="AZ">Auto Session</a></h3> + + <p>Lynx can save and restore useful information about your + browsing history. Use this setting to enable or disable the + feature.</p> + + <h3><a name="SZ" id="SZ">Session file</a></h3> + + <p>Define the file name where lynx will store user sessions. This + setting is used only when <em>Auto Session</em> is enabled.</p> + + <h3><a name="VP" id="VP">Visited Pages</a></h3> <p>This allows you to change the appearance of the <a href= "visited_help.html">Visited Links Page</a> Normally it shows a @@ -465,74 +816,5 @@ from lynx.cfg or command line switch. is shown in order, to make the current page (usually) at the bottom of the list.</dt> </dl> - - <h1><a name="FT" id="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" id="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" id="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" id="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" id="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" id="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 c43be74d..791718a5 100644 --- a/lynx_help/keystrokes/other_help.html +++ b/lynx_help/keystrokes/other_help.html @@ -1,4 +1,4 @@ -<!-- $LynxId: other_help.html,v 1.13 2013/05/21 10:51:27 tom Exp $ --> +<!-- $LynxId: other_help.html,v 1.14 2014/01/08 00:12:12 tom Exp $ --> <!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01//EN"> <html> @@ -6,14 +6,16 @@ <meta name="generator" content= "HTML Tidy for Linux (vers 25 March 2009), see www.w3.org"> - <title>Help on Misc. Lynx Commands</title> + <title>Help on Miscellaneous Lynx Commands</title> <link rev="made" href="mailto:lynx-dev@nongnu.org"> <meta http-equiv="Content-Type" content= "text/html; charset=us-ascii"> -</head> + <meta name="description" content= + "This is a table listing with brief descriptions miscellaneous Lynx commands, along with links to related topics"> + </head> <body> - <h1>Other Commands</h1> + <h2>Summary of Commands</h2> <pre> a - Places the link that you are currently positioned on into a personal <a href= @@ -44,7 +46,7 @@ as a <em>goto</em> URL. ? or H - Hypertext help to explain how to navigate in - Lynx and use its features. + <strong>Lynx</strong> and use its features. i - Shows an index of files or subjects, which may be changed in <em>lynx.cfg</em>. @@ -69,7 +71,7 @@ o - Brings up a list of settable <a href= "option_help.html">options</a>. - q - Quits Lynx. ('Q' quits without asking) + q - Quits <strong>Lynx</strong>. ('Q' quits without asking) / - Search for a string of characters in the current document (case insensitive or case sensitive @@ -111,7 +113,7 @@ comments within the angle-brackets. _ - Clears all authorization info for the current session. Can - be used when leaving one's terminal without ending the Lynx + be used when leaving one's terminal without ending the <strong>Lynx</strong> session, to guard against someone else retrieving protected documents with previously entered username/password info. Note that any protected documents that are still in cache @@ -130,13 +132,13 @@ for documents which does not specify character set explicitly. Should be on when the document's charset matches the display character set, and otherwise off so that 8-bit - characters will be translated by Lynx with respect to the + characters will be translated by <strong>Lynx</strong> with respect to the Assumed document charset, using approximations if necessary (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 - "[INLINE]" pseudo-ALT string inserted in the Lynx display. + "[INLINE]" pseudo-ALT string inserted in the <strong>Lynx</strong> display. When off, they will be treated as having ALT="" (i.e., they'll be ignored). If image_links mode is toggled on, the pseudo-ALT strings will be restored, to serve as links @@ -146,7 +148,7 @@ applies only to documents or links (or form submit buttons) of http servers. A statusline message will notify you if the context for this command was inappropriate. The HEAD - requests always are sent to the http server, i.e., Lynx + requests always are sent to the http server, i.e., <strong>Lynx</strong> does not retrieve any previous server replies from its cache. Note that for form submissions, http servers vary in whether they'll treat HEAD requests as valid and return @@ -173,11 +175,11 @@ CTRL-T - Toggles trace mode on and off. - ; - Views the Lynx Trace Log for the current session. + ; - Views the <em>Lynx Trace Log</em> for the current session. CTRL-K - Invokes the Cookie Jar Page. - numbers - Lynx offers other, advanced navigation features when + numbers - <strong>Lynx</strong> 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 diff --git a/lynx_help/keystrokes/print_help.html b/lynx_help/keystrokes/print_help.html index 2e1b7c05..2bd58a0e 100644 --- a/lynx_help/keystrokes/print_help.html +++ b/lynx_help/keystrokes/print_help.html @@ -1,4 +1,4 @@ -<!-- $LynxId: print_help.html,v 1.7 2013/05/21 10:51:27 tom Exp $ --> +<!-- $LynxId: print_help.html,v 1.8 2014/01/07 23:47:13 tom Exp $ --> <!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01//EN"> <html> @@ -6,20 +6,26 @@ <meta name="generator" content= "HTML Tidy for Linux (vers 25 March 2009), see www.w3.org"> - <title>Lynx Print Help</title> + <title>Lynx Print Help and Configuration Summary</title> <link rev="made" href="mailto:lynx-dev@nongnu.org"> <meta http-equiv="Content-Type" content= "text/html; charset=us-ascii"> -</head> + <meta name="description" content= + "Describe Lynx's print command, showing the different ways that a document's content can be saved as plain text, e.g., mail, local-file, user-defined."> + </head> <body> - <h1>Printing Help</h1> + <h2>Overview</h2> - <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> + <p>After entering the <code><strong>p</strong></code> 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.</p> + + <h2>Print-command Options</h2> + + <p>The following print options may be available:</p> <dl> <dt>Print to a local file:</dt> @@ -27,7 +33,8 @@ <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> + to the directory that you were in when you began + <strong>Lynx</strong>.</dd> <dt>Print to the screen:</dt> diff --git a/lynx_help/keystrokes/scrolling_help.html b/lynx_help/keystrokes/scrolling_help.html index ffa121fb..cedfac86 100644 --- a/lynx_help/keystrokes/scrolling_help.html +++ b/lynx_help/keystrokes/scrolling_help.html @@ -1,4 +1,4 @@ -<!-- $LynxId: scrolling_help.html,v 1.9 2013/05/21 10:51:27 tom Exp $ --> +<!-- $LynxId: scrolling_help.html,v 1.10 2014/01/08 00:25:16 tom Exp $ --> <!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01//EN"> <html> @@ -6,25 +6,38 @@ <meta name="generator" content= "HTML Tidy for Linux (vers 25 March 2009), see www.w3.org"> - <title>Lynx Scrolling Help</title> + <title>Lynx Scrolling/Paging Help Summary</title> <link rev="made" href="mailto:lynx-dev@nongnu.org"> <meta http-equiv="Content-Type" content= "text/html; charset=us-ascii"> -</head> + <meta name="description" content= + "This gives an overview and some details on Lynx's scrolling/paging commands. A diagram shows keypad shortcuts."> + </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). + <h2>Paging shortcuts</h2> - - (or b, - If you have moved down in a document, this - or CTRL-B) will bring you back up one page (Page-Up). + <blockquote> + <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). - If the 'Num Lock' on your keyboard is on, Lynx translates - the numbers of your keypad into movement commands as follows: + - (or b, - If you have moved down in a document, this + or CTRL-B) will bring you back up one page (Page-Up). +</pre> + </blockquote> + + <h2>Keypad shortcuts</h2> + <p><strong>Lynx</strong> can use the digits 0-9 as movement + shortcuts. They are designed to work best when the <em>Num + Lock</em> on your keyboard is on, so that <strong>Lynx</strong> + can translate the numbers of your keypad into <a href= + "movement_help.html">movement commands</a>:</p> + + <blockquote> + <pre> 9 - page up 8 - up arrow 7 8 9 7 - moves to the top of a document @@ -34,41 +47,54 @@ 1 2 3 3 - page down 2 - down arrow 1 - moves to the end of a document +</pre> + </blockquote> - CTRL-A (or Find) - This Control key, and Function key synonym, - brings you back to the first page of the - current document (Home). + <h2>Control-characters</h2> - CTRL-E (or Select) - This Control key, and Function key synonym, - takes you to the last page of the current - document (End). + <blockquote> + <pre> + CTRL-A (or Find) - This Control key, and Function key synonym, + brings you back to the first page of the + current document (Home). - CTRL-N (or Remove) - This Control key, and Function key synonym, - moves you forward two lines in the current - document (Down-Two). + CTRL-E (or Select) - This Control key, and Function key synonym, + takes you to the last page of the current + document (End). + + CTRL-N (or Remove) - This Control key, and Function key synonym, + moves you forward two lines in the current + document (Down-Two). + + CTRL-P (or Insert) - This Control key, and Function key synonym, + moves you back two lines in the current + document (Up-Two). +</pre> + </blockquote> - CTRL-P (or Insert) - This Control key, and Function key synonym, - moves you back two lines in the current - document (Up-Two). + <h2>Ordinary characters</h2> - ) - Moves you forward half a page in the current - document (Down-Half). + <blockquote> + <pre> + ) - Moves you forward half a page in the current + document (Down-Half). - ( - Moves you back half a page in the current - document (Up-Half). + ( - Moves you back half a page in the current + document (Up-Half). - ^ - Go to the first link on the current line. + ^ - Go to the first link on the current line. - $ - Go to the last link on the current line. + $ - Go to the last link on the current line. - < - Go to the previous link in the current column. + < - Go to the previous link in the current column. - > - Go to the next link in the current column. + > - Go to the next link in the current column. - # - Jumps you to the pseudo Toolbar or Banner if - present in the current document. Use left-arrow - to return from there to your previous position - in the document. + # - Jumps you to the pseudo Toolbar or Banner if + present in the current document. Use left-arrow + to return from there to your previous position + in the document. </pre> + </blockquote> </body> </html> diff --git a/lynx_help/keystrokes/test_display.html b/lynx_help/keystrokes/test_display.html index 34d66e61..8cc4ab21 100644 --- a/lynx_help/keystrokes/test_display.html +++ b/lynx_help/keystrokes/test_display.html @@ -1,4 +1,4 @@ -<!-- $LynxId: test_display.html,v 1.8 2013/05/21 10:56:48 tom Exp $ --> +<!-- $LynxId: test_display.html,v 1.9 2014/01/08 00:05:32 tom Exp $ --> <!-- do not use tidy for this page --> <!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01//EN"> @@ -11,22 +11,27 @@ <link rev="made" href="mailto:lynx-dev@nongnu.org"> <meta http-equiv="Content-Type" content= "text/html; charset=us-ascii"> -</head> + <meta name="description" content= + "Display a test-page for common problems with Lynx's display character set and/or locale problems."> + </head> <body> - <h1>Try this page with Lynx 2.7.2 or above:</h1> - - <p>If you see several letters instead of a single - your promised - display charset does not support this character so "7 bit - approximation" is in effect. If you see any single letter which - definitely far from being supposed you have a wrong lynx - settings. <em>Press 'o' for Options menu and change "Display - character set"</em>. Try again if necessary.<br> - When you are satisfied save your changes in Options menu, + <p>If you see several letters instead of a single – your + promised display charset does not support this character so "7 + bit approximation" is in effect. If you see any single letter + which is unexpected, you have incorrect <strong>Lynx</strong> + settings.</p> + + <blockquote> + <p><em>Press 'o' for Options menu and change "Display character + set"</em>.<br> + Try again if necessary.</p> + </blockquote> + + <p>When you are satisfied save your changes in Options menu, thanks.</p> <pre> - 0x00A9 © # COPYRIGHT SIGN 0x00C7 Ç # LATIN CAPITAL LETTER C WITH CEDILLA @@ -39,7 +44,6 @@ 0x0108 Ĉ # LATIN CAPITAL LETTER C WITH CIRCUMFLEX 0x010C Č # LATIN CAPITAL LETTER C WITH CARON - 0x03BB λ # GREEK SMALL LETTER LAMDA 0x041B Л # CYRILLIC CAPITAL LETTER EL @@ -54,9 +58,6 @@ 0x255E ╞ # BOX DRAWINGS VERTICAL SINGLE AND RIGHT DOUBLE 0xFB01 fi # LATIN SMALL LIGATURE FI - - - </pre> <p>This is only a quick test to see obvious problems.</p> diff --git a/lynx_help/keystrokes/visited_help.html b/lynx_help/keystrokes/visited_help.html index 197eb498..a6dae243 100644 --- a/lynx_help/keystrokes/visited_help.html +++ b/lynx_help/keystrokes/visited_help.html @@ -1,4 +1,4 @@ -<!-- $LynxId: visited_help.html,v 1.8 2013/05/21 10:51:27 tom Exp $ --> +<!-- $LynxId: visited_help.html,v 1.9 2014/01/07 09:26:22 tom Exp $ --> <!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01//EN"> <html> @@ -10,21 +10,26 @@ <link rev="made" href="mailto:lynx-dev@nongnu.org"> <meta http-equiv="Content-Type" content= "text/html; charset=us-ascii"> -</head> + <meta name="description" content= + "Lynx provides an alternative to its history page, the visited-links page which highlights those which are of most interest."> + </head> <body> - <h1>Visited Links Page Help</h1> - - <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> + <h2>Overview</h2> + + <p><strong>Lynx</strong>'s <em>Visited Links Page</em> 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> + + <h2>Navigation</h2> <p>You may <a href="movement_help.html">select</a> any link on the Visited Links Page to retrieve a document that you had @@ -39,8 +44,13 @@ i.e., not just the links that were rendered and displayed by Lynx, itself.</p> + <h2>Configuration</h2> + <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> + "option_help.html#VP">Options Menu</a>). The menu allows you to + choose whether to view the list ordered by the first or last + visit, forward or reversed – or a mixture (a tree + structure).</p> </body> </html> diff --git a/lynx_help/keystrokes/xterm_help.html b/lynx_help/keystrokes/xterm_help.html index 4b65016d..0339f2dc 100644 --- a/lynx_help/keystrokes/xterm_help.html +++ b/lynx_help/keystrokes/xterm_help.html @@ -1,4 +1,4 @@ -<!-- $LynxId: xterm_help.html,v 1.7 2013/05/21 10:51:27 tom Exp $ --> +<!-- $LynxId: xterm_help.html,v 1.9 2014/01/09 00:17:28 tom Exp $ --> <!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01//EN"> <html> @@ -10,10 +10,12 @@ <link rev="made" href="mailto:lynx-dev@nongnu.org"> <meta http-equiv="Content-Type" content= "text/html; charset=us-ascii"> -</head> + <meta name="description" content= + "This outlines what is meant by an X terminal, for gopher support, i.e., something which can display images"> + </head> <body> - <h1>X Terminal or X Server</h1> + <h1>X Terminal Help</h1> <p>An X terminal is an electronic display terminal that communicates with a host computer system using the X Window |