diff options
| author | Daniel Baumann <daniel.baumann@progress-linux.org> | 2024-04-15 20:21:21 +0000 |
|---|---|---|
| committer | Daniel Baumann <daniel.baumann@progress-linux.org> | 2024-04-15 20:21:21 +0000 |
| commit | 510ed32cfbffa6148018869f5ade416505a450b3 (patch) | |
| tree | 0aafabcf3dfaab7685fa0fcbaa683dafe287807e /lynx_help/keystrokes | |
| parent | Initial commit. (diff) | |
| download | lynx-510ed32cfbffa6148018869f5ade416505a450b3.tar.xz lynx-510ed32cfbffa6148018869f5ade416505a450b3.zip | |
Adding upstream version 2.9.0rel.0.upstream/2.9.0rel.0
Signed-off-by: Daniel Baumann <daniel.baumann@progress-linux.org>
Diffstat (limited to 'lynx_help/keystrokes')
| -rw-r--r-- | lynx_help/keystrokes/alt_edit_help.html | 128 | ||||
| -rw-r--r-- | lynx_help/keystrokes/bashlike_edit_help.html | 277 | ||||
| -rw-r--r-- | lynx_help/keystrokes/bookmark_help.html | 58 | ||||
| -rw-r--r-- | lynx_help/keystrokes/cookie_help.html | 76 | ||||
| -rw-r--r-- | lynx_help/keystrokes/dired_help.html | 90 | ||||
| -rw-r--r-- | lynx_help/keystrokes/edit_help.html | 191 | ||||
| -rw-r--r-- | lynx_help/keystrokes/environments.html | 558 | ||||
| -rw-r--r-- | lynx_help/keystrokes/follow_help.html | 286 | ||||
| -rw-r--r-- | lynx_help/keystrokes/gopher_types_help.html | 87 | ||||
| -rw-r--r-- | lynx_help/keystrokes/history_help.html | 58 | ||||
| -rw-r--r-- | lynx_help/keystrokes/keystroke_help.html | 185 | ||||
| -rw-r--r-- | lynx_help/keystrokes/movement_help.html | 78 | ||||
| -rw-r--r-- | lynx_help/keystrokes/option_help.html | 823 | ||||
| -rw-r--r-- | lynx_help/keystrokes/other_help.html | 196 | ||||
| -rw-r--r-- | lynx_help/keystrokes/print_help.html | 62 | ||||
| -rw-r--r-- | lynx_help/keystrokes/scrolling_help.html | 117 | ||||
| -rw-r--r-- | lynx_help/keystrokes/test_display.html | 82 | ||||
| -rw-r--r-- | lynx_help/keystrokes/visited_help.html | 63 | ||||
| -rw-r--r-- | lynx_help/keystrokes/xterm_help.html | 52 |
19 files changed, 3467 insertions, 0 deletions
diff --git a/lynx_help/keystrokes/alt_edit_help.html b/lynx_help/keystrokes/alt_edit_help.html new file mode 100644 index 0000000..63f1044 --- /dev/null +++ b/lynx_help/keystrokes/alt_edit_help.html @@ -0,0 +1,128 @@ +<!-- $LynxId: alt_edit_help.html,v 1.21 2021/07/01 21:02:38 tom Exp $ --> +<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01//EN"> +<html> +<head> + <meta name="generator" content= + "HTML Tidy for HTML5 for Linux version 5.6.0"> + <title>Lynx Line Editor Alternative Key Binding</title> + <link rev="made" href="mailto:lynx-dev@nongnu.org"> + <link rel="Sibling" title="Default Binding" href= + "edit_help.html"> + <link rel="Sibling" title="Bash-Like Binding" href= + "bashlike_edit_help.html"> + <meta http-equiv="Content-Type" content= + "text/html; charset=us-ascii"> + <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> + <div class="nav"> + <ul> + <li><a href="#overview">Overview</a></li> + + <li><a href="#alternate_bindings">Table of key-bindings</a></li> + + <li><a href="#notes">Notes</a></li> + </ul> + </div> + + <h2><a name="overview" id="overview">Overview</a></h2> + + <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><strong><em>Note:</em></strong> setting emacs/vi keys ON has + no direct effect on line-editor bindings.</p> + + <h2><a name="alternate_bindings" id="alternate_bindings">Table of + key-bindings</a></h2> + + <p>This is the <em>Alternative Binding</em> keymap.</p> + + <pre> + ENTER Input complete - RETURN + TAB Input complete - TAB, Do + ABORT Input cancelled - Ctrl-G, Ctrl-O, (Ctrl-C on some systems) + ERASE Erase the line - Ctrl-U + + BACK Cursor back char - Left-Arrow, Ctrl-B + FORW Cursor forward char - Right-Arrow, Ctrl-F + BACKW Cursor back word - Ctrl-P + FORWW Cursor forward word - Ctrl-N + BOL Go to begin of line - Ctrl-A, Home, Find + EOL Go to end of line - Ctrl-E, End, Select + + DELP Delete prev char - Backspace, Delete, Remove + DELN Delete next char - Ctrl-D (<em><a href= +"#note_1">see note 1</a></em>) + DELPW Delete prev word - Ctrl-R + DELNW Delete next word - Ctrl-T + DELEL Delete to end of line - Ctrl-K + + UPPER Upper case the line - Ctrl-^ + LOWER Lower case the line - Ctrl-_ + + LKCMD Invoke cmd prompt - Ctrl-V (in form text fields, only) (<em><a href="#note_2">see note 2</a></em>) + +<a name="TASpecial" id= +"TASpecial">Special commands for use only in textarea fields</a> (<em><a href="#note_3">see note 3</a></em>): + + Textarea external edit - Ctrl-X e + Insert file in textarea - Ctrl-X i + Grow textarea - Ctrl-X g +</pre> + <h2><a name="emacs_bindings" id="emacs_bindings">Emacs-like + commands</a></h2> + + <pre> + TPOS Transpose characters - Ctrl-t + SETMARK Set mark at current position in line - Ctrl-@ + XPMARK Exchange current position with mark - Ctrl-x Ctrl-x + KILLREG Kill region between mark and position - Ctrl-x Ctrl-w (<em><a href="#note_3">see note 3</a></em>) + YANK Insert text last killed (with KILLREG) - Ctrl-y +</pre> + <h2><a name="examples" id="examples">Try it yourself</a></h2> + + <p>Here is a little textarea for practice:</p> + + <form action=""> + <p> + <textarea name="practice" cols="40" rows= + "5">This text cannot be submitted. Normally lines like +these would be part of a form that is filled out and +then submitted. You can move around here and delete +or add text as you like, using the Line-Editor keys. +</textarea><input type="reset" value="[reset content]"> + </p> + </form> + + <h2><a name="special_keys" id="special_keys">Special keys</a></h2> + + <p>See the <em><a href="edit_help.html#special_keys">Lynx Line + Editor</a></em> page for an explanation of terminology and + key-names.</p> + + <h2><a name="notes" id="notes">Notes</a></h2> + + <ol> + <li id="note_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.</li> + + <li id="note_2">Follow Ctrl-V with any recognized key command, + to "escape" from a text input field.</li> + + <li id="note_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.</li> + </ol> +</body> +</html> diff --git a/lynx_help/keystrokes/bashlike_edit_help.html b/lynx_help/keystrokes/bashlike_edit_help.html new file mode 100644 index 0000000..621e3e0 --- /dev/null +++ b/lynx_help/keystrokes/bashlike_edit_help.html @@ -0,0 +1,277 @@ +<!-- $LynxId: bashlike_edit_help.html,v 1.22 2021/07/01 21:02:38 tom Exp $ --> +<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01//EN"> +<html> +<head> + <meta name="generator" content= + "HTML Tidy for HTML5 for Linux version 5.6.0"> + <title>Lynx Line Editor Bash-Like Key Binding</title> + <link rev="made" href="mailto:lynx-dev@nongnu.org"> + <link rel="Sibling" title="Default Binding" href= + "edit_help.html"> + <link rel="Sibling" title="Alternative Binding" href= + "alt_edit_help.html"> + <meta http-equiv="Content-Type" content= + "text/html; charset=us-ascii"> + <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> + <div class="nav"> + <ul> + <li><a href="#overview">Overview</a></li> + + <li><a href="#bash_bindings">Bash-like bindings</a></li> + + <li><a href="#examples">Try it yourself</a></li> + + <li><a href="#emacs_bindings">Emacs-like commands</a></li> + + <li><a href="#special_keys">Comments on special keys</a></li> + + <li><a href="#notes">Notes</a></li> + + <li><a href="#miscellaneous">Additional details</a></li> + </ul> + </div> + + <h2><a name="overview" id="overview">Overview</a></h2> + + <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. 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>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><strong><em>Note:</em></strong> setting emacs/vi keys ON has + no direct effect on line-editor bindings.</p> + + <h2><a name="bash_bindings" id="bash_bindings">Bash-like + bindings</a></h2> + + <p>This is the <em>Bash-like Binding</em> keymap.</p> + + <pre> + ENTER Input complete - Enter, RETURN + TAB Completion / Next - TAB, Do (<em><a href= +"#note_2">see note 2</a></em>) + ABORT Cancel / Undo Change - Ctrl-g, Ctrl-_ + ERASE Erase the line - M-k, Ctrl-x k + + BACK Cursor back char - Left-Arrow, Ctrl-b + FORW Cursor forward char - Right-Arrow, Ctrl-f + BACKW Cursor back word - M-b, Ctrl-r + FORWW Cursor forward word - M-f, Ctrl-s (<em><a href= +"#note_5">see note 5</a></em>) + BOL Go to begin of line - Ctrl-a, Home, Find + EOL Go to end of line - Ctrl-e, End, Select (<em><a href="#note_4">see note 4</a></em>) + + DELP Delete prev char - Backspace + DELN Delete next char - Ctrl-d, Delete, Remove (<em><a href="#note_1">see note 1</a></em>) + DELPW Delete prev word - Ctrl-w, M-Backspace, M-Delete (<em><a href="#note_3">see note 3</a></em>) + DELNW Delete next word - M-d + DELBL Delete to beg of line - Ctrl-u + DELEL Delete to end of line - Ctrl-k (<em><a href= +"#note_4">see note 4</a></em>) + + UPPER Upper case the line - M-u + LOWER Lower case the line - M-l + + LKCMD Invoke cmd prompt - Ctrl-v [FORM] (<em><a href= +"#note_6">see note 6</a></em>) + SWMAP Switch input keymap - Ctrl-^ (if compiled in) + +<a name="TASpecial" id= +"TASpecial">Special commands for use in textarea fields</a> [FORM]: + + PASS! Textarea external edit - Ctrl-e Ctrl-e, Ctrl-x e (<em><a href="#note_4">see note 4</a></em>) + PASS! Insert file in textarea - Ctrl-x i + PASS! Grow textarea - Ctrl-x g +</pre> + <h2><a name="examples" id="examples">Try it yourself</a></h2> + + <p>Here is a little textarea for practice:</p> + + <form action=""> + <p> + <textarea name="practice" cols="40" rows= + "5">This text cannot be submitted. Normally lines like +these would be part of a form that is filled out and +then submitted. You can move around here and delete +or add text as you like, using the Line-Editor keys. +</textarea><input type="reset" value="[reset content]"> + </p> + </form> + + <h2><a name="emacs_bindings" id="emacs_bindings">Emacs-like + commands</a></h2> + + <pre> + TPOS Transpose characters - Ctrl-t + SETMARK Set mark at current position in line - Ctrl-@ + XPMARK Exchange current position with mark - Ctrl-x Ctrl-x + KILLREG Kill region between mark and position - Ctrl-x Ctrl-w (<em><a href="#note_3">see note 3</a></em>) + YANK Insert text last killed (with KILLREG) - Ctrl-y +</pre> + <h2><a name="special_keys" id="special_keys">Special keys</a></h2> + + <p>See the <em><a href="edit_help.html#special_keys">Lynx Line + Editor</a></em> page for an explanation of terminology and + key-names.</p> + + <h2><a name="notes" id="notes">Notes</a></h2> + + <ol> + <li id="note_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.</li> + + <li id="note_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.</li> + + <li id="note_3">Ctrl-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 id="note_4">These keys invoke special behavior when pressed + twice in a row: Ctrl-e Ctrl-e calls the external editor for + changing the text in a textarea (if available). Ctrl-k Ctrl-k + will move to the next link, so that all lines in a textarea can + be conveniently cleared by repeating Ctrl-k.</li> + + <li id="note_5">Key is likely unavailable for + <strong>Lynx</strong>, 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 does not apply.</li> + + <li id="note_6">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 Ctrl-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><a name="miscellaneous" id="miscellaneous">Additional + details</a></h2> + + <p>Here are some additional details on other keys, for the + curious (very much subject to change)</p> + + <pre> +Normal key action when used in form fields, subject to remapping +with KEYMAP: [FORM (except Up-Arrow, Down-Arrow)] + Ctrl-l (<em><a href="#note_3">see note 3</a></em>) + Ctrl-o, Ctrl-z, Ctrl-\, Ctrl-] (<em><a href= +"#note_5">see note 5</a></em>) + Ctrl-n [emacskey], Ctrl-p [emacskey] + Up-Arrow, Down-Arrow (<em><a href= +"#note_2">see note 2</a></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-Ctrl-l (<em><a href= +"#note_3">see note 3</a></em>) M-Ctrl-o <a href="#no_meta">[!]</a>, + M-Ctrl-z, M-Ctrl-\, M-Ctrl-] (<em><a href= +"#note_5">see note 5</a></em>) + M-Ctrl-u, M-/, M-n + M-Up-Arrow <a href= +"#no_meta">[!]</a>, M-Down-Arrow <a href= +"#no_meta">[!]</a> (<em><a href="#note_2">see note 2</a></em>) + M-Page-Up <a href= +"#no_meta">[!]</a>, M-Page-Down <a href= +"#no_meta">[!]</a>, M-Home, M-End + +Passed as specific command: + lynx action duplicates by default + ----------- --------------------- + M-Ctrl-d NEXT_LINK Down-Arrow + M-Ctrl-e EDITTEXTAREA Ctrl-e Ctrl-e + M-Ctrl-k LPOS_NEXT_LINK (none, Down-Arrow suggested) + M-e EDITTEXTAREA Ctrl-e Ctrl-e + M-g GROWTEXTAREA (none, Ctrl-v $ suggested?) + M-i INSERTFILE (none, Ctrl-v # suggested?) + M-< HOME M-Home + M-> END M-End + M-F1 DWIMHELP F1 + M-Find WHEREIS Ctrl-v / + M-Select NEXT Ctrl-v n + +Duplicates function of other key(s): + edit action duplicates + ----------- ---------- + M-Ctrl-b BACKW M-b, Ctrl-r + M-Ctrl-f FORWW M-f + M-Ctrl-n FORWW M-f + M-Ctrl-p BACKW M-b, Ctrl-r + M-Ctrl-r BACKW M-b, Ctrl-r + M-a BOL Ctrl-a, Home, ... + +Modifier ignored, and duplicates function of other key(s): + edit action duplicates + ----------- ---------- + M-Ctrl-a BOL Ctrl-a, Home, ... + M-Ctrl-g ABORT Ctrl-g, ... + M-TAB TAB Ctrl-i <a href= +"#no_meta">[!]</a> + M-Ctrl-j ENTER Ctrl-m, Ctrl-j, Enter / RETURN + M-RETURN ENTER Ctrl-m, Ctrl-j, Enter / RETURN + M-Ctrl-y YANK Ctrl-y <a href= +"#no_meta">[!]</a> + M-Ctrl-^ SWMAP Ctrl-^ <a href= +"#no_meta">[!]</a> (if compiled in) + M-Right-Arrow FORW Right-Arrow <a href= +"#no_meta">[!]</a>, Ctrl-f + M-Left-Arrow BACK Left-Arrow <a href= +"#no_meta">[!]</a>, Ctrl-b + M-Do TAB Ctrl-i <a href= +"#no_meta">[!]</a> + +Key completely ignored: + Ctrl-q, Insert + M-Ctrl-q, M-Ctrl-s, M-Ctrl-t, M-Ctrl-v, M-ESC (<em><a href="#note_5">see note 5</a></em>) + M-Ctrl-@, M-Ctrl-_, M-Remove, M-Insert <a href= +"#no_meta">[!]</a> + +Meta + other (mostly, printable character) keys: + Modifier ignored, or sequence swallowed (<em><a href= +"#note_5">see note 5</a></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. + +[emacskey] Normal key action subject to emacs_keys setting. + +<a name="no_meta" id= +"no_meta">[!]</a> Action of key with Meta modifier follows action of key without + Meta. If you manage to enter the Meta key while Line-Editor + Binding is not set to Bash-Like, and the unmodified binding + is different from that listed here, M-<<var>key</var>> will act + like <<var>key</var>>. +</pre> +</body> +</html> diff --git a/lynx_help/keystrokes/bookmark_help.html b/lynx_help/keystrokes/bookmark_help.html new file mode 100644 index 0000000..87d8591 --- /dev/null +++ b/lynx_help/keystrokes/bookmark_help.html @@ -0,0 +1,58 @@ +<!-- $LynxId: bookmark_help.html,v 1.11 2021/07/01 21:02:38 tom Exp $ --> +<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01//EN"> +<html> +<head> + <meta name="generator" content= + "HTML Tidy for HTML5 for Linux version 5.6.0"> + <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"> + <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> + <div class="nav"> + <ul> + <li><a href="#overview">Bookmark files</a></li> + + <li><a href="#internal_edit">Updating within Lynx</a></li> + + <li><a href="#external_edit">Updating with a text editor</a></li> + </ul> + </div> + + <h2><a name="overview" id="overview">Bookmark files</a></h2> + + <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> + + <h2><a name="internal_edit" id="internal_edit">Updating within + Lynx</a></h2> + + <ul> + <li>The append feature, invoked by pressing an + “<em>a</em>” while viewing a document will add the + current document or the currently highlighted link to your + default <em>Bookmark file</em>, or to one you select if + multiple bookmarks are enabled.</li> + + <li>The remove feature, invoked by pressing an + “<em>r</em>” when a <em>Bookmark file</em> is being + displayed, will remove the currently highlighted link.</li> + + <li>You may set and modify the paths and names of your + <em>Bookmark files</em> and enable or disable multiple + bookmarks in the <a href="option_help.html">Options + Menu</a>.</li> + </ul> + + <h2><a name="external_edit" id="external_edit">Updating with a + text editor</a></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 new file mode 100644 index 0000000..80e01d6 --- /dev/null +++ b/lynx_help/keystrokes/cookie_help.html @@ -0,0 +1,76 @@ +<!-- $LynxId: cookie_help.html,v 1.12 2021/07/01 21:02:38 tom Exp $ --> +<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01//EN"> +<html> +<head> + <meta name="generator" content= + "HTML Tidy for HTML5 for Linux version 5.6.0"> + <title>Help on the Cookie Jar Page</title> + <link rev="made" href="mailto:lynx-dev@nongnu.org"> + <meta http-equiv="Content-Type" content= + "text/html; charset=us-ascii"> + <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> + <div class="nav"> + <ul> + <li><a href="#overview">Overview</a></li> + + <li><a href="#showing_cookies">Cookie Details Shown</a></li> + + <li><a href="#removing_cookies">Removing Cookies</a></li> + </ul> + </div> + + <h2><a name="overview" id="overview">Overview</a></h2> + + <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 <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><a name="showing_cookies" id="showing_cookies">Cookie Details + Shown</a></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 + whether the <em>secure</em> flag is set for the cookie, in which + case it will be sent only via secure connections (presently, only + SSL). The <em>Maximum Gobble Date</em>, i.e., when the cookie is + intended to expire, also is indicated. Also, a server may change + the expiration date, or cause the cookie to be deleted, in its + replies to subsequent requests from <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><a name="removing_cookies" id="removing_cookies">Removing + Cookies</a></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 + will invoke a prompt asking whether all cookies in that + <em>domain</em> should be <em>Gobbled</em> (deleted from the + <em>Cookie Jar</em>), and/or whether the <em>domain</em> entry + should be <em>Gobbled</em> if all of its cookies have been + <em>Gobbled</em>, or whether to change the “allow” + setting for that <em>domain</em>. Activating a cookie's + name=value link will cause that particular cookie to be + <em>Gobbled</em>. You will be prompted for confirmations of + deletions, to avoid any accidental <em>Gobbling</em>.</p> +</body> +</html> diff --git a/lynx_help/keystrokes/dired_help.html b/lynx_help/keystrokes/dired_help.html new file mode 100644 index 0000000..f3e7e05 --- /dev/null +++ b/lynx_help/keystrokes/dired_help.html @@ -0,0 +1,90 @@ +<!-- $LynxId: dired_help.html,v 1.12 2021/07/01 21:02:38 tom Exp $ --> +<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01//EN"> +<html> +<head> + <meta name="generator" content= + "HTML Tidy for HTML5 for Linux version 5.6.0"> + <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"> + <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> + <div class="nav"> + <ul> + <li><a href="#overview">Overview</a></li> + + <li><a href="#dired_bindings">Dired Key bindings</a></li> + + <li><a href="#other_bindings">Other Key bindings</a></li> + + <li><a href="#notes">Notes</a></li> + </ul> + </div> + + <h2><a name="overview" id="overview">Overview</a></h2> + + <p><strong>Lynx</strong> changes into <em>Dired mode</em> when + you use a URL of the type <em>file://localhost/path/</em>.</p> + + <h2><a name="dired_bindings" id="dired_bindings">Dired Key + bindings</a></h2> + + <p>While in Dired mode, some keys are remapped to do the + following functions:</p> + + <blockquote> + <pre> + + C)reate - Create a new, empty file in the current + directory. You will be prompted to enter + a name for the file. + + F)ull menu - Show a full menu of commands for currently + selected file or directory. + + 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> + + <h2><a name="other_bindings" id="other_bindings">Other Key + bindings</a></h2> + + <p>Some other keys useful in <em>Dired mode</em>:</p> + + <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. +</pre> + </blockquote> + + <h2><a name="notes" id="notes">Notes</a></h2> + + <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 new file mode 100644 index 0000000..42d3e8a --- /dev/null +++ b/lynx_help/keystrokes/edit_help.html @@ -0,0 +1,191 @@ +<!-- $LynxId: edit_help.html,v 1.30 2021/07/01 21:02:38 tom Exp $ --> +<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01//EN"> +<html> +<head> + <meta name="generator" content= + "HTML Tidy for HTML5 for Linux version 5.6.0"> + <title>Lynx Line Editor Default Key Binding</title> + <link rev="made" href="mailto:lynx-dev@nongnu.org"> + <meta http-equiv="Content-Type" content= + "text/html; charset=us-ascii"> + <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> + <div class="nav"> + <ul> + <li><a href="#overview">Overview</a></li> + + <li><a href="#regular_keymap">Regular Keymap</a></li> + + <li><a href="#editing_keymap">Editing Keymap</a></li> + + <li><a href="#examples">Try it yourself</a></li> + + <li><a href="#notes">Notes</a></li> + </ul> + </div> + + <h2><a name="overview" id="overview">Overview</a></h2> + + <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</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><strong><em>Note:</em></strong> setting emacs/vi keys ON has + no effect on line-editor bindings.</p> + + <h2><a name="regular_keymap" id="regular_keymap">Regular + Keymap</a></h2> + + <p>This is the <em>Default Binding</em> keymap:</p> + + <pre> + ENTER Input complete - RETURN + TAB Input complete - TAB, Do + ABORT Input cancelled - Ctrl-G, Ctrl-O, (Ctrl-C on some systems) + ERASE Erase the line - Ctrl-U + + BACK Cursor back char - Left-Arrow + FORW Cursor forward char - Right-Arrow + BACKW Cursor back word - Ctrl-P + FORWW Cursor forward word - Ctrl-N + BOL Go to begin of line - Ctrl-A, Home, Find + EOL Go to end of line - Ctrl-E, End, Select + + DELP Delete prev char - Backspace, Delete, Remove + DELN Delete next char - Ctrl-D, Ctrl-R (<em><a href= +"#note_1">see note 1</a></em>) + DELPW Delete prev word - Ctrl-B + DELNW Delete next word - Ctrl-F + DELEL Delete to end of line - Ctrl-_ + + 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) (<em><a href="#note_2">see note 2</a></em>) + SWMAP Switch input keymap - Ctrl-^ (if compiled in) +</pre> + <h2><a name="editing_keymap" id="editing_keymap">Editing + Keymap</a></h2> + + <p><a name="TASpecial" id="TASpecial">These are special commands + for use only in textarea fields</a> (<em><a href="#note_3">see + note 3</a></em>):</p> + + <pre> + Textarea external edit - Ctrl-X e + Insert file in textarea - Ctrl-X i + Grow textarea - Ctrl-X g +</pre> + <h2><a name="emacs_bindings" id="emacs_bindings">Emacs-like + commands</a></h2> + + <pre> + TPOS Transpose characters - Ctrl-t + SETMARK Set mark at current position in line - Ctrl-@ + XPMARK Exchange current position with mark - Ctrl-x Ctrl-x + KILLREG Kill region between mark and position - Ctrl-x Ctrl-w (<em><a href="#note_3">see note 3</a></em>) + YANK Insert text last killed (with KILLREG) - Ctrl-y +</pre> + <h2><a name="examples" id="examples">Try it yourself</a></h2> + + <p>Here is a little textarea for practice:</p> + + <form action=""> + <p> + <textarea name="practice" cols="40" rows= + "5">This text cannot be submitted. Normally lines like +these would be part of a form that is filled out and +then submitted. You can move around here and delete +or add text as you like, using the Line-Editor keys. +</textarea><input type="reset" value="[reset content]"> + </p> + </form> + + <h2><a name="special_keys" id="special_keys">Special keys</a></h2> + + <p><samp><dfn>Ctrl-</dfn><strong>key</strong> means + Control+<strong><kbd>key</kbd></strong>. + <dfn><code>Ctrl-x</code></dfn> <strong>key</strong> means first + Control+<kbd>x</kbd>, then <strong><kbd>key</kbd></strong>. + <dfn>M-</dfn>key means Meta+<strong><kbd>key</kbd></strong>, + where Meta is a modifier that can be entered in a variety of + ways:</samp> + </p> + + <ul> + <li>First ESC, then the <strong><kbd>key</kbd></strong>. This + does not work with all systems or on all connections, and if it + does may not work for some keys (because the ESC character is + also part of code sequences for "normal" function keys).</li> + + <li>Alt+<strong><kbd>key</kbd></strong>. This works if the + terminal, console, or comm program is set up to interpret Alt + as a modifier to send ESC. The Linux console acts like that by + default for most keys; Kermit can be set up to do it, xterm can + be for some keys, and so on. But the same caveats as for the + previous item apply. This Alt mapping may also be possible, + independent of the ESC character, for some keys in + <strong>Lynx</strong> for DOS/i386 or for Win32.</li> + + <li>Ctrl-x <strong><kbd>key</kbd></strong>. Actually, currently + the same internal table is used for Meta and the Ctrl-x prefix. + Therefore all M-<strong><kbd>key</kbd></strong> combinations + can also be typed as Ctrl-x <strong><kbd>key</kbd></strong>, + and vice versa.</li> + </ul> + + <p>A few key names may be less familiar now than when + <strong>Lynx</strong> was first written: <em>Find</em>, + <em>Select</em> and <em>Remove</em>. The <a href= + "https://invisible-island.net/xterm/xterm.faq.html#xterm_keypad">XTerm + FAQ</a> shows some typical keypad layouts of emulators for VT220 + and other DEC terminals.</p> + + <p>The VT220 did not have a “backspace” key but + <strong>Lynx</strong>'s default bindings mention it. Both ASCII + <samp>BS</samp> (backspace) and <samp>DEL</samp> are bound by + default to the same functions. <samp>DEL</samp> (occasionally + referred to as <samp>RUBOUT</samp>) is not the same as + <samp>Delete</samp>: the former is a single character while the + latter is usually a sequence of characters.</p> + + <h2><a name="notes" id="notes">Notes</a></h2> + + <ol> + <li id="note_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.</li> + + <li id="note_2">Follow Ctrl-V with any recognized key command, + to "escape" from a text input field.</li> + + <li id="note_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.</li> + </ol> +</body> +</html> diff --git a/lynx_help/keystrokes/environments.html b/lynx_help/keystrokes/environments.html new file mode 100644 index 0000000..1d7245a --- /dev/null +++ b/lynx_help/keystrokes/environments.html @@ -0,0 +1,558 @@ +<!-- $LynxId: environments.html,v 1.22 2021/07/01 21:02:38 tom Exp $ --> +<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01//EN"> +<html> +<head> + <meta name="generator" content= + "HTML Tidy for HTML5 for Linux version 5.6.0"> + <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"> + <meta name="description" content= + "Describes environment variables used by Lynx. Some are specific to Lynx, others are common with similar programs."> +</head> +<body> + <div class="nav"> + <ul> + <li><a href="#overview">Environment Variables</a></li> + + <li><a href="#env">Variables Used By Lynx</a></li> + + <li><a href="#setenv">Variables Set or Modified By Lynx</a></li> + + <li><a href="#cgi">Simulated CGI Support</a></li> + + <li><a href="#language">Native Language Support</a></li> + + <li><a href="#proxy">Proxy details and examples</a></li> + + <li><a href="#dos">Win32 (95/NT) and 386 DOS</a></li> + </ul> + </div> + + <h2><a name="overview" id="overview">Environment Variables</a></h2> + + <pre> + In addition to various “standard” environment variables + 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 <strong>Lynx</strong> to pass data to + an external program, or for other reasons. These are + listed separately <a href="#setenv">below</a>. + + See also the sections on <a href= +"#cgi">Simulated CGI Support</a> and + <a href="#language">Native Language Support</a>, below. + + Note: Not all environment variables apply to all types of + 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> + <h2><a name="env" id="env">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 <strong>Lynx</strong> + was built using the slang screen-handling + library. + + LYNX_CFG + This variable, if set, will override + the default location and name of the + global configuration file (normally, + lynx.cfg) that was defined by the + LYNX_CFG_FILE constant in the + userdefs.h file, during installation. + See the userdefs.h file for more + information. + + LYNX_HELPFILE + If set, this variable overrides the + compiled-in URL and configuration file + URL for the <strong>Lynx</strong> help file. + + LYNX_LOCALEDIR + If set, this variable overrides the + compiled-in location of the locale + directory which contains native lan- + guage (NLS) message text. + + LYNX_LSS + This variable, if set, specifies the + location of the default <strong>Lynx</strong> character + style sheet file. [Currently only + meaningful if <strong>Lynx</strong> was built using + experimental color style support.] + + LYNX_SAVE_SPACE + This variable, if set, will override + the default path prefix for files + saved to disk that is defined in the + lynx.cfg SAVE_SPACE: statement. See + the lynx.cfg file for more information. + + LYNX_TEMP_SPACE + This variable, if set, will override + the default path prefix for temporary + files that was defined during installation, + as well as any value that may + be assigned to the TMPDIR variable. + + LYNX_TRACE + If set, causes <strong>Lynx</strong> to write a trace + file as if the -trace option were sup- + plied. + + LYNX_TRACE_FILE + If set, overrides the compiled-in name + of the trace file, which is either + Lynx.trace or LY-TRACE.LOG (the latter + on the DOS platform). The trace file + is in either case relative to the home + directory. + + MAIL + This variable specifies the default + inbox <strong>Lynx</strong> will check for new mail, if + such checking is enabled in the + lynx.cfg file. + + NEWS_ORGANIZATION + This variable, if set, provides the + string used in the Organization: + header of USENET news postings. It will + override the setting of the ORGANIZATION + environment variable, if it is also set + (and, on UNIX, the contents of an + /etc/organization file, if present). + + NNTPSERVER + If set, this variable specifies the + default NNTP server that will be used + for USENET news reading and posting + with <strong>Lynx</strong>, via news: URL's. + + ORGANIZATION + This variable, if set, provides the + string used in the Organization: + header of USENET news postings. On + UNIX, it will override the contents of + an /etc/organization file, if present. + + <em>PROTOCOL</em>_proxy + <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 <strong>Lynx</strong> (http, ftp, + gopher, etc), can be mapped separately + by setting environment variables of + the form <em>PROTOCOL</em>_proxy (literally: + http_proxy, ftp_proxy, gopher_proxy, + etc), to “http://some.server.dom:port/”. + See <a href= +"#proxy">Proxy details and examples</a>. + + WWW_<em>access</em>_GATEWAY + <strong>Lynx</strong> still supports use of gateway + servers, with the servers specified + via “WWW_<em>access</em>_GATEWAY” variables + (where “access” is lower case and can + be “http”, “ftp”, “gopher” or “wais”), + however most gateway servers have been + discontinued. Note that you do not + include a terminal “/” for gateways, + but do for proxies specified by <em>PROTOCOL</em>_proxy + environment variables. See <a href= +"#proxy">Proxy details</a>. + + WWW_HOME + This variable, if set, will override + the default startup URL specified in + any of the <strong>Lynx</strong> configuration files. +</pre> + <h2><a name="setenv" id="setenv">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 + created for use by an external program, + as defined in a lynx.cfg + PRINTER: definition statement. If the + field does not exist for the document, + the variable is set to a null string + under UNIX, or “No Date” under VMS. + + 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. + It is created for use by an external + program, as defined in a lynx.cfg + PRINTER: definition statement. If the + field does not exist for the document, + the variable is set to a null string + under UNIX, or “No LastMod” under VMS. + + 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. + It is created for use by an external + program, as defined in a lynx.cfg + PRINTER: definition statement. If the + field does not exist for the document, + the variable is set to a null string + under UNIX, or “No Title” under VMS. + + 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 + created for use by an external program, + as defined in a lynx.cfg + PRINTER: definition statement. If the + field does not exist for the document, + the variable is set to a null string + under UNIX, or “No URL” under VMS. + + 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 + <strong>Lynx</strong>. See also the comments in the + distribution's sample mailcap file, + for notes on usage in such a file. + + SSL_CERT_DIR Set to the directory containing trusted + certificates. + + SSL_CERT_FILE Set to the full path and filename for + your file of trusted certificates. + + TERM Normally, this variable is used by + <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, + <strong>Lynx</strong> will set or modify its value + to the user specified terminal type + (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> + + <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 + + DOCUMENT_ROOT + + HTTP_ACCEPT_CHARSET + + HTTP_ACCEPT_LANGUAGE + + HTTP_USER_AGENT + + PATH_INFO + + PATH_TRANSLATED + + QUERY_STRING + + REMOTE_ADDR + + REMOTE_HOST + + REQUEST_METHOD + + SERVER_SOFTWARE +</pre> + <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 + the language. Language codes are NOT + the same as the country codes given in + ISO 3166. + + LANGUAGE This variable, if set, will override + the default message language. This is a + GNU extension that has higher priority for + setting the message catalog than LANG or + LC_ALL. + + LC_ALL and + + LC_MESSAGES These variables, if set, specify the + notion of native language formatting + style. They are POSIXly correct. + + LINGUAS This variable, if set prior to configuration, + limits the installed languages to specific values. + It is a space-separated list of two-letter codes. + Currently, it is hard-coded to a wish list. + + 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> + + <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 <em>PROTOCOL</em>_proxy environment variables as shown + below:</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 <em>PROTOCOL</em>_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> + <p>386 version only:<br></p> + + <pre> + WATTCP.CFG Set to the full path for the WATTCP.CFG directory +</pre> + <p>(Depending on how you compiled libtcp.a, you may have to use + WATCONF.)</p> + + <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 +</pre> + <p>In lynx_386, a typical batch file might look like:</p> + + <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 +</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 new file mode 100644 index 0000000..1c9ca08 --- /dev/null +++ b/lynx_help/keystrokes/follow_help.html @@ -0,0 +1,286 @@ +<!-- $LynxId: follow_help.html,v 1.17 2021/07/01 21:02:38 tom Exp $ --> +<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01//EN"> +<html> +<head> + <meta name="generator" content= + "HTML Tidy for HTML5 for Linux version 5.6.0"> + <title>Help on the Follow link (or page) number feature</title> + <link rev="made" href="mailto:lynx-dev@nongnu.org"> + <meta http-equiv="Content-Type" content= + "text/html; charset=us-ascii"> + <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> + <div class="nav"> + <ul> + <li><a href="#overview">Overview</a></li> + + <li><a href="#numbering">Zero and other digits</a></li> + + <li><a href="#suffixes">Suffixes</a></li> + + <li><a href="#form_fields">Specifics for Form Fields</a></li> + + <li><a href="#hidden_links">Hidden Links</a></li> + + <li><a href="#goto_hidden_link">Navigating to Hidden + Links</a></li> + </ul> + </div> + + <h2><a name="overview" id="overview">Overview</a></h2> + + <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:</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><a name="numbering" id="numbering">Zero and other digits</a></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 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><a name="suffixes" id="suffixes">Suffixes</a></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><a name="form_fields" id="form_fields">Specifics for Form + Fields</a></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:</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 will not appear on screen, but the + user can still navigate using these commands.</p> + + <h2><a name="hidden_links" id="hidden_links">Hidden Links</a></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><a name="goto_hidden_link" id="goto_hidden_link">Navigating + to Hidden Links</a></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.</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 new file mode 100644 index 0000000..ac6b090 --- /dev/null +++ b/lynx_help/keystrokes/gopher_types_help.html @@ -0,0 +1,87 @@ +<!-- $LynxId: gopher_types_help.html,v 1.13 2021/07/01 21:02:38 tom Exp $ --> +<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01//EN"> +<html> +<head> + <meta name="generator" content= + "HTML Tidy for HTML5 for Linux version 5.6.0"> + <title>Listing of Gopher types</title> + <link rev="made" href="mailto:lynx-dev@nongnu.org"> + <meta http-equiv="Content-Type" content= + "text/html; charset=us-ascii"> + <meta name="description" content= + "This is a list of the file-types which are known to Lynx in its gopher interface."> +</head> +<body> + <div class="nav"> + <ul> + <li><a href="#overview">Listing of Gopher types</a></li> + </ul> + </div> + + <h2><a name="overview" id="overview">Listing of Gopher types</a></h2> + + <dl> + <dt>(FILE)</dt> + + <dd>An ASCII file</dd> + + <dt>(DIR)</dt> + + <dd>A directory listing</dd> + + <dt>(CSO)</dt> + + <dd>The Computing Services Organizations nameserver + interface</dd> + + <dt>(BIN)</dt> + + <dd> + A binary file with one of the following meanings + <ul> + <li>A Binary file with PC extensions</li> + + <li>A Binary file with UNIX extensions</li> + </ul> + </dd> + + <dt>(HQX)</dt> + + <dd>A Macintosh file that has been BinHexed</dd> + + <dt>(?)</dt> + + <dd>A searchable database</dd> + + <dt>(IMG)</dt> + + <dd>An unknown image type<br> + You must have an <a href="xterm_help.html">X terminal</a> to + view images</dd> + + <dt>(GIF)</dt> + + <dd>An image in Graphics Interchange Format<br> + You must have an <a href="xterm_help.html">X terminal</a> to + view images</dd> + + <dt>(HTML)</dt> + + <dd>A World Wide Web hypertext file</dd> + + <dt>(TEL)</dt> + + <dd>The link will open a connection to another host using + telnet</dd> + + <dt>(3270)</dt> + + <dd>The link will open a connection to another host using + tn3270</dd> + + <dt>(UKN)</dt> + + <dd>An unknown or unsupported type</dd> + </dl> +</body> +</html> diff --git a/lynx_help/keystrokes/history_help.html b/lynx_help/keystrokes/history_help.html new file mode 100644 index 0000000..62f45df --- /dev/null +++ b/lynx_help/keystrokes/history_help.html @@ -0,0 +1,58 @@ +<!-- $LynxId: history_help.html,v 1.10 2021/07/01 21:02:38 tom Exp $ --> +<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01//EN"> +<html> +<head> + <meta name="generator" content= + "HTML Tidy for HTML5 for Linux version 5.6.0"> + <title>Help on the History Page</title> + <link rev="made" href="mailto:lynx-dev@nongnu.org"> + <meta http-equiv="Content-Type" content= + "text/html; charset=us-ascii"> + <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> + <div class="nav"> + <ul> + <li><a href="#overview">Overview</a></li> + + <li><a href="#navigation">Navigation</a></li> + </ul> + </div> + + <h2><a name="overview" id="overview">Overview</a></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><a name="navigation" id="navigation">Navigation</a></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 + visited. That link, and any subsequent to it, will not be removed + from the history stack if you return to it via the History Page. + You thus should use a History Page link, rather than the + <em>left-arrow</em> key, if you wish to review previous documents + without needing to remember and repeat the series of selections + for reaching your currently displayed document.</p> + + <p>Upon using <em>left-arrow</em> in the document selected via + the History Page, you will be returned to the document from which + you initially went to the History Page.</p> + + <p>If a previously visited link has been removed from the history + stack, and it was not a temporary menu or list file, bookmark + file, or document associated with POST content, it can still be + selected conveniently via the <a href="visited_help.html">Visited + Links Page</a>. The latter also will include links which were + “<em>d</em>”ownloaded or passed to a helper + application, and thus were not included in the history stack.</p> +</body> +</html> diff --git a/lynx_help/keystrokes/keystroke_help.html b/lynx_help/keystrokes/keystroke_help.html new file mode 100644 index 0000000..f079c78 --- /dev/null +++ b/lynx_help/keystrokes/keystroke_help.html @@ -0,0 +1,185 @@ +<!-- $LynxId: keystroke_help.html,v 1.24 2023/11/05 10:04:26 tom Exp $ --> +<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01//EN"> +<html> +<head> + <meta name="generator" content= + "HTML Tidy for HTML5 for Linux version 5.6.0"> + <title>Help on Lynx Keystroke Commands</title> + <link rev="made" href="mailto:lynx-dev@nongnu.org"> + <meta http-equiv="Content-Type" content= + "text/html; charset=us-ascii"> + <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> + <div class="nav"> + <ul> + <li><a href="#overview">Overview</a></li> + + <li><a href="#movement">Movement</a></li> + + <li><a href="#scrolling">Scrolling</a></li> + + <li><a href="#dired">Dired</a></li> + + <li><a href="#other">Other</a></li> + </ul> + </div> + + <h2><a name="overview" id="overview">Overview</a></h2> + + <p><strong>Lynx</strong> recognizes many single-character + commands. This is an overview to their default bindings, with + links to more detailed documentation.</p> + + <h2><a name="movement" href="movement_help.html" id= + "movement">Movement</a></h2> + + <pre> + 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 +</pre> + <h2><a name="scrolling" href="scrolling_help.html" id= + "scrolling">Scrolling</a></h2> + + <pre> + + - 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) + CTRL-A - Go to first page of the current document (Home) + CTRL-E - Go to last page of the current document (End) + CTRL-B - Scroll up to previous page (Page-Up) + CTRL-F - Scroll down to next page (Page-Down) + CTRL-N - Go forward two lines in the current document + CTRL-P - Go back two lines in the current document + ) - Go forward half a page in the current document + ( - Go back half a page in the current document + ^ - Go to the first 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 next link in the current column + # - Go to Toolbar or Banner in the current document +</pre> + <h2><a name="dired" href="dired_help.html" id="dired">Dired</a></h2> + + <pre> + c - Create a new file + d - Download selected file + e - Edit selected file + f - Show a full menu of options for current file + m - Modify the name or location of selected file + r - Remove selected file + t - Tag highlighted file + u - Upload a file into the current directory +</pre> + <h2><a name="other" href="other_help.html" id="other">Other</a></h2> + + <pre> + ? (or h) - Help (this screen) + a - Add the current link to a bookmark file + c - Send a comment to the document owner + d - Download the current link + e - Edit the current file + E - Edit the current link's URL (or ACTION) and + use that as a goto URL. + g - Goto a user specified <a href= +"../lynx_url_support.html">URL</a> or file + G - Edit the current document's URL and use that + as a goto URL. + i - Show an index of documents + j - Execute a jump operation + k - Show list of actual key mappings + l - List references (links) in current document + m - Return to main screen + o - Set your <a href= +"option_help.html">options</a> + p - <a href= +"print_help.html">Print</a> to a file, mail, printers, or other + q - Quit (Capital “Q” for quick quit) + / - Search for a string within the current document + s - Enter a search string for an external search + n - Go to the next search string + N - Go to the previous search string + v - View a <a href= +"bookmark_help.html">bookmark file</a> + V - Go to the <a href= +"visited_help.html">Visited Links Page</a> + x - Force submission of form or link with no-cache + z - Cancel transfer in progress + [backspace] - Go to the <a href= +"history_help.html">History Page</a> + = - Show info about current document, URL and link + \ - Toggle document source/rendered view + ! - Spawn your default shell + ' - Toggle "historical" vs minimal or valid comment + parsing + _ - Clear all authorization info for this session + ` - Toggle minimal or valid comment parsing + * - Toggle image_links mode on and off + @ - Toggle raw 8-bit translations or CJK mode + on or off + . - Run external program on the current link. + , - Run external program on the current document. + { - Shift the screen left. + } - Shift the screen right. + | - Toggle line-wrap mode. When line-wrap is + off, you may use { and } to shift the screen + left/right. The screen width is set to 999. + ~ - Toggle parsing of nested tables (experimental). + [ - Toggle pseudo_inlines mode on and off + ] - Send a HEAD request for the current doc or link + " - Toggle valid or "soft" double-quote parsing + CTRL-R - Reload current file and refresh the screen + CTRL-L - Refresh the screen + CTRL-S - For UNIX hosts: + Copy the URL for the current document or link to + the clipboard using command in $RL_CLCOPY_CMD. as + illustrated in the <a href= +"https://metacpan.org/dist/Term-ReadLine-Perl/source/ReadLine/readline.pm#L4451">clipboard_set</a> function + of the (undated) Perl Term-ReadLine-Perl script. + The clipboard contents can be retrieved using Lynx's + PASTE_URL command (in turn, via $RL_PASTE_CMD). + + CTRL-V - Outside of a text input line or field, + switch to <a href= +"option_help.html#tagsoup">alternative parsing</a> of HTML. + - In a form text input field, + CTRL-V prompts for a key command (allows + <a href= +"../Lynx_users_guide.html#CtrlVNote">escaping</a> from the field). + + Note that on most UNIX hosts, CTRL-V is bound + via stty to the lnext (literal-next) code but + the exact behavior of that is implementation + specific. On Solaris you must type CTRL-V + twice to use it, since it quotes the following + keystroke. + + CTRL-U - Inside text input line or field, + erase input line (<a href= +"edit_help.html">more input line commands</a>) + - Outside of text input or field, + undo returning to previous topic. + + CTRL-G - Cancel input or transfer + + CTRL-T - Toggle trace mode on and off + ; - View the Lynx Trace Log for the current session + CTRL-K - Invoke the <a href= +"cookie_help.html">Cookie Jar Page</a> + CTRL-X - Invoke the <a href= +"../Lynx_users_guide.html#Cache">Cache Jar Page</a> + <em>numbers</em> - Invoke the prompt + <a href= +"follow_help.html">Follow link (or goto link or page) number:</a> + or the + <a href= +"follow_help.html#select-option">Select option (or page) number:</a> + prompt +</pre> +</body> +</html> diff --git a/lynx_help/keystrokes/movement_help.html b/lynx_help/keystrokes/movement_help.html new file mode 100644 index 0000000..1ba648e --- /dev/null +++ b/lynx_help/keystrokes/movement_help.html @@ -0,0 +1,78 @@ +<!-- $LynxId: movement_help.html,v 1.11 2021/07/01 21:02:38 tom Exp $ --> +<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01//EN"> +<html> +<head> + <meta name="generator" content= + "HTML Tidy for HTML5 for Linux version 5.6.0"> + <title>Help on Lynx Movement commands</title> + <link rev="made" href="mailto:lynx-dev@nongnu.org"> + <meta http-equiv="Content-Type" content= + "text/html; charset=us-ascii"> + <meta name="description" content= + "These are the Lynx keystroke-movement commands which are usable in all non-editing contexts, for traversing links."> +</head> +<body> + <div class="nav"> + <ul> + <li><a href="#overview">Overview</a></li> + + <li><a href="#notes">Notes</a></li> + </ul> + </div> + + <h2><a name="overview" id="overview">Overview</a></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 + links on the page to move to. + + Up arrow - Move to the previous hypertext link, + or scroll up if there are no links + above the current one, and there are + previous pages to move to. + + Right arrow, - select the link that the cursor is + Return, Enter positioned on. + + Left arrow - Retreat from a link. Go back to the + previous topic. +</pre> + <h2><a name="notes" id="notes">Notes</a></h2> + + <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> + + <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> + + <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 + \|/ 6 - right arrow + 4 - 5 - 6 5 - nothing + /|\ 4 - left arrow + 1 2 3 3 - page down + 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 new file mode 100644 index 0000000..3138572 --- /dev/null +++ b/lynx_help/keystrokes/option_help.html @@ -0,0 +1,823 @@ +<!-- $LynxId: option_help.html,v 1.34 2021/07/01 21:02:38 tom Exp $ --> +<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01//EN"> +<html> +<head> + <meta name="generator" content= + "HTML Tidy for HTML5 for Linux version 5.6.0"> + <title>Form-based Options Menu : Help</title> + <link rev="made" href="mailto:lynx-dev@nongnu.org"> + <meta http-equiv="Content-Type" content= + "text/html; charset=us-ascii"> + <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> + <h2><a name="overview" id="overview">Options Menu</a></h2> + + <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> + + <div class="nav"> + <ul> + <li><a href="#overview">Options Menu</a></li> + + <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">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> + <a href="#KI">Keyboard Input</a> + <ul> + <li><a href="#KM">Keypad mode</a></li> + + <li><a href="#EM">Emacs keys</a></li> + + <li><a href="#VI">VI keys</a></li> + + <li><a href="#LE">Line edit style</a></li> + </ul> + </li> + + <li> + <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> + + <li><a href="#JK">Raw 8-bit or CJK mode</a></li> + + <li><a href="#DV">X DISPLAY variable</a></li> + </ul> + </li> + + <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> + <a href="#HP">Headers Transferred to Remote Servers</a> + <ul> + <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> + <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> + + <li>Special Files and Screens + <ul> + <li><a href="#MB">Multi-bookmarks</a></li> + + <li><a href="#BF">Bookmark file</a></li> + + <li><a href="#AZ">Auto Session</a></li> + + <li><a href="#SZ">Session file</a></li> + + <li><a href="#VP">Visited Pages</a></li> + </ul> + </li> + </ul> + </div> + + <h2><a name="GP" id="GP">General Preferences</a></h2> + + <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> + + <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 + input field). The full pathname of the editor command should be + specified when possible. It is assumed the text editor supports + the same character set you have for "display character set" in + Lynx.</p> + + <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 insensitive) 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 left-arrow respectively. Otherwise, they remain mapped to + their configured bindings (normally UP_TWO lines, DOWN_TWO lines, + NEXT_PAGE and PREV_PAGE respectively).</p> + + <p>Note: setting emacs keys does not affect the line-editor + bindings.</p> + + <h3><a name="VI" id="VI">VI keys</a></h3> + + <p>If set to “ON” then the lowercase h, j, k and l + keys will be mapped to left-arrow, down-arrow, up-arrow and + right-arrow respectively.</p> + + <p>The uppercase H, J, K, and L keys remain mapped to their + configured bindings (normally HELP, JUMP, KEYMAP and LIST, + respectively).</p> + + <p>Note: setting vi keys does not affect the line-editor + bindings.</p> + + <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> + + <h2><a name="DP" id="DP">Display and Character Set</a></h2> + + <h3><a name="LC" id="LC">Use locale-based character set</a></h3> + + <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> + + <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> + + <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> + + <h3><a name="DV" id="DV">X DISPLAY variable</a></h3> + + <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> + + <ul> + <li>If set to ON or ALWAYS, color mode will be forced on if + possible. If (n)curses color support is available but cannot be + used for the current terminal type, selecting ON is rejected + with a message.</li> + + <li>If set to OFF or NEVER, color mode will be turned off.</li> + + <li>ALWAYS and NEVER are not offered in anonymous accounts. If + saved to a “.lynxrc” file in non-anonymous + accounts, ALWAYS will cause Lynx to set color mode on at + startup if supported.</li> + </ul> + + <p>If Lynx is built with slang, this is equivalent to having + included the -color command line switch or having the COLORTERM + environment variable set. If color support is provided by curses + or ncurses, this is equivalent to the default behavior of using + color when the terminal type supports it. If (n)curses color + support is available but cannot be used for the current terminal + type, the preference can still be saved but will have no + effect.</p> + + <p>A saved value of NEVER will cause Lynx to assume a monochrome + terminal at start-up. It is similar to the -nocolor switch, but + (when the slang library is used) can be overridden with the + -color switch. If the setting is OFF or ON when the current + options are saved to a “.lynxrc” file, the default + start-up behavior is retained, such that color mode will be + turned on at startup only if the terminal info indicates that you + have a color-capable terminal, or (when slang is used) if forced + on via the -color switch or COLORTERM variable. This default + behavior always is used in anonymous accounts, or if the + “option”_save restriction is set explicitly. If for + any reason the start-up color mode is incorrect for your + terminal, set it appropriately on or off via this option.</p> + + <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 + current link or OPTION is indicated solely by its highlighting or + color. If show cursor is set to ON, the cursor will be positioned + at the left of the current link or OPTION. This is helpful when + Lynx is being used with a speech or braille interface. It is also + useful for sighted users when the terminal cannot distinguish the + character attributes used to distinguish the current link or + OPTION from the others in the display.</p> + + <h3><a name="UK" id="UK">Underline links</a></h3> + + <p>Use underline-attribute rather than bold for links.</p> + + <h3><a name="SS" id="SS">Show scrollbar</a></h3> + + <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> + + <h3><a name="PU" id="PU">Pop-ups for select fields</a></h3> + + <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="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 + way for doing this. As a result, there are two parsing modes: + "<dfn>SortaSGML</dfn>" attempts to enforce valid nesting of most + tags at an earlier stage of processing, while + "<dfn>TagSoup</dfn>" relies more on the HTML rendering stage to + mimic the behavior of some other browsers. You can also switch + between these modes with the CTRL-V key, and the default can be + changed in lynx.cfg or with the -tagsoup command line switch.</p> + + <p>The "SortaSGML" mode will often appear to be more strict, and + makes some errors apparent that are otherwise unnoticeable. One + particular difference is the handling of block elements or + <li>..</li> inside <a + HREF="some.url">..</a>. Invalid nesting like this may + turn anchors into hidden links which cannot be easily followed, + this is avoided in "TagSoup" mode. See the <a href= + "follow_help.html">help on following links by number</a> for more + information on hidden links. Often pages may be more readable in + "TagSoup" mode, but sometimes the opposite is true. Most + documents with valid HTML, and documents with only minor errors, + should be rendered the same way in both modes.</p> + + <p>If you are curious about what goes on behind the scenes, but + find that the information from the -trace switch is just too + much, Lynx can be started with the -preparsed switch; going into + SOURCE mode (“\” key) and toggling the parsing mode + (with CTRL-V) should then show some of the differences.</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> + + <pre> + <em>ignore</em> all images which lack an ALT= text string, + <em>show labels</em>, e.g. [INLINE] — see “Verbose Images” below — , + <em>use links</em> for every image, enabling downloading. +</pre> + <p>This option setting cannot be saved between sessions. See + <a href="../Lynx_users_guide.html#Images">Users Guide</a> & + <em>lynx.cfg</em> for more details.</p> + + <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 + be helpful by revealing which images are important & which + are merely decoration, e.g. <em>button.gif</em>, + <em>line.gif</em>. See <a href= + "../Lynx_users_guide.html#Images">Users Guide</a> & + <em>lynx.cfg</em> for more details.</p> + + <h2><a name="HP" id="HP">Headers Transferred to Remote + Servers</a></h2> + + <h3><a name="PM" id="PM">Personal Mail Address</a></h3> + + <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="PN" id="PN">Personal mail name</a></h3> + + <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> + + <h3><a name="PW" id="PW">Password for anonymous ftp</a></h3> + + <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> + + <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> + + <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 <strong>HIGHLY + DANGEROUS</strong>, 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> + + <ul> + <li>When OFF, the default bookmark file is used for the + “v”iew-bookmarks and “a”dd-bookmark + link commands.</li> + + <li>If set to STANDARD, a menu of available bookmarks is always + invoked when you seek to view a bookmark file or add a link, + and you select the bookmark file by its letter token in that + menu.</li> + + <li>If set to ADVANCED, you are instead prompted for the letter + of the desired bookmark file, but can enter “=” to + invoke the STANDARD selection menu, or RETURN for the default + bookmark file.</li> + </ul> + + <h3><a name="BF" id="BF">Bookmark file</a></h3> + + <p>Manage the default bookmark file:</p> + + <ul> + <li>If non-empty and multi-bookmarks is OFF, it specifies your + default “<a href="bookmark_help.html">Bookmark + file</a>”.</li> + + <li>If multi-bookmarks is STANDARD or ADVANCED, entering + “B” will invoke a menu in which you can specify + filepaths and descriptions of up to 26 bookmark files.</li> + </ul> + + <p>The filepaths must be from your home directory and begin with + “./” if subdirectories are included (e.g., + “./BM/lynx_bookmarks.html”).</p> + + <p>Lynx will create bookmark files when you first + “a”dd a link, but any subdirectories in the filepath + must already exist.</p> + + <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 + list, in reverse order of the pages visited. The popup menu + allows you these choices:</p> + + <dl> + <dt><em>By First Visit</em>: The default appearance, shows the + pages based on when they were first visited. The list is shown + in reverse order, to make the current page (usually) at the top + of the list.</dt> + + <dt><em>By First Visit Reversed</em> The default appearance, + shows the pages based on when they were first visited. The list + is shown in order, to make the current page (usually) at the + bottom of the list.</dt> + + <dt><em>As Visit Tree</em> Combines the first/last visited + information, showing the list in order of the first visit, but + using the indentation level of the page immediately previous to + determine indentation of new entries. That gives a clue to the + order of visiting pages when moving around in the History or + Visited Pages lists.</dt> + + <dt><em>By Last Visit</em> The default appearance, shows the + pages based on when they were last visited. The list is shown + in reverse order, to make the current page (usually) at the top + of the list.</dt> + + <dt><em>By Last Visit Reversed</em> The default appearance, + shows the pages based on when they were last visited. The list + is shown in order, to make the current page (usually) at the + bottom of the list.</dt> + </dl> +</body> +</html> diff --git a/lynx_help/keystrokes/other_help.html b/lynx_help/keystrokes/other_help.html new file mode 100644 index 0000000..8202bd3 --- /dev/null +++ b/lynx_help/keystrokes/other_help.html @@ -0,0 +1,196 @@ +<!-- $LynxId: other_help.html,v 1.19 2021/07/01 21:02:38 tom Exp $ --> +<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01//EN"> +<html> +<head> + <meta name="generator" content= + "HTML Tidy for HTML5 for Linux version 5.6.0"> + <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"> + <meta name="description" content= + "This is a table listing with brief descriptions miscellaneous Lynx commands, along with links to related topics"> +</head> +<body> + <div class="nav"> + <ul> + <li><a href="#command_list">Summary of Commands</a></li> + </ul> + </div> + + <h2><a name="command_list" id="command_list">Summary of + Commands</a></h2> + + <pre> + a - Places the link that you are currently positioned + on into a personal <a href= +"bookmark_help.html">bookmark file</a>. + + c - Allows you to send a mail message to the owner + or maintainer of the data that you are currently + viewing. In the case that no owner is known, + you cannot send a comment. + + d - Downloads the file pointed to by the current link + and displays an option menu allowing the file to + be saved or transferred by configurable options. + Can also be used when positioned on a form SUBMIT + button to download the reply to a form submission. + + e - Allows you to edit the current document if it is a + local file. + + E - Allows you to edit the current link's URL (or ACTION) and + use that as a <em>goto</em> URL. + + g - Allows you to enter any <a href= +"http://www.ietf.org/rfc/rfc1738.txt">URL</a> or filename that + you wish to view, and then <em>goto</em> it. + + G - Allows you to edit the current document's URL and use that + as a <em>goto</em> URL. + + ? or H - Hypertext help to explain how to navigate in + <strong>Lynx</strong> and use its features. + + i - Shows an index of files or subjects, + which may be changed in <em>lynx.cfg</em>. + + j - Allows you to enter a short name to goto an URL, + if a jumps file has been defined. Press "?" + and ENTER to see the list of defined jump commands. + + k - Shows a list of key mappings. Keys remapped in + "lynx.cfg" show up in this list. + + l - Brings up a list of references (links) in the current + document, which can be used for rapid access to the + links in large documents. + + m - Returns to the first screen and empties the + history stack. + + p - Brings up a list of <a href= +"print_help.html">print commands</a>. + + o - Brings up a list of settable <a href= +"option_help.html">options</a>. + + q - Quits <strong>Lynx</strong>. (“Q” quits without asking) + + / - Search for a string of characters in the current document + (case insensitive or case sensitive + depending on the <a href= +"option_help.html">options</a> set). + + s - Search through an external searchable indexed document. + + n - Move to the next instance of a search string if you + have searched previously. + + v - View a <a href= +"bookmark_help.html">Bookmark file</a>. + + V - Go to the <a href= +"visited_help.html">Visited Links Page</a> + + x - Force submission of form or link with no-cache. + + z - Abort a network transfer in progress. If any partial + data has been transferred it will be displayed. + + <backspace> - displays the <a href= +"history_help.html">History Page</a>. + + = - Show information about the file and link that you + are currently viewing. + + \ - Toggles between viewing the HTML source of a + document and the rendered version of the document. + + ! - Spawns your default operating system shell. + + ' - Toggles "historical" vs minimal or valid comment parsing. + When historical, any close-angle-bracket will be treated + as a comment terminator, emulating the parsing bug in old + versions of Mosaic and Netscape, rather than validly + requiring pairs of two successive dashes to delimit + comments within the angle-brackets. + + _ - Clears all authorization info for the current session. Can + 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 + can still be accessed. + + ` - Toggles minimal or valid comment parsing. When minimal, any + two successive dashes followed by a close-angle-bracket will + be treated as a comment terminator, emulating the parsing bug + in Netscape v2.0. If historical comment parsing is set, that + will override minimal or valid comment parsing. + + * - Toggles image_links mode on and off. When on, links will + be created for all images, including inlines. + + @ - Toggles raw 8-bit translations or CJK mode on and off, only + 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 <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 <strong>Lynx</strong> display. + When off, they will be treated as having ALT="" (i.e., + they will be ignored). If image_links mode is toggled on, + the pseudo-ALT strings will be restored, to serve as links + to the inline images' sources. + + ] - Sends a HEAD request for the current document or link. It + 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., <strong>Lynx</strong> + does not retrieve any previous server replies from its + cache. Note that for form submissions, http servers vary + in whether they will treat HEAD requests as valid and return + the CGI script's headers, or treat it as invalid and return + an error message. + + " - Toggles valid or "soft" double-quote parsing. When soft, + a close-angle-bracket will serve as both a close-double- + quote and close-tag, emulating the parsing bug in old + versions of Mosaic and Netscape. + + CTRL-R - Reloads the current document and resets the display. + + CTRL-V - Switches to an alternative way of parsing HTML documents. + This may help to get a more readable rendering of some + documents with invalidly placed HTML tags, <a href= +"option_help.html#tagsoup">more details</a>. + + CTRL-W - Resets or cleans up the display. + + CTRL-U - Clears text from an input field or prompt. + + CTRL-G - Cancels any input prompt, mail message or data transfer. + + CTRL-T - Toggles trace mode on and off. + + ; - Views the <em>Lynx Trace Log</em> for the current session. + + CTRL-K - Invokes the Cookie Jar Page. + + 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 + <a href= +"follow_help.html#select-option">Select option (or page) number:</a> + prompts. +</pre> +</body> +</html> diff --git a/lynx_help/keystrokes/print_help.html b/lynx_help/keystrokes/print_help.html new file mode 100644 index 0000000..fb7738e --- /dev/null +++ b/lynx_help/keystrokes/print_help.html @@ -0,0 +1,62 @@ +<!-- $LynxId: print_help.html,v 1.10 2021/07/01 21:02:38 tom Exp $ --> +<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01//EN"> +<html> +<head> + <meta name="generator" content= + "HTML Tidy for HTML5 for Linux version 5.6.0"> + <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"> + <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> + <div class="nav"> + <ul> + <li><a href="#overview">Overview</a></li> + + <li><a href="#command_options">Print-command Options</a></li> + </ul> + </div> + + <h2><a name="overview" id="overview">Overview</a></h2> + + <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><a name="command_options" id="command_options">Print-command + Options</a></h2> + + <p>The following print options may be available:</p> + + <dl> + <dt>Print to a local file:</dt> + + <dd>This allows you to save the current file as ASCII text to + your local disk. You will be asked for a path and filename to + save the file to. If no path is given, the file will be saved + to the directory that you were in when you began + <strong>Lynx</strong>.</dd> + + <dt>Print to the screen:</dt> + + <dd>This option simply scrolls the entire document up the + screen and is intended for those who wish to capture the + document with their terminal.</dd> + + <dt>Mail the file to yourself:</dt> + + <dd>This option allows you to mail the file, in ASCII form, to + any valid e-mail address.</dd> + + <dt>Custom print options:</dt> + + <dd>Any number of custom print options may be defined in + <em>lynx.cfg</em>.</dd> + </dl> +</body> +</html> diff --git a/lynx_help/keystrokes/scrolling_help.html b/lynx_help/keystrokes/scrolling_help.html new file mode 100644 index 0000000..b6f086b --- /dev/null +++ b/lynx_help/keystrokes/scrolling_help.html @@ -0,0 +1,117 @@ +<!-- $LynxId: scrolling_help.html,v 1.13 2021/07/01 21:02:38 tom Exp $ --> +<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01//EN"> +<html> +<head> + <meta name="generator" content= + "HTML Tidy for HTML5 for Linux version 5.6.0"> + <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"> + <meta name="description" content= + "This gives an overview and some details on Lynx's scrolling/paging commands. A diagram shows keypad shortcuts."> +</head> +<body> + <div class="nav"> + <ul> + <li><a href="#overview">Overview</a></li> + + <li><a href="#paging_keys">Paging shortcuts</a></li> + + <li><a href="#keypad_keys">Keypad shortcuts</a></li> + + <li><a href="#control_keys">Control-characters</a></li> + + <li><a href="#other_keys">Ordinary characters</a></li> + </ul> + </div> + + <h2><a name="overview" id="overview">Overview</a></h2> + + <p>This gives an overview and some details on Lynx's + scrolling/paging commands. A diagram shows keypad shortcuts.</p> + + <h2><a name="paging_keys" id="paging_keys">Paging shortcuts</a></h2> + + <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). + + - (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><a name="keypad_keys" id="keypad_keys">Keypad shortcuts</a></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 + \|/ 6 - right arrow + 4 - 5 - 6 5 - nothing + /|\ 4 - left arrow + 1 2 3 3 - page down + 2 - down arrow + 1 - moves to the end of a document +</pre> + </blockquote> + + <h2><a name="control_keys" id= + "control_keys">Control-characters</a></h2> + + <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-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> + + <h2><a name="other_keys" id="other_keys">Ordinary characters</a></h2> + + <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). + + ^ - Go to the first 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 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. +</pre> + </blockquote> +</body> +</html> diff --git a/lynx_help/keystrokes/test_display.html b/lynx_help/keystrokes/test_display.html new file mode 100644 index 0000000..adbe3ef --- /dev/null +++ b/lynx_help/keystrokes/test_display.html @@ -0,0 +1,82 @@ +<!-- $LynxId: test_display.html,v 1.12 2021/07/01 21:02:38 tom Exp $ --> +<!-- do not use tidy for this page --> +<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01//EN"> +<html> +<head> + <meta name="generator" content= + "HTML Tidy for HTML5 for Linux version 5.6.0"> + <title>Quick test for identifying display character set</title> + <link rev="made" href="mailto:lynx-dev@nongnu.org"> + <meta http-equiv="Content-Type" content= + "text/html; charset=us-ascii"> + <meta name="description" content= + "Display a test-page for common problems with Lynx's display character set and/or locale problems."> +</head> +<body> + <div class="nav"> + <ul> + <li><a href="#overview">Overview</a></li> + + <li><a href="#configuration">Configuration</a></li> + + <li><a href="#test_screen">Test-screen</a></li> + </ul> + </div> + + <h2><a name="overview" id="overview">Overview</a></h2> + + <p>Display a test-page for common problems with Lynx's display + character set and/or locale problems.</p> + + <h2><a name="configuration" id="configuration">Configuration</a></h2> + + <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> + + <h2><a name="test_screen" id="test_screen">Test-screen</a></h2> + + <p>This is only a quick test to see obvious problems.</p> + + <pre> + +0x00A9 © # COPYRIGHT SIGN + +0x00C7 Ç # LATIN CAPITAL LETTER C WITH CEDILLA + +0x00DC Ü # LATIN CAPITAL LETTER U WITH DIAERESIS + +0x00D1 Ñ # LATIN CAPITAL LETTER N WITH TILDE + +0x0107 ć # LATIN SMALL LETTER C WITH ACUTE +0x0108 Ĉ # LATIN CAPITAL LETTER C WITH CIRCUMFLEX +0x010C Č # LATIN CAPITAL LETTER C WITH CARON + +0x03BB λ # GREEK SMALL LETTER LAMDA + +0x041B Л # CYRILLIC CAPITAL LETTER EL +0x042E Ю # CYRILLIC CAPITAL LETTER YU +0x043B л # CYRILLIC SMALL LETTER EL +0x044E ю # CYRILLIC SMALL LETTER YU + +0x2026 … # HORIZONTAL ELLIPSIS +0x2122 ™ # TRADE MARK SIGN + +0x255D ╝ # BOX DRAWINGS DOUBLE UP AND LEFT +0x255E ╞ # BOX DRAWINGS VERTICAL SINGLE AND RIGHT DOUBLE + +0xFB01 fi # LATIN SMALL LIGATURE FI +</pre> +</body> +</html> diff --git a/lynx_help/keystrokes/visited_help.html b/lynx_help/keystrokes/visited_help.html new file mode 100644 index 0000000..14a83c1 --- /dev/null +++ b/lynx_help/keystrokes/visited_help.html @@ -0,0 +1,63 @@ +<!-- $LynxId: visited_help.html,v 1.12 2021/07/01 21:02:38 tom Exp $ --> +<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01//EN"> +<html> +<head> + <meta name="generator" content= + "HTML Tidy for HTML5 for Linux version 5.6.0"> + <title>Help on the Visited Links Page</title> + <link rev="made" href="mailto:lynx-dev@nongnu.org"> + <meta http-equiv="Content-Type" content= + "text/html; charset=us-ascii"> + <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> + <div class="nav"> + <ul> + <li><a href="#overview">Overview</a></li> + + <li><a href="#navigation">Navigation</a></li> + + <li><a href="#configuration">Configuration</a></li> + </ul> + </div> + + <h2><a name="overview" id="overview">Overview</a></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><a name="navigation" id="navigation">Navigation</a></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 + previously visited, or you can use this list to save such links + in your <a href="bookmark_help.html">bookmark files</a>, or to + <a href="../Lynx_users_guide.html#RemoteSource">Download</a> + them.</p> + + <p>In contrast to the History Page, the Visited Links Page + includes any links which were retrieved for + “<em>d</em>”ownloading or were passed to helper + applications, i.e., not just the links that were rendered and + displayed by Lynx, itself.</p> + + <h2><a name="configuration" id="configuration">Configuration</a></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>). 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 new file mode 100644 index 0000000..84ac3df --- /dev/null +++ b/lynx_help/keystrokes/xterm_help.html @@ -0,0 +1,52 @@ +<!-- $LynxId: xterm_help.html,v 1.11 2021/07/01 21:02:38 tom Exp $ --> +<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01//EN"> +<html> +<head> + <meta name="generator" content= + "HTML Tidy for HTML5 for Linux version 5.6.0"> + <title>X Terminal Help</title> + <link rev="made" href="mailto:lynx-dev@nongnu.org"> + <meta http-equiv="Content-Type" content= + "text/html; charset=us-ascii"> + <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> + <div class="nav"> + <ul> + <li>X Terminal Help</li> + + <li>Notes</li> + </ul> + </div> + + <h2>X Terminal Help</h2> + + <p>An X terminal is an electronic display terminal that + communicates with a host computer system using the X Window + protocol developed at the Massachusetts Institute of + Technology.</p> + + <p>The X Window protocol allows a program running on the host + computer system to display both formatted text and graphics on + the X terminal. Since the X Window protocol is defined to work + over any TCP/IP network, X terminals connected to the Internet + can be connected to hosts located anywhere on the Internet.</p> + + <p>Personal computers (including both PCs and Macintoshes) can + execute programs, usually called X servers, that make them act + like X Window terminals and are frequently used as X + terminals.</p> + + <h2>Notes</h2> + + <dl> + <dt>Terminology</dt> + + <dd>The terminology used to describe processes associated with + X terminals can be confusing. An X terminal is also known as an + "X display server," and the program running on the host + computer is usually known as the "X client."</dd> + </dl> +</body> +</html> |