diff options
| author | Thomas E. Dickey <dickey@invisible-island.net> | 2017-04-28 22:16:55 +0000 |
|---|---|---|
| committer | Thomas E. Dickey <dickey@invisible-island.net> | 2017-04-28 22:16:55 +0000 |
| commit | 5ae317fdbe6eed531e4eba65faaa6e33050e19c2 (patch) | |
| tree | 9bd6162c49f69375b6555712f2692c6ab18b011f | |
| parent | b694a6d466c2c4f2f3b2fb48945e488b6bd79fc8 (diff) | |
| download | lynx-snapshots-5ae317fdbe6eed531e4eba65faaa6e33050e19c2.tar.gz | |
snapshot of project "lynx", label v2-8-9dev_11q
24 files changed, 1353 insertions, 1002 deletions
diff --git a/CHANGES b/CHANGES index e683813e..713a0717 100644 --- a/CHANGES +++ b/CHANGES @@ -1,9 +1,13 @@ --- $LynxId: CHANGES,v 1.884 2017/04/27 22:45:53 tom Exp $ +-- $LynxId: CHANGES,v 1.886 2017/04/28 20:10:44 tom Exp $ =============================================================================== Changes since Lynx 2.8 release =============================================================================== 2017-04-28 (2.8.9dev.12) +* improve manual page discussion of environment variables, prompted by + comments in Debian #791452, which overlooked the fact that details of proxy + behavior are found in the user guide -TD +* cleanup some of the user's guide formatting, e.g., for quote-characters -TD * consistently use "_" in command-line options table and manual page, to work with program logic that treats "-" as "_", but not the reverse (report by Larry Hines) -TD diff --git a/lynx.man b/lynx.man index b4ada44f..d5feb3d1 100644 --- a/lynx.man +++ b/lynx.man @@ -1,4 +1,4 @@ -.\" $LynxId: lynx.man,v 1.116 2017/04/27 23:12:12 tom Exp $ +.\" $LynxId: lynx.man,v 1.117 2017/04/28 01:19:42 tom Exp $ .\" ************************************************************************** .\" Escape single quotes in literal strings from groff's Unicode transform. .ie \n(.g .ds AQ \(aq @@ -1074,8 +1074,30 @@ servers (see WWW_access_GATEWAY, below). .IP Each protocol used by \fILynx\fR, (http, ftp, gopher, etc), can be mapped separately by setting environment -variables of the form \fIPROTOCOL\fP_proxy (literally: http_proxy, ftp_proxy, -gopher_proxy, etc), to \*(``http://some.server.dom:port/\*(''. +variables of the form \fIPROTOCOL\fP_proxy. +Protocols are indicated in a URI by the name before \*(``:\*('', e.g., +\*(``http\*('' in +\*(``http://some.server.dom:port/\*('' for HTML. +.IP +Depending on your system configuration and supported protocols, +the environment variables recognized by \fIlynx\fP may include +.NS +cso_proxy +finger_proxy +ftp_proxy +gopher_proxy +https_proxy +http_proxy +newspost_proxy +newsreply_proxy +news_proxy +nntp_proxy +no_proxy +snewspost_proxy +snewsreply_proxy +snews_proxy +wais_proxy +.NE .IP See \fBLynx Users Guide\fR for additional details and examples. .TP @@ -1085,9 +1107,10 @@ Set to the directory containing trusted certificates. .B SSL_CERT_FILE Set to the full path and filename for your file of trusted certificates. .TP -.B WWW_access_GATEWAY +.B WWW_\fIaccess\fB_GATEWAY \fILynx\fR still supports use of gateway servers, with the servers specified -via \*(``WWW_access_GATEWAY\*('' variables (where \*(``access\*('' is lower case and can be +via \*(``WWW_\fIaccess\fP_GATEWAY\*('' variables +(where \*(``\fIaccess\fP\*('' 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 diff --git a/lynx_help/Lynx_users_guide.html b/lynx_help/Lynx_users_guide.html index 338894b3..c6cb8cb9 100644 --- a/lynx_help/Lynx_users_guide.html +++ b/lynx_help/Lynx_users_guide.html @@ -1,4 +1,4 @@ -<!-- $LynxId: Lynx_users_guide.html,v 1.128 2015/12/18 10:24:31 tom Exp $ --> +<!-- $LynxId: Lynx_users_guide.html,v 1.130 2017/04/28 16:42:13 tom Exp $ --> <!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01//EN"> <html> @@ -161,19 +161,20 @@ help</a></h2> <p>Online help is available while viewing any document. Press the - '<em>?</em>' or '<em>H</em>' key (or the '<em>h</em>' key if - vi-like key movement is not on) to see a list of help topics. See - the section titled <a href="#IntraDocNav">Navigating hypertext - documents with Lynx</a> for information on navigating through the - help files.</p> + “<em>?</em>” or “<em>H</em>” key (or the + “<em>h</em>” key if vi-like key movement is not on) + to see a list of help topics. See the section titled <a href= + "#IntraDocNav">Navigating hypertext documents with Lynx</a> for + information on navigating through the help files.</p> <p>In addition, a summary description of all the Lynx keystroke commands and their key bindings is available by pressing the - '<em>K</em>' key (or the '<em>k</em>' key if vi-like key movement - is not on).</p> + “<em>K</em>” key (or the “<em>k</em>” key + if vi-like key movement is not on).</p> <p>If you want to recall recent status-line messages, you can do - so by entering the `g' command, followed by `LYNXMESSAGES:'.</p> + so by entering the “g” command, followed by + “LYNXMESSAGES:”.</p> <p>[<a href="#ToC-Help">ToC</a>]</p> @@ -261,19 +262,20 @@ file) for initial display and should you select the link again. If you do select a link again and have reason to desire a new fetch and rendering of the file, use the NOCACHE command, - normally mapped to '<em>x</em>' and '<em>X</em>', instead of the - <em>right-arrow</em> or <em>Return</em> key when positioned on - the link. You also can force a new fetch and rendering of the - currently displayed document via the RELOAD command, normally - mapped to <em>Control-R</em>.</p> + normally mapped to “<em>x</em>” and + “<em>X</em>”, instead of the <em>right-arrow</em> or + <em>Return</em> key when positioned on the link. You also can + force a new fetch and rendering of the currently displayed + document via the RELOAD command, normally mapped to + <em>Control-R</em>.</p> <p>When a binary file is encountered Lynx will ask the user if he/she wishes to download the file or cancel. If the user selects - '<em>D'</em> for download, Lynx will transfer the file into a - temporary location and present the user with a list of options. - The only default option is <em>Save to disk</em>, which is - disabled if Lynx is running in anonymous mode. Additional - download methods may be defined in the <a href= + “<em>D</em>” for download, Lynx will transfer the + file into a temporary location and present the user with a list + of options. The only default option is <em>Save to disk</em>, + which is disabled if Lynx is running in anonymous mode. + Additional download methods may be defined in the <a href= "#lynx.cfg">lynx.cfg</a> file. Programs like kermit, zmodem and FTP are some possible options.</p> @@ -282,10 +284,11 @@ <h2 id="id-Leaving"><a name="Leaving" id="Leaving">Leaving Lynx</a></h2> - <p>To exit Lynx use the '<em>q</em>' command. You will be asked - whether you really want to quit. Answering '<em>y</em>' will exit - and '<em>n</em>' will return you to the current document. Use - '<em>Q</em>' or <em>Control-D</em> to quit without + <p>To exit Lynx use the “<em>q</em>” command. You + will be asked whether you really want to quit. Answering + “<em>y</em>” will exit and “<em>n</em>” + will return you to the current document. Use + “<em>Q</em>” or <em>Control-D</em> to quit without verification.</p> <p>[<a href="#ToC-Leaving">ToC</a>]</p> @@ -438,20 +441,22 @@ links leading to your access of the current document. Any of the previous documents shown in the list may be revisited by selecting them from the history screen. The VLINKS keystroke - command, normally mapped to uppercase '<em>V</em>', will show the - <em>Visited Links Page</em>, and you similarly can select links - in that list. The MAIN_MENU keystroke command, normally mapped to - '<em>m</em>' and '<em>M</em>', will take you back to the starting + command, normally mapped to uppercase “<em>V</em>”, + will show the <em>Visited Links Page</em>, and you similarly can + select links in that list. The MAIN_MENU keystroke command, + normally mapped to “<em>m</em>” and + “<em>M</em>”, will take you back to the starting document unless you specified the <em>-homepage=URL</em> option at the command line. Also, the LIST and ADDRLIST keystroke - commands, normally mapped to '<em>l</em>' and <em>A</em>' - respectively, will create a compact lists of all the links in the - current document, and they can be selected via those lists.</p> + commands, normally mapped to “<em>l</em>” and + “<em>A</em>” respectively, will create a compact + lists of all the links in the current document, and they can be + selected via those lists.</p> - <p>The '<em>i</em>' key presents an index of documents. The - default index offered contains many useful links, but can be - changed in <em>lynx.cfg</em> or on the command line using the - <em>-index=URL</em> switch.</p> + <p>The “<em>i</em>” key presents an index of + documents. The default index offered contains many useful links, + but can be changed in <em>lynx.cfg</em> or on the command line + using the <em>-index=URL</em> switch.</p> <p>If you choose a link to a server with active access authorization, Lynx will automatically prompt for a username and @@ -467,17 +472,17 @@ disk.</a></h2> <p>Rendered HTML documents, and plain text files, may be printed - using the '<em>p</em>' command while viewing the document. After - pressing the '<em>p</em>' key a menu of <em>Print Options</em> - will be displayed. The menu will vary according to several - factors. First, some sites set up special accounts to let users - run Lynx to access local information systems. Typically these - accounts require no passwords and do not require users to - identify themselves. As a result such accounts are called - "anonymous" accounts, and their users are considered "anonymous" - users. In most configurations, all Lynx users (including - anonymous users) are able to mail files to themselves and print - the entire file to the screen.</p> + using the “<em>p</em>” command while viewing the + document. After pressing the “<em>p</em>” key a menu + of <em>Print Options</em> will be displayed. The menu will vary + according to several factors. First, some sites set up special + accounts to let users run Lynx to access local information + systems. Typically these accounts require no passwords and do not + require users to identify themselves. As a result such accounts + are called "anonymous" accounts, and their users are considered + "anonymous" users. In most configurations, all Lynx users + (including anonymous users) are able to mail files to themselves + and print the entire file to the screen.</p> <p>Additional print options are available for users who are using Lynx from their own accounts (that is, so-called "non-anonymous @@ -504,10 +509,10 @@ <p>When viewing HTML documents it is possible to retrieve and display the unrendered (i.e., the original HTML) source of the - document by pressing the '<em>\</em>' (backslash) key. Lynx - usually caches only the rendering of the document and doesn't - keep the source (unless it is configured to do so in the <a href= - "#lynx.cfg">lynx.cfg</a> file), so to display the source + document by pressing the “<em>\</em>” (backslash) + key. Lynx usually caches only the rendering of the document and + does not keep the source (unless it is configured to do so in the + <a href="#lynx.cfg">lynx.cfg</a> file), so to display the source unrendered, Lynx must reload it from the server or disk. When viewing unrendered documents you may print them as any normal document.</p> @@ -538,23 +543,25 @@ <p>In addition, the user must also specify an editor in the <em>Options Menu</em> so that Lynx knows which editor to use. If the file is specified correctly and an editor is defined, then - you may edit documents by using the '<em>e</em>' command. When - the '<em>e</em>' command is entered your specified editor is - spawned to edit the file. After changes are completed, exit your - editor and you will return to Lynx. Lynx will reload and render - the file so that changes can be immediately examined.</p> + you may edit documents by using the “<em>e</em>” + command. When the “<em>e</em>” command is entered + your specified editor is spawned to edit the file. After changes + are completed, exit your editor and you will return to Lynx. Lynx + will reload and render the file so that changes can be + immediately examined.</p> <p>[<a href="#ToC-LocalSource">ToC</a>]</p> <h2 id="id-RemoteSource"><a name="RemoteSource" id= "RemoteSource">Downloading and Saving source files.</a></h2> - <p>If the DOWNLOAD keystroke command ('<em>d</em>' or <em>D</em>) - is used when positioned on a link for an HTML, plain text, or - binary file, Lynx will transfer the file, without rendering, into - a temporary location and present the user with a list of options, - just as it does when a link for a binary file of a type for which - no viewer has been mapped is activated.</p> + <p>If the DOWNLOAD keystroke command (“<em>d</em>” or + “<em>D</em>”) is used when positioned on a link for + an HTML, plain text, or binary file, Lynx will transfer the file, + without rendering, into a temporary location and present the user + with a list of options, just as it does when a link for a binary + file of a type for which no viewer has been mapped is + activated.</p> <p>There is a default <em>Download option</em> of <em>Save to disk</em>. This is disabled if Lynx is running in anonymous mode. @@ -595,39 +602,39 @@ or wipe the screen to remove or correct any errors that may be caused by operating system or other messages.</p> - <p>The NOCACHE ('<em>x</em>' or '<em>X</em>') command can be used - in lieu of ACTIVATE (<em>Return</em> or <em>right-arrow</em>) to - request an uncached copy and new rendition for the current link, - or resubmission of a FORM, if a cache from a previous request or - submission exits. The request or submission will include - <em>Pragma: no-cache</em> and <em>Cache-Control: no-cache</em> in - its headers. Note that FORMs with POST content will be - resubmitted regardless of whether the NOCACHE or ACTIVATE command - is used (see <a href="#Forms"><em>Lynx and HTML - Forms</em></a>).</p> + <p>The NOCACHE (“<em>x</em>” or + “<em>X</em>”) command can be used in lieu of ACTIVATE + (<em>Return</em> or <em>right-arrow</em>) to request an uncached + copy and new rendition for the current link, or resubmission of a + FORM, if a cache from a previous request or submission exits. The + request or submission will include <em>Pragma: no-cache</em> and + <em>Cache-Control: no-cache</em> in its headers. Note that FORMs + with POST content will be resubmitted regardless of whether the + NOCACHE or ACTIVATE command is used (see <a href= + "#Forms"><em>Lynx and HTML Forms</em></a>).</p> <p>[<a href="#ToC-ReDo">ToC</a>]</p> <h2 id="id-Search"><a name="Search" id="Search">Lynx searching commands</a></h2> - <p>Two commands activate searching in Lynx: '<em>/</em>' and - '<em>s</em>'.</p> + <p>Two commands activate searching in Lynx: + “<em>/</em>” and “<em>s</em>”.</p> - <p>While viewing a normal document use the '<em>/</em>' command - to find a word or phrase within the current document. The search - type will depend on the search option setting in the <a href= - "#InteractiveOptions">Options Menu</a>. The search options are - case sensitive and case insensitive. These searches are entirely - local to Lynx.</p> + <p>While viewing a normal document use the + “<em>/</em>” command to find a word or phrase within + the current document. The search type will depend on the search + option setting in the <a href="#InteractiveOptions">Options + Menu</a>. The search options are case sensitive and case + insensitive. These searches are entirely local to Lynx.</p> <p>Some documents are designated <em>index documents</em> by virtue of an ISINDEX element in their HEAD section. These documents can be used to retrieve additional information based on searches using words or phrases submitted to an index server. The Lynx statusline will indicate that you are viewing such a - document, and if so, the '<em>s</em>' key will invoke a - statusline prompt to enter a query string. The prompt can be + document, and if so, the “<em>s</em>” key will invoke + a statusline prompt to enter a query string. The prompt can be specified via a PROMPT attribute in the ISINDEX element. Otherwise, Lynx will use an internally configured prompt. The address for submitting the search can be specified via an HREF or @@ -639,11 +646,11 @@ Lynx session are saved in a circular buffer, and can be retrieved for re-use by pressing the <em>up-arrow</em> or <em>down-arrow</em> keys at the prompt for a search word or - string. Also, you can use the '<em>n</em>'ext command to repeat a - search with the last-entered search word or phrase, starting from - the current position in the document. The word or phrase matches - will be highlighted throughout the document, but such - highlighting will not persist for new documents, or if the + string. Also, you can use the “<em>n</em>”ext command + to repeat a search with the last-entered search word or phrase, + starting from the current position in the document. The word or + phrase matches will be highlighted throughout the document, but + such highlighting will not persist for new documents, or if the current document is reloaded. The search cycles to the top of the document if the word or phrase is not located below your current position.</p> @@ -670,9 +677,9 @@ "InteractiveOptions">Lynx Options Menu</a></h2> <p>The Lynx <em>Options Menu</em> may be accessed by pressing the - '<em>o</em>' key. It allows you to change options at runtime, if - you need to. Most changes are read from & saved to your - .lynxrc file; those which are not are marked (!) in the + “<em>o</em>” key. It allows you to change options at + runtime, if you need to. Most changes are read from & saved + to your .lynxrc file; those which are not are marked (!) in the form-based menu (as below). Many other options are stored in the <a href="#lynx.cfg">lynx.cfg</a> file.</p> @@ -789,9 +796,9 @@ <p>An option can be changed by entering the capital letter or character in parentheses for the option you wish to change (e.g., - '<em>E</em>' for Editor or '<em>@</em>' for show cursor). For - fields where text must be entered, simply enter the text by - typing on the keyboard. The <a href= + “<em>E</em>” for Editor or “<em>@</em>” + for show cursor). For fields where text must be entered, simply + enter the text by typing on the keyboard. The <a href= "keystrokes/edit_help.html">Line Editor</a> can be used to correct mistakes, and <em>Control-U</em> can be used to erase the line. When you are done entering a change press the @@ -811,9 +818,10 @@ the choices, then press the <em>Return</em> key to finish the change.</p> - <p>When you are done changing options use the '<em>r</em>' - command to return to Lynx or the '<em>></em>' command to save - the options to a <em>.lynxrc</em> file and return to Lynx.</p> + <p>When you are done changing options use the + “<em>r</em>” command to return to Lynx or the + “<em>></em>” command to save the options to a + <em>.lynxrc</em> file and return to Lynx.</p> <p>The following table describes the options available on the <em>Options Menu</em>:</p> @@ -830,8 +838,8 @@ broken pages if you know by some means 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. This option active when 'Raw 8-bit or CJK - Mode' is OFF.</dd> + encoded accordingly. This option active when “Raw 8-bit + or CJK Mode” is OFF.</dd> <dt>Auto Session</dt> @@ -872,31 +880,32 @@ <dd> When multi-bookmarks is OFF, this is the filename and location of your default personal bookmark file. Enter - '<em>B</em>' to modify the filename and/or location via the - <a href="keystrokes/edit_help.html">Line Editor</a>. Bookmark - files allow frequently traveled links to be stored in - personal easy to access files. - - <p>Using the '<em>a</em>'dd bookmark link command (see - <a href="#Bookmarks">Lynx bookmarks</a>) you may save any - link that does not have associated POST content into a + “<em>B</em>” to modify the filename and/or + location via the <a href="keystrokes/edit_help.html">Line + Editor</a>. Bookmark files allow frequently traveled links to + be stored in personal easy to access files. + + <p>Using the “<em>a</em>”dd bookmark link command + (see <a href="#Bookmarks">Lynx bookmarks</a>) you may save + any link that does not have associated POST content into a bookmark file. All bookmark files must be in or under your account's home directory. If the location specified does not begin with a dot-slash (./), its presence will still be assumed, and referenced to the home directory.</p> <p>When multi-bookmarks is STANDARD or ADVANCED, entering - '<em>B</em>' will invoke a menu of up to 26 bookmark files - (associated with the letters of the English alphabet), for - editing their filenames and locations (<em>filepath</em>), - and descriptions.</p> - - <p>Lynx will create bookmark files, if they don't already - exist, when you first '<em>a</em>'dd a bookmark link to them. - However, if you've specified a subdirectory (e.g., - ./BM/lynx_bookmarks.html), that subdirectory must already - exist. Note that on VMS you should use the URL syntax for the - filepath (e.g., <em>not</em> [.BM]lynx_bookmarks.html).</p> + “<em>B</em>” will invoke a menu of up to 26 + bookmark files (associated with the letters of the English + alphabet), for editing their filenames and locations + (<em>filepath</em>), and descriptions.</p> + + <p>Lynx will create bookmark files, if they do not already + exist, when you first “<em>a</em>”dd a bookmark + link to them. However, if you've specified a subdirectory + (e.g., ./BM/lynx_bookmarks.html), that subdirectory must + already exist. Note that on VMS you should use the URL syntax + for the filepath (e.g., <em>not</em> + [.BM]lynx_bookmarks.html).</p> </dd> <dt>Cookies</dt> @@ -1076,7 +1085,7 @@ <dt>By type</dt> <dd>by filename suffix, e.g., the text beginning with - '.'</dd> + “.”</dd> <dt>By user</dt> @@ -1092,17 +1101,18 @@ <dd>Lynx supports a default bookmark file, and up to 26 total bookmark files (see below). When multi-bookmarks is OFF, the - default bookmark file is used for the '<em>v</em>'iew bookmarks - and '<em>a</em>'dd bookmark link commands. If multi-bookmark - support is available in your account, the setting can be - changed to STANDARD or ADVANCED. In STANDARD mode, a menu of - available bookmarks always is invoked when you seek to view a - bookmark file or add a link, and you select the bookmark file - by its letter token (see <em>Bookmark file</em>, below) in that - menu. In ADVANCED mode, you instead are prompted for the letter - of the desired bookmark file, but can enter '<em>=</em>' to - invoke the STANDARD selection menu, or <em>RETURN</em> for the - default bookmark file.</dd> + default bookmark file is used for the + “<em>v</em>”iew bookmarks and + “<em>a</em>”dd bookmark link commands. If + multi-bookmark support is available in your account, the + setting can be changed to STANDARD or ADVANCED. In STANDARD + mode, a menu of available bookmarks always is invoked when you + seek to view a bookmark file or add a link, and you select the + bookmark file by its letter token (see <em>Bookmark file</em>, + below) in that menu. In ADVANCED mode, you instead are prompted + for the letter of the desired bookmark file, but can enter + “<em>=</em>” to invoke the STANDARD selection menu, + or <em>RETURN</em> for the default bookmark file.</dd> <dt>Password for anonymous ftp</dt> @@ -1233,10 +1243,11 @@ header from an HTTP server to indicate what it is) but you know by some means that you have the matching display character set selected. 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 also can be toggled via the - RAW_TOGGLE command, normally mapped to '<em>@</em>', and at - startup via the <em>-raw</em> switch.</dd> + the document is ISO-8859-1 or another “assumed document + character set”. The setting also can be toggled via the + RAW_TOGGLE command, normally mapped to + “<em>@</em>”, and at startup via the <em>-raw</em> + switch.</dd> <dt>Send User-Agent header</dt> @@ -1488,13 +1499,13 @@ links</a></h2> <p>At any time while viewing documents within Lynx, you may use - the '<em>c</em>' command to send a mail message to the owner of - the current document if the author of the document has specified - ownership. (Note to authors: if you want to assign the ownership - to your document, you need to add into HEAD section a LINK - element with appropriate value for REV attribute. Two values are - recognized: <em>owner</em> and <em>made</em> (these are case - insensitive). For example,</p> + the “<em>c</em>” command to send a mail message to + the owner of the current document if the author of the document + has specified ownership. (Note to authors: if you want to assign + the ownership to your document, you need to add into HEAD section + a LINK element with appropriate value for REV attribute. Two + values are recognized: <em>owner</em> and <em>made</em> (these + are case insensitive). For example,</p> <pre> <HEAD> … @@ -1525,14 +1536,14 @@ <p>To finish sending the message, exit your spawned editor or, if you are using the simple line mode input scheme, type a - '<em>.</em>' (period) on a line by itself. You will be asked a - final time whether to send the message. If you press - '<em>y</em>', you will be prompted whether to append your - signature file if one was defined in <a href= + “<em>.</em>” (period) on a line by itself. You will + be asked a final time whether to send the message. If you press + “<em>y</em>”, you will be prompted whether to append + your signature file if one was defined in <a href= "#lynx.cfg">lynx.cfg</a> and is accessible, and then the message - will be sent, whereas if you press '<em>n</em>' the message will - be deleted. Entering Control-G in response to any prompts also - will cancel the mailing.</p> + will be sent, whereas if you press “<em>n</em>” the + message will be deleted. Entering Control-G in response to any + prompts also will cancel the mailing.</p> <p>[<a href="#ToC-Mail">ToC</a>]</p> @@ -1585,37 +1596,40 @@ Menu</em>.</p> <p>To save a bookmark to the document you wish to place in the - bookmark file press the '<em>a</em>' key and you will be - asked:</p> + bookmark file press the “<em>a</em>” key and you will + be asked:</p> <blockquote> <p>Save D)ocument or L)ink to bookmark file or C)ancel? (d,l,c):</p> </blockquote> - <p>Answer '<em>d</em>' to save a link to the document you are - currently viewing or '<em>l</em>' to save the link that is - currently selected on the page. Selecting '<em>c</em>' will - cancel without saving anything to your bookmark file.</p> + <p>Answer “<em>d</em>” to save a link to the document + you are currently viewing or “<em>l</em>” to save the + link that is currently selected on the page. Selecting + “<em>c</em>” will cancel without saving anything to + your bookmark file.</p> <p>A bookmark file will be created in conjunction with acting on - the '<em>a</em>'dd command if it does not already exist. - Otherwise, the link will be added to the bottom of the + the “<em>a</em>”dd command if it does not already + exist. Otherwise, the link will be added to the bottom of the pre-existing bookmark file. You must have created a bookmark file - via the '<em>a</em>'dd command before you can view it.</p> + via the “<em>a</em>”dd command before you can view + it.</p> - <p>Use the '<em>v</em>' command to view the list of bookmarks you - have saved. While viewing the bookmark list you may select a - bookmark as you would any other link.</p> + <p>Use the “<em>v</em>” command to view the list of + bookmarks you have saved. While viewing the bookmark list you may + select a bookmark as you would any other link.</p> <p>You can remove a link from the bookmark list by pressing the - '<em>r</em>' key when positioned on that link. You also can use a - standard text editor (e.g., via the '<em>e</em>'dit command while - viewing a bookmark file, if an external editor has been defined - via the <em>Options menu</em>) to delete or re-order links in the - bookmark file, or to modify a link name by editing the content of - the <em>A</em>nchor element for the link, but you should not - change the format within the line for the link, consisting of an + “<em>r</em>” key when positioned on that link. You + also can use a standard text editor (e.g., via the + “<em>e</em>”dit command while viewing a bookmark + file, if an external editor has been defined via the <em>Options + menu</em>) to delete or re-order links in the bookmark file, or + to modify a link name by editing the content of the + <em>A</em>nchor element for the link, but you should not change + the format within the line for the link, consisting of an <em>LI</em> element followed by the <em>A</em>nchor element, nor cause the line to become wrapped to a second line. You similarly can change the link destination by editing the double-quoted @@ -1628,8 +1642,8 @@ markup to the bookmark file. If the format and spacing (other than the <em>A</em>nchor content or <em>HREF</em> value) within lines is changed or other HTML markup is added, the - '<em>a</em>'dd and '<em>r</em>'emove commands may not work - properly.</p> + “<em>a</em>”dd and “<em>r</em>”emove + commands may not work properly.</p> <p>When multi-bookmarks (see <a href= "#InteractiveOptions">Options Menu</a>) is OFF, you will always @@ -1637,9 +1651,9 @@ STANDARD, a menu of up to 26 bookmark files will be invoked, and you select the bookmark file by entering its letter token. When it is ADVANCED, you will be prompted for the letter token, but - can enter '<em>=</em>' to invoke the STANDARD selection menu, or - <em>RETURN</em> for the default bookmark file. [<a href= - "#ToC-Bookmarks">ToC</a>]</p> + can enter “<em>=</em>” to invoke the STANDARD + selection menu, or <em>RETURN</em> for the default bookmark file. + [<a href="#ToC-Bookmarks">ToC</a>]</p> <h2 id="id-Jumps"><a name="Jumps" id="Jumps">Jump Command</a></h2> @@ -1649,11 +1663,12 @@ distribution package. To use the jumps command, create a <em>jumps file</em> with the same format as the sample file, but containing your own URLs & short-cut names. Once you have - done that, typing '<em>j</em>' prompts you to enter a short-cut - name, which will take you straight to the URL associated with the - short-cut in the jumps file, much like using '<em>g</em>'. If you - want to check which short-cuts are available, type '<em>?</em>' - at the jump prompt for the full list.</p> + done that, typing “<em>j</em>” prompts you to enter a + short-cut name, which will take you straight to the URL + associated with the short-cut in the jumps file, much like using + “<em>g</em>”. If you want to check which short-cuts + are available, type “<em>?</em>” at the jump prompt + for the full list.</p> <p>You can set up a jumps file which makes Lynx prompt for parameters, e.g., as part of a search. Do this by putting a "%s" @@ -1662,8 +1677,8 @@ you for the parameters, one by one.</p> <p>All jump short-cuts you have entered are saved in a circular - buffer in the same way as with '<em>g</em>' and '<em>/</em>' - (search):<br> + buffer in the same way as with “<em>g</em>” and + “<em>/</em>” (search):<br> previous entries can be retrieved with <em>up-arrow</em> or <em>down-arrow</em>.</p> @@ -1694,49 +1709,50 @@ <dl> <dt><code>C)reate</code></dt> - <dd>Type '<em>c</em>' to create a new file. New file will be - empty.</dd> + <dd>Type “<em>c</em>” to create a new file. New + file will be empty.</dd> <dt><code>D)ownload</code></dt> - <dd>Type '<em>d</em>' to download using one of the pre-defined - options.</dd> + <dd>Type “<em>d</em>” to download using one of the + pre-defined options.</dd> <dt><code>E)dit</code></dt> - <dd>Type '<em>e</em>' to spawn the editor defined in - <em>Options Menu</em> and load a selected file for + <dd>Type “<em>e</em>” to spawn the editor defined + in <em>Options Menu</em> and load a selected file for editing.</dd> <dt><code>F)ull Menu</code></dt> - <dd>Type '<em>f</em>' to show full menu of options available - for selection. Menu may vary according to type of file selected - and compression facilities available. + <dd>Type “<em>f</em>” to show full menu of options + available for selection. Menu may vary according to type of + file selected and compression facilities available. <!-- List of full menu options --></dd> <dt><code>M)odify</code></dt> - <dd>Type '<em>m</em>' to modify the name or location of file. - Then type '<em>n</em>' to rename the file or '<em>l</em>' to - move the file to a different location.</dd> + <dd>Type “<em>m</em>” to modify the name or + location of file. Then type “<em>n</em>” to rename + the file or “<em>l</em>” to move the file to a + different location.</dd> <dt><code>R)emove</code></dt> - <dd>Type '<em>r</em>' to remove the selected file or - directory.</dd> + <dd>Type “<em>r</em>” to remove the selected file + or directory.</dd> <dt><code>T)ag</code></dt> - <dd>Type '<em>t</em>' to tag highlighted file. Further - operations will be performed on tagged files instead of + <dd>Type “<em>t</em>” to tag highlighted file. + Further operations will be performed on tagged files instead of highlighted ones.</dd> <dt><code>U)pload</code></dt> - <dd>Type '<em>u</em>' to upload a file to the present - directory. An uploading method must have been pre-defined in - <a href="#lynx.cfg">lynx.cfg</a> .</dd> + <dd>Type “<em>u</em>” to upload a file to the + present directory. An uploading method must have been + pre-defined in <a href="#lynx.cfg">lynx.cfg</a> .</dd> </dl> <p>[<a href="#ToC-DirEd">ToC</a>]</p> @@ -1753,8 +1769,8 @@ <p>A summary of all the keystroke commands and their key bindings can be invoked via the KEYMAP command, normally mapped to - '<em>k</em>' and '<em>K</em>'. The following describes some of - the most commonly used commands.</p> + “<em>k</em>” and “<em>K</em>”. The + following describes some of the most commonly used commands.</p> <dl> <dt><em>^A</em></dt> @@ -1820,65 +1836,67 @@ <dt><em>#</em></dt> - <dd>The '<em>#</em>' command jumps you to the pseudo Toolbar or - Banner if present in the current document. Use - <em>left-arrow</em> to return from there to your previous + <dd>The “<em>#</em>” command jumps you to the + pseudo Toolbar or Banner if present in the current document. + Use <em>left-arrow</em> to return from there to your previous position in the document.</dd> <dt><em>!</em></dt> - <dd>When '<em>!</em>' is pressed your default shell will be - spawned. When you quit or exit the shell you will return to - Lynx (usually <em>exit</em> under Unix and <em>logout</em> - under VMS). This command is usually disabled for anonymous - users. On VMS, '<em>$</em>' normally is a synonym. On Win32, - this has no effect [???].</dd> + <dd>When “<em>!</em>” is pressed your default shell + will be spawned. When you quit or exit the shell you will + return to Lynx (usually <em>exit</em> under Unix and + <em>logout</em> under VMS). This command is usually disabled + for anonymous users. On VMS, “<em>$</em>” normally + is a synonym. On Win32, this has no effect [???].</dd> <dt><em>g</em></dt> - <dd>The '<em>g</em>' command allows any URL to be viewed. - Pressing the '<em>g</em>' command will bring up a prompt asking - for a URL. Type in the URL that you wish to view. All - previously entered goto URLs are saved in a circular buffer, - and can be accessed at the prompt by pressing the - <em>up-arrow</em> or <em>down-arrow</em> keys.</dd> + <dd>The “<em>g</em>” command allows any URL to be + viewed. Pressing the “<em>g</em>” command will + bring up a prompt asking for a URL. Type in the URL that you + wish to view. All previously entered goto URLs are saved in a + circular buffer, and can be accessed at the prompt by pressing + the <em>up-arrow</em> or <em>down-arrow</em> keys.</dd> <dt><em>G</em></dt> - <dd>The '<em>G</em>' command allows you to edit the URL of the - current document and then use that as a goto URL. Pressing the - '<em>G</em>' command will bring up a prompt asking you to edit - the current document's URL. If you do not modify it, or - completely delete it, or enter Control-G, the command will be - cancelled. If the current document has POST content associated - with it, an Alert will be issued. If you do edit that URL, and - it does not simply involve a fragment change (for seeking a - position in the current document), the modified URL will be - submitted with method GET and no POST content. If a + <dd>The “<em>G</em>” command allows you to edit the + URL of the current document and then use that as a goto URL. + Pressing the “<em>G</em>” command will bring up a + prompt asking you to edit the current document's URL. If you do + not modify it, or completely delete it, or enter Control-G, the + command will be cancelled. If the current document has POST + content associated with it, an Alert will be issued. If you do + edit that URL, and it does not simply involve a fragment change + (for seeking a position in the current document), the modified + URL will be submitted with method GET and no POST content. If a modification of the current document's URL results in a submission, that modified URL will be entered into the circular buffer for goto URLs, and can be accessed for further - modification via the '<em>g</em>' command.</dd> + modification via the “<em>g</em>” command.</dd> <dt><em>E</em></dt> - <dd>The '<em>E</em>' command allows you to edit the URL (or - ACTION) of the current link and then use that as a goto URL. - Pressing the '<em>E</em>' command will bring up a prompt asking - you to edit the current link's URL. If you do not modify it, or - completely delete it, or enter Control-G, the command will be - cancelled. Otherwise, the request for the 'E'dited URL will be - sent with method GET, and will be entered into the circular - buffer for goto URLs so that it can be accessed for further - modification via the '<em>g</em>' command. Note that lower case - 'e' invokes the external editor for the current document.</dd> + <dd>The “<em>E</em>” command allows you to edit the + URL (or ACTION) of the current link and then use that as a goto + URL. Pressing the “<em>E</em>” command will bring + up a prompt asking you to edit the current link's URL. If you + do not modify it, or completely delete it, or enter Control-G, + the command will be cancelled. Otherwise, the request for the + “E”dited URL will be sent with method GET, and will + be entered into the circular buffer for goto URLs so that it + can be accessed for further modification via the + “<em>g</em>” command. Note that lower case + “e” invokes the external editor for the current + document.</dd> <dt><em>=</em></dt> - <dd>The '<em>=</em>' command shows information about the - current document and the currently selected link if there is - one. The number of lines in the file, URL, title, owner, and - type are shown.</dd> + <dd>The “<em>=</em>” command shows information + about the current document and the currently selected link if + there is one. The number of lines in the file, URL, title, + owner, and type are shown.</dd> <dt><em>^T</em></dt> @@ -1889,10 +1907,10 @@ document in trace mode. You may then examine the <em>Lynx Trace Log</em> file with the <em>;</em> command if enabled (see below), watch out especially for lines marked with a number of - asterisks '<code>*****</code>'. You also can submit the - document for validation via links in the online help menu. If - you are able to diagnose the problem, send a message about it - to the document's author.</dd> + asterisks “<code>*****</code>”. You also can submit + the document for validation via links in the online help menu. + If you are able to diagnose the problem, send a message about + it to the document's author.</dd> <dt><em>;</em></dt> @@ -1913,43 +1931,44 @@ <dt><a name="asterisk-key" id= "asterisk-key"><em>*</em></a></dt> - <dd>The '<em>*</em>' command toggles image_links mode on and - off. When on, links will be created for all images, including - inline images. If you have an image viewer mapped to the - image's MIME type, you can activate such links to view an + <dd>The “<em>*</em>” command toggles image_links + mode on and off. When on, links will be created for all images, + including inline images. If you have an image viewer mapped to + the image's MIME type, you can activate such links to view an inline image. You should normally have this mode toggled off.</dd> <dt><em>@</em></dt> - <dd>The '<em>@</em>' command toggles raw 8-bit or CJK mode on - and off. When on, the charset is assumed to match the selected - character set and 8-bit characters are not reverse translated - with respect to the ISO-8859-1 conversion tables.</dd> + <dd>The “<em>@</em>” command toggles raw 8-bit or + CJK mode on and off. When on, the charset is assumed to match + the selected character set and 8-bit characters are not reverse + translated with respect to the ISO-8859-1 conversion + tables.</dd> <dt><a name="lbracket-key" id= "lbracket-key"><em>[</em></a></dt> - <dd>The '<em>[</em>' command toggles pseudo_inlines mode on and - off. When on, inline images which have no ALT string specified - will have an <em>[INLINE]</em> pseudo-ALT string inserted in - the Lynx display. When off, they will be treated as having - ALT="" (i.e., they'll be ignored). If image_links mode is - toggled on, the pseudo-ALT strings will be restored, to serve - as links to the inline images' sources.</dd> + <dd>The “<em>[</em>” command toggles pseudo_inlines + mode on and off. When on, inline images which have no ALT + string specified will have an <em>[INLINE]</em> pseudo-ALT + string inserted in the Lynx 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.</dd> <dt><em>]</em></dt> - <dd>The '<em>]</em>' command is used to send HEAD requests 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., Lynx does not retrieve any previous server - replies from its cache. Note that for form submissions, http - servers vary in whether they'll treat HEAD requests as valid - and return the CGI script's headers, or treat it as invalid and - return an error message.</dd> + <dd>The “<em>]</em>” command is used to send HEAD + requests 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., Lynx does not retrieve any previous + server replies from its cache. Note that for form submissions, + http servers vary in whether they'll treat HEAD requests as + valid and return the CGI script's headers, or treat it as + invalid and return an error message.</dd> <dt><em>^K</em></dt> @@ -1965,9 +1984,10 @@ <dt><em>z</em></dt> <dd>Lynx supports completely interruptible I/O processes. Press - the '<em>z</em>' key at any time during a connect or transfer - process and the process will be halted. If any data was - transferred before the interrupt, it will be displayed.</dd> + the “<em>z</em>” key at any time during a connect + or transfer process and the process will be halted. If any data + was transferred before the interrupt, it will be + displayed.</dd> <dt><em>numbers</em></dt> @@ -2001,8 +2021,9 @@ <dd>Buttons are displayed in the same way that Lynx displays links in a document. To "push" the button press the <em>right-arrow</em> or <em>Return</em> key. If it is a form - submission button, you also can use the NOCACHE ('<em>x</em>') - or DOWNLOAD ('<em>d</em>') keystroke commands to "push" the + submission button, you also can use the NOCACHE + (“<em>x</em>”) or DOWNLOAD + (“<em>d</em>”) keystroke commands to "push" the button (see below).</dd> <dt>Checkboxes and Radio buttons</dt> @@ -2026,16 +2047,16 @@ <em>down-arrow</em>, <em>page-up</em>, <em>page-down</em>, and other navigation keys to move the cursor among options, and the <em>right-arrow</em> or <em>Return</em> key to select an - option. You also can use the '<em>/</em>' and '<em>n</em>'ext - <a href="#Search">searching</a> commands for navigating to - options which contain particular strings. <em>NOTE</em> that - the popup menu feature can be disabled via compilation and/or - configuration options, or via the <a href= - "#InteractiveOptions">Options Menu</a>, in which case the - selection field options will be converted to a list of radio - buttons. The default setting for use of popups or radio button - lists can be toggled via the <em>-popup</em> command line - switch.</dd> + option. You also can use the “<em>/</em>” and + “<em>n</em>”ext <a href="#Search">searching</a> + commands for navigating to options which contain particular + strings. <em>NOTE</em> that the popup menu feature can be + disabled via compilation and/or configuration options, or via + the <a href="#InteractiveOptions">Options Menu</a>, in which + case the selection field options will be converted to a list of + radio buttons. The default setting for use of popups or radio + button lists can be toggled via the <em>-popup</em> command + line switch.</dd> <dt>Text Entry Fields</dt> @@ -2075,11 +2096,11 @@ <p>Some flavors of UNIX, shells & terminal settings require that you enter <em>^V^Ve</em> in order to start the external editor, as they also use <em>^V</em> as default - command-line quote key (called `lnext' in stty man pages and - `stty -a' output); to avoid this, you can put `stty lnext - undef' in your .cshrc file (or .profile or .bashrc, depending - on what shell you use), or invoke Lynx with a wrapper script, - e.g.</p> + command-line quote key (called “lnext” in stty + man pages and “stty -a” output); to avoid this, + you can put “stty lnext undef” in your .cshrc + file (or .profile or .bashrc, depending on what shell you + use), or invoke Lynx with a wrapper script, e.g.</p> <p><code> #!/bin/sh<br> stty lnext undef<br> @@ -2152,8 +2173,8 @@ KEYMAP:e:DWIMEDIT<br> (the first is only functional for TEXTAREA editing, while the second allows to use the same key for normal <a href= - "#FileEdit">file editing</a> <em>as long as both functions - don't conflict</em>).</p> + "#FileEdit">file editing</a> <em>as long as both functions do + not conflict</em>).</p> <p>Please see the <a href="#CtrlVNote">note above</a> for details about <em>^V</em> behavior.</p>You can also use two @@ -2211,11 +2232,11 @@ content, and the METHOD was <em>GET</em>, Lynx will retrieve from its cache what was returned from the previous submission. If you wish to resubmit that form to the server with the same content as - previously, use the NOCACHE command ('<em>x</em>') when - positioned on the submit button. The <em>right-arrow</em> and - <em>Return</em> keys also will invoke a no-cache resubmission if - the reply from a form submission included a META element with a - no-cache Pragma or Cache-Control directive:<br></p> + previously, use the NOCACHE command (“<em>x</em>”) + when positioned on the submit button. The <em>right-arrow</em> + and <em>Return</em> keys also will invoke a no-cache resubmission + if the reply from a form submission included a META element with + a no-cache Pragma or Cache-Control directive:<br></p> <pre> <em><META HTTP-EQUIV="Pragma" CONTENT="no-cache"></em> <em><META HTTP-EQUIV="Cache-Control" CONTENT="no-cache"></em> @@ -2224,10 +2245,10 @@ <p>or the server sent a "Pragma" or "Cache-Control" MIME header with a no-cache directive.</p> - <p>You also can use the DOWNLOAD ('<em>d</em>') keystroke command - when positioned on a form submit button if you wish to download - the server's reply to the submission instead of having Lynx - render and display it.</p> + <p>You also can use the DOWNLOAD (“<em>d</em>”) + keystroke command when positioned on a form submit button if you + wish to download the server's reply to the submission instead of + having Lynx render and display it.</p> <p>Forms which have <em>POST</em> as the METHOD, or a <a href= "lynx_url_support.html#mailto_url">mailto:</a> URL as the ACTION, @@ -2281,16 +2302,16 @@ submitting the form. Otherwise, the entire string is treated as a submit button. If a VALUE or ALT attribute is present and clickable images is set, Lynx prepends "[IMAGE]" as a link for - the image, followed by '-' and then the attribute's value as the - displayed string for the submit button. Note that earlier - versions of Lynx would send a name=value pair instead of a 0,0 - coordinate pair if a TYPE="image" submit button was NAME-ed, had - a VALUE attribute in the INPUT tag, and was used to submit the - form. The script which analyzes the form content thus could be - made aware whether the submission was by a user with a graphic - client and had image loading turned on, or by a user who did not - see the image nor make a conscious choice within it. However, - requests that this be included in HTML specifications + the image, followed by “-” and then the attribute's + value as the displayed string for the submit button. Note that + earlier versions of Lynx would send a name=value pair instead of + a 0,0 coordinate pair if a TYPE="image" submit button was + NAME-ed, had a VALUE attribute in the INPUT tag, and was used to + submit the form. The script which analyzes the form content thus + could be made aware whether the submission was by a user with a + graphic client and had image loading turned on, or by a user who + did not see the image nor make a conscious choice within it. + However, requests that this be included in HTML specifications consistently have fallen on deaf ears, and thus Lynx now "fakes" a 0,0 coordinate pair whether or not a VALUE or ALT attribute is present in the INPUT tag. Ideally, the script which analyzes the @@ -2327,17 +2348,17 @@ <em>ENCTYPE="application/sgml-form-urlencoded"</em> for which all reserved characters in the content will be hex escaped, as with <em>application/x-www-form-urlencoded</em>, but semicolons - ('<em>;</em>') instead of ampersands ('<em>&</em>') will be - used as the separator for name=value pairs in the form content. - The use of semicolons is preferred for forms with the - <em>GET</em> METHOD, because the <em>GET</em> METHOD causes the - encoded form content to be appended as a <em>?searchpart</em> for - the form's ACTION, and if such URLs are used in - <em>text/html</em> documents or bookmark files without conversion - of the ampersands to SGML character references - (<em>&amp;</em> or <em>&#38;</em>), their being followed - by form field NAMEs which might correspond to SGML entities could - lead to corruption of the intended URL.</p> + (“<em>;</em>”) instead of ampersands + (“<em>&</em>”) will be used as the separator for + name=value pairs in the form content. The use of semicolons is + preferred for forms with the <em>GET</em> METHOD, because the + <em>GET</em> METHOD causes the encoded form content to be + appended as a <em>?searchpart</em> for the form's ACTION, and if + such URLs are used in <em>text/html</em> documents or bookmark + files without conversion of the ampersands to SGML character + references (<em>&amp;</em> or <em>&#38;</em>), their + being followed by form field NAMEs which might correspond to SGML + entities could lead to corruption of the intended URL.</p> <p>NOTE, in this regard, that Lynx converts ampersands to <em>&amp;</em> when creating bookmarks, and thus the bookmark @@ -2354,20 +2375,20 @@ Lynx does not yet support INPUTs with <em>TYPE="file"</em> or <em>TYPE="range"</em> and will set the <em>DISABLED</em> attribute for all of the form's fields if any INPUTs with either - of those two TYPEs are present, so that the form can't be + of those two TYPEs are present, so that the form cannot be submitted. Otherwise, Lynx will submit the form with the multipart ENCTYPE.</p> <p>A <em>Content-Disposition: file; filename=name.suffix</em> header can be used by CGI scripts to set the suggested filename - offered by Lynx for '<em>d</em>'ownload and '<em>p</em>'rint menu - options to save or mail the body returned by the script following - submission of a FORM. Otherwise, Lynx uses the last symbolic - element in the path for the FORM's ACTION, which is normally the - script, itself, or a PATH_INFO field, and thus might be - misleading. This also can be done via a META element in any - document:</p> + offered by Lynx for “<em>d</em>”ownload and + “<em>p</em>”rint menu options to save or mail the + body returned by the script following submission of a FORM. + Otherwise, Lynx uses the last symbolic element in the path for + the FORM's ACTION, which is normally the script, itself, or a + PATH_INFO field, and thus might be misleading. This also can be + done via a META element in any document:</p> <pre> <em><META HTTP-EQUIV="Content-Disposition" CONTENT="file; filename=name.suffix"></em> @@ -2400,12 +2421,13 @@ VERBOSE_ Y Y Y verbose_img FM = Form-based Menu ; KM = Key-based Menu ; -in .lynxrc , VERBOSE_IMAGES is called `verbose_images': +in .lynxrc , VERBOSE_IMAGES is called “verbose_images”: the other two cannot be saved between sessions. </pre> - <p>In the Form-based Menu, the 3-way `Show images' selection - combines the effects of the `*' & `[' keys, as follows:</p> + <p>In the Form-based Menu, the 3-way “Show images” + selection combines the effects of the “*” & + “[” keys, as follows:</p> <pre> Ignore clickable_images = FALSE, pseudo_inline_alts = FALSE As labels clickable_images = FALSE, pseudo_inline_alts = TRUE @@ -2583,7 +2605,7 @@ the other two cannot be saved between sessions. value in the LINK, will invoke creation of a <em>banner</em> at the top of the first page, with the element's HREF as the link, and the token as the default link name. If a TITLE attribute is - included in the LINK, it's value will be used as the link name + included in the LINK, its value will be used as the link name instead of the default. <em>Bookmark</em> and <em>Banner</em> are intended to be accompanied by a TITLE attribute, which in effect makes the namespace for REL <em>banner</em> tokens infinite.</p> @@ -2595,39 +2617,40 @@ the other two cannot be saved between sessions. <em>STARTFILE</em> (i.e., derived from the configuration files or the WWW_HOME environment variable, <em>not</em> the command line <em>startfile</em> if one was used). However, if a - <em>-homepage=URL</em> was specified on the command line, it's - URL will be used as the HREF. For the special token - <em>Index</em> without an HREF, Lynx will use the - <em>DEFAULT_INDEX_FILE</em> derived from the configuration files, - or if an <em>-index=URL</em> was specified on the command line, - it's URL will be used as the HREF.</p> + <em>-homepage=URL</em> was specified on the command line, its URL + will be used as the HREF. For the special token <em>Index</em> + without an HREF, Lynx will use the <em>DEFAULT_INDEX_FILE</em> + derived from the configuration files, or if an + <em>-index=URL</em> was specified on the command line, its URL + will be used as the HREF.</p> <p>Lynx does not waste screen real estate maintaining the <em>banner</em> at the top of every page, but the Lynx TOOLBAR - keystroke command ('<em>#</em>') will, any time it is pressed, - position you on the <em>banner</em> so that any of its links can - be activated, and pressing the <em>left-arrow</em> when in the - <em>banner</em> will return you to where you were in the current - document. The toolbar is indicated by a '<em>#</em>" preceding - its first link when present on the screen, that is, when the - first page of the document is being displayed. The availability - of a toolbar is indicated by a '<em>#</em>' at the top, left-hand - corner of the screen when the second or subsequent pages of the - document are being displayed.</p> + keystroke command (“<em>#</em>”) will, any time it is + pressed, position you on the <em>banner</em> so that any of its + links can be activated, and pressing the <em>left-arrow</em> when + in the <em>banner</em> will return you to where you were in the + current document. The toolbar is indicated by a + “<em>#</em>" preceding its first link when present on the + screen, that is, when the first page of the document is being + displayed. The availability of a toolbar is indicated by a + “<em>#</em>” at the top, left-hand corner of the + screen when the second or subsequent pages of the document are + being displayed.</p> <p>Lynx also recognizes the <a href= "http://www.w3.org/MarkUp/html3/Contents.html">HTML 3.0</a> BANNER container element, and will create a <em>banner</em> based on its content if one has not already been created based on LINK elements. Lynx treats the Microsoft MARQUEE element as a synonym - for BANNER (i.e., presenting it's markup as a static + for BANNER (i.e., presenting its markup as a static <em>banner</em>, without any horizontal scrolling of its content). Lynx does not prefix the BANNER or MARQUEE content with - a '<em>#</em>' because the content need not be only a series of - links with brief, descriptive links names, but does add a - '<em>#</em>' at the top, left-hand corner of the screen when the - content is not being displayed, to indicate it's accessibility - via the TOOLBAR keystroke command.</p> + a “<em>#</em>” because the content need not be only a + series of links with brief, descriptive links names, but does add + a “<em>#</em>” at the top, left-hand corner of the + screen when the content is not being displayed, to indicate its + accessibility via the TOOLBAR keystroke command.</p> <p>[<a href="#ToC-Banners">ToC</a>]</p> @@ -2773,7 +2796,7 @@ the other two cannot be saved between sessions. "http://www.w3.org/MarkUp/html3/Contents.html">HTML 3.0</a> and later specifications provide for two classes of quotation in HTML documents. Block quotes, designated by the BLOCKQUOTE element (or - it's abbreviated synonym BQ in HTML 3.0), have implied paragraph + its abbreviated synonym BQ in HTML 3.0), have implied paragraph breaks preceding and following the start and end tags for the block. Character level quotes, designated by the Q element, in contrast are simply directives in the markup to insert an @@ -2969,21 +2992,22 @@ the other two cannot be saved between sessions. <p>When cookie support is enabled, <em>Set-Cookie</em> MIME headers received from an http server invoke confirmation prompts - with possible replies of '<em>Y</em>'es or '<em>N</em>'o for - acceptance of the cookie, '<em>A</em>'lways to accept the cookie - and to allow all subsequent cookies from that <em>domain</em> - (server's Fully Qualified Domain Name, or site-identifying - portion of the FQDN) without further confirmation prompts, or - ne'<em>V</em>'er to never allow cookies from that <em>domain</em> - to be accepted (silently ignore its <em>Set-Cookie</em> MIME - headers). All unexpired cookies are held in a hypothetical - <em>Cookie Jar</em> which can be examined via the COOKIE_JAR - keystroke command, normally mapped to <em>Ctrl-K</em>, for - invoking the <a href="keystrokes/cookie_help.html">Cookie Jar - Page</a>. If Lynx has been compiled with the - --enable-persistent-cookies flag, then unexpired cookies will be - stored between sessions in the filename set with the COOKIE_FILE - option in your .lynxrc.</p> + with possible replies of “<em>Y</em>”es or + “<em>N</em>”o for acceptance of the cookie, + “<em>A</em>”lways to accept the cookie and to allow + all subsequent cookies from that <em>domain</em> (server's Fully + Qualified Domain Name, or site-identifying portion of the FQDN) + without further confirmation prompts, or + ne“<em>V</em>”er to never allow cookies from that + <em>domain</em> to be accepted (silently ignore its + <em>Set-Cookie</em> MIME headers). All unexpired cookies are held + in a hypothetical <em>Cookie Jar</em> which can be examined via + the COOKIE_JAR keystroke command, normally mapped to + <em>Ctrl-K</em>, for invoking the <a href= + "keystrokes/cookie_help.html">Cookie Jar Page</a>. If Lynx has + been compiled with the --enable-persistent-cookies flag, then + unexpired cookies will be stored between sessions in the filename + set with the COOKIE_FILE option in your .lynxrc.</p> <p>A common use of cookies by http servers is simply to track the documents visited by individual users. Though this can be useful @@ -3004,9 +3028,9 @@ the other two cannot be saved between sessions. <p>If you accept cookies when accessing a site, but are given no indication about how they will be used in subsequent requests to that site, nor can infer how they will be used, you can - <em>Gobble</em> (delete) the cookies and/or change the 'allow' - setting for its <em>domain</em> via the <a href= - "keystrokes/cookie_help.html">Cookie Jar Page</a>.</p> + <em>Gobble</em> (delete) the cookies and/or change the + “allow” setting for its <em>domain</em> via the + <a href="keystrokes/cookie_help.html">Cookie Jar Page</a>.</p> <p>[<a href="#ToC-Cookies">ToC</a>]</p> @@ -3205,10 +3229,10 @@ the other two cannot be saved between sessions. <dt><code><strong>-</strong></code></dt> <dd>If the argument is only - '<code><strong>-</strong></code>' (dash), then Lynx expects - to receive the arguments from stdin. This is to allow for - the potentially very long command line that can be - associated with the <em>-get_data</em> or + “<code><strong>-</strong></code>” (dash), then + Lynx expects to receive the arguments from stdin. This is + to allow for the potentially very long command line that + can be associated with the <em>-get_data</em> or <em>-post_data</em> arguments (see below). It can also be used to avoid having sensitive information in the invoking command line (which would be visible to other processes on @@ -3216,9 +3240,9 @@ the other two cannot be saved between sessions. <em>-pauth</em> options are used. On VMS, the dash must be encased in double-quotes ("-") and the keyboard input terminated with <em>Control-Z</em> or the command file - input terminated by a line that begins with '<em>$</em>'. - On Unix, the keyboard input terminator is - <em>Control-D</em>. On Win32, [???].</dd> + input terminated by a line that begins with + “<em>$</em>”. On Unix, the keyboard input + terminator is <em>Control-D</em>. On Win32, [???].</dd> <dt><code><strong>-accept_all_cookies</strong></code></dt> @@ -3233,7 +3257,7 @@ the other two cannot be saved between sessions. <dt> <code><strong>-assume_charset=</strong><em>MIMENAME</em></code></dt> - <dd>charset for documents that don't specify it.</dd> + <dd>charset for documents that do not specify it.</dd> <dt> <code><strong>-assume_local_charset=</strong><em>MIMENAME</em></code></dt> @@ -3480,8 +3504,8 @@ the other two cannot be saved between sessions. <dt> <code><strong>-force_empty_hrefless_a</strong></code></dt> - <dd>force HREF-less 'A' elements to be empty (close them as - soon as they are seen).</dd> + <dd>force HREF-less “A” elements to be empty + (close them as soon as they are seen).</dd> <dt><code><strong>-force_html</strong></code></dt> @@ -3511,7 +3535,7 @@ the other two cannot be saved between sessions. <dd>properly formatted data for a get form are read in from stdin and passed to the form. Input is terminated by a line - that starts with '---'.</dd> + that starts with “---”.</dd> <dt><code><strong>-head</strong></code></dt> @@ -3550,8 +3574,8 @@ the other two cannot be saved between sessions. <dt><code><strong>-historical</strong></code></dt> - <dd>toggles use of '>' or '-->' as a terminator for - comments.</dd> + <dd>toggles use of “>” or + “-->” as a terminator for comments.</dd> <dt> <code><strong>-homepage=</strong><em>URL</em></code></dt> @@ -3559,8 +3583,8 @@ the other two cannot be saved between sessions. <dd>set homepage separate from start page. Will be used if a fetch of the start page fails or if it is a script which does not return a document, and as the - <code><em>URL</em></code> for the '<em>m</em>'ain menu - command.</dd> + <code><em>URL</em></code> for the + “<em>m</em>”ain menu command.</dd> <dt><code><strong>-image_links</strong></code></dt> @@ -3608,11 +3632,12 @@ the other two cannot be saved between sessions. <dt><code><strong>-minimal</strong></code></dt> <dd>toggles minimal versus valid comment parsing. When - minimal, any '-->' serves as a terminator for a comment - element. When valid, pairs of '--' are treated as - delimiters for series of comments within the overall - comment element. If historical is set, that overrides - minimal or valid comment parsing.</dd> + minimal, any “-->” serves as a terminator + for a comment element. When valid, pairs of + “--” are treated as delimiters for series of + comments within the overall comment element. If historical + is set, that overrides minimal or valid comment + parsing.</dd> <dt><code><strong>-nested_tables</strong></code></dt> @@ -3694,7 +3719,7 @@ the other two cannot be saved between sessions. <dt><code><strong>-noredir</strong></code></dt> - <dd>don't follow URL redirections</dd> + <dd>do not follow URL redirections</dd> <dt><code><strong>-noreferer</strong></code></dt> @@ -3753,23 +3778,23 @@ the other two cannot be saved between sessions. popup windows or as lists of radio buttons. The default configuration can be changed in userdefs.h or <a href= "#lynx.cfg">lynx.cfg</a>. It also can be set and saved via - the 'o'ptions menu. The command line switch toggles the - default.</dd> + the “o”ptions menu. The command line switch + toggles the default.</dd> <dt><code><strong>-post_data</strong></code></dt> <dd>properly formatted data for a post form are read in from stdin and passed to the form. Input is terminated by a - line that starts with '---'.</dd> + line that starts with “---”.</dd> <dt><code><strong>-preparsed</strong></code></dt> <dd>show source preparsed and reformatted when used with - -source or in source view ('<em>\</em>'). May be useful for - debugging of broken HTML markup to visualize the difference - between SortaSGML and TagSoup <a href= + -source or in source view (“<em>\</em>”). May + be useful for debugging of broken HTML markup to visualize + the difference between SortaSGML and TagSoup <a href= "keystrokes/option_help.html#tagsoup">recovery modes</a>, - switched by '<em>^V</em>'.</dd> + switched by “<em>^V</em>”.</dd> <dt><code><strong>-prettysrc</strong></code></dt> @@ -3918,7 +3943,8 @@ the other two cannot be saved between sessions. <dt>goto</dt> - <dd>disable the '<em>g</em>' (goto) command.</dd> + <dd>disable the “<em>g</em>” (goto) + command.</dd> <dt>inside_ftp</dt> @@ -3945,7 +3971,8 @@ the other two cannot be saved between sessions. <dt>jump</dt> - <dd>disable the '<em>j</em>' (jump) command.</dd> + <dd>disable the “<em>j</em>” (jump) + command.</dd> <dt>lynxcgi</dt> @@ -4069,8 +4096,8 @@ the other two cannot be saved between sessions. systems without FANCY_CURSES capabilities. The default configuration can be changed in userdefs.h or <a href= "#lynx.cfg">lynx.cfg</a>. It also can be set and saved via - the 'o'ptions menu. The command line switch toggles the - default.</dd> + the “o”ptions menu. The command line switch + toggles the default.</dd> <dt><code><strong>-show_rate</strong></code></dt> @@ -4081,8 +4108,8 @@ the other two cannot be saved between sessions. <dt><code><strong>-soft_dquotes</strong></code></dt> <dd>toggles emulation of the old Netscape and Mosaic bug - which treated '<em>></em>' as a co-terminator for - double-quotes and tags.</dd> + which treated “<em>></em>” as a + co-terminator for double-quotes and tags.</dd> <dt><code><strong>-source</strong></code></dt> @@ -4171,9 +4198,10 @@ the other two cannot be saved between sessions. keystroke command. Once a log is started for the session, all trace and other stderr messages are written to the log. The contents of the log can be examined during the session - via the TRACE_LOG (normally, '<em>;</em>') keystroke - command. If use of a Lynx Trace Log is turned off, any - trace output will go to the standard error stream.</dd> + via the TRACE_LOG (normally, “<em>;</em>”) + keystroke command. If use of a Lynx Trace Log is turned + off, any trace output will go to the standard error + stream.</dd> <dt><code><strong>-tna</strong></code></dt> @@ -4186,8 +4214,9 @@ the other two cannot be saved between sessions. (<em>Lynx.trace</em> in the home directory) has been started for the current session, all trace messages are written to that log, and can be examined during the session - via the TRACE_LOG (normally, '<em>;</em>') command. If no - Trace Log file is in use, trace messages go to stderr.</dd> + via the TRACE_LOG (normally, “<em>;</em>”) + command. If no Trace Log file is in use, trace messages go + to stderr.</dd> <dt> <code><strong>-trace_mask=</strong><em>value</em></code></dt> @@ -4300,10 +4329,10 @@ the other two cannot be saved between sessions. <p>No options are required, nor is a startfile argument required. White space can be used in place of equal sign separators - ('<em>=</em>') appearing in the option list above. It can not be - used in place of the equal signs in forms like "-option=on" and - "-option=off" for simple switches and toggles, for which - "-option" alone (without a value) is valid.</p> + (“<em>=</em>”) appearing in the option list above. It + can not be used in place of the equal signs in forms like + "-option=on" and "-option=off" for simple switches and toggles, + for which "-option" alone (without a value) is valid.</p> <p>[<a href="#ToC-Invoking">ToC</a>]</p> @@ -4347,11 +4376,11 @@ the other two cannot be saved between sessions. by alphabet</a>.</p> <p>To view your current configuration derived from lynx.cfg and - any included configuration files, press <em>'g'</em> and type in - '<em>lynxcfg:</em>'. If you are using the forms-based <em>Options - Menu</em>, you may press <em>'o'</em> for the Options Menu and - follow the '<em>Check your lynx.cfg</em>' link near the - bottom.</p> + any included configuration files, press <em>“g”</em> + and type in “<em>lynxcfg:</em>”. If you are using the + forms-based <em>Options Menu</em>, you may press + <em>“o”</em> for the Options Menu and follow the + “<em>Check your lynx.cfg</em>'s link near the bottom.</p> <p>However, for those who have a restricted account many Lynx features may be disabled by the system administrator, you diff --git a/lynx_help/keystrokes/alt_edit_help.html b/lynx_help/keystrokes/alt_edit_help.html index 2268a819..514e0799 100644 --- a/lynx_help/keystrokes/alt_edit_help.html +++ b/lynx_help/keystrokes/alt_edit_help.html @@ -1,4 +1,4 @@ -<!-- $LynxId: alt_edit_help.html,v 1.11 2014/01/08 00:56:30 tom Exp $ --> +<!-- $LynxId: alt_edit_help.html,v 1.14 2017/04/28 21:24:42 tom Exp $ --> <!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01//EN"> <html> @@ -19,7 +19,18 @@ </head> <body> - <h2>Overview</h2> + <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 @@ -28,15 +39,16 @@ 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> + they may be selected via the “o”ptions menu, or by + editing lineedit_mode in the “.lynxrc” file.</p> <p>Note: setting emacs/vi keys ON has no direct effect on line-editor bindings.</p> <p>This is the <em>Alternative Binding</em> keymap.</p> - <h2>Table of key-bindings</h2> + <h2><a name="alternate_bindings" id="alternate_bindings">Table of + key-bindings</a></h2> <pre> ENTER Input complete - RETURN TAB Input complete - TAB, Do @@ -69,7 +81,7 @@ Grow textarea - Ctrl-X g </pre> - <h2>Notes</h2> + <h2><a name="notes" id="notes">Notes</a></h2> <ol> <li>"next" means the character "under" a box or underline style diff --git a/lynx_help/keystrokes/bashlike_edit_help.html b/lynx_help/keystrokes/bashlike_edit_help.html index b62e6cb3..821c826c 100644 --- a/lynx_help/keystrokes/bashlike_edit_help.html +++ b/lynx_help/keystrokes/bashlike_edit_help.html @@ -1,4 +1,4 @@ -<!-- $LynxId: bashlike_edit_help.html,v 1.10 2014/01/08 00:50:05 tom Exp $ --> +<!-- $LynxId: bashlike_edit_help.html,v 1.13 2017/04/28 21:04:38 tom Exp $ --> <!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01//EN"> <html> @@ -19,7 +19,25 @@ </head> <body> - <h2>Overview</h2> + <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>Lynx invokes a built-in <a href="edit_help.html">Line Editor</a> for entering strings in response to prompts, in forms, @@ -27,15 +45,16 @@ defined. Several sets of key-bindings can be offered by configuring with --enable-alt-bindings or by adding them in LYEditmap.c before compiling Lynx. If available, they may be - selected via the 'o'ptions menu, or by editing lineedit_mode in - the '.lynxrc' file.</p> + selected via the “o”ptions menu, or by editing + lineedit_mode in the “.lynxrc” file.</p> - <p>Note: setting emacs/vi keys ON has no direct effect on - line-editor bindings.</p> + <p><strong>Note:</strong> setting emacs/vi keys ON has no direct + effect on line-editor bindings.</p> - <p>This summarizes the <em>Bash-like Binding</em> keymap.</p> + <h2><a name="bash_bindings" id="bash_bindings">Bash-like + bindings</a></h2> - <h2>Basic commands</h2> + <p>This summarizes the <em>Bash-like Binding</em> keymap.</p> <pre> ENTER Input complete - Enter, RETURN TAB Completion / Next - TAB, Do (<em>see note 2</em>) @@ -70,7 +89,7 @@ PASS! Grow textarea - C-x g </pre> - <h2>Try it yourself</h2> + <h2><a name="examples" id="examples">Try it yourself</a></h2> <p>Here is a little textarea for practice:</p> @@ -84,7 +103,8 @@ or add text as you like, using the Line-Editor keys. </textarea><input type="reset" value="[reset content]"></p> </form> - <h2>Advanced emacs-like commands</h2> + <h2><a name="emacs_bindings" id="emacs_bindings">Emacs-like + commands</a></h2> <pre> TPOS Transpose characters - C-t @@ -94,7 +114,8 @@ or add text as you like, using the Line-Editor keys. YANK Insert text last killed (with KILLREG) - C-y </pre> - <h2>Comments on special keys</h2> + <h2><a name="special_keys" id="special_keys">Comments on special + keys</a></h2> <p><samp><dfn>C-</dfn><strong>key</strong> means Control+<strong><kbd>key</kbd></strong>. @@ -106,7 +127,7 @@ or add text as you like, using the Line-Editor keys. <ul> <li>First ESC, then the <strong><kbd>key</kbd></strong>. This - doesn't work with all systems or on all connections, and if it + does 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> @@ -126,7 +147,7 @@ or add text as you like, using the Line-Editor keys. vice versa.</li> </ul> - <h2>Notes</h2> + <h2><a name="notes" id="notes">Notes</a></h2> <ol> <li>"next" means the character "under" a box or underline style @@ -156,8 +177,8 @@ or add text as you like, using the Line-Editor keys. <li>Key is likely unavailable for Lynx, because it is interpreted by operating system, comm program, or curses library, or swallowed as part of escape sequence recognition. - Binding is provided for the benefit of those where this doesn't - apply.</li> + Binding is provided for the benefit of those where this does + not apply.</li> <li>where <strong>[FORM]</strong> is marked, indicates that the binding is effective only in form text fields. It is ignored by @@ -173,8 +194,11 @@ or add text as you like, using the Line-Editor keys. accessible with the key <kbd>K</kbd> for current information).</p> - <h2>Additional details on other keys, for the curious (very much - subject to change)</h2> + <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)] diff --git a/lynx_help/keystrokes/bookmark_help.html b/lynx_help/keystrokes/bookmark_help.html index 87187fd1..9eeb055b 100644 --- a/lynx_help/keystrokes/bookmark_help.html +++ b/lynx_help/keystrokes/bookmark_help.html @@ -1,4 +1,4 @@ -<!-- $LynxId: bookmark_help.html,v 1.8 2014/01/07 23:32:23 tom Exp $ --> +<!-- $LynxId: bookmark_help.html,v 1.10 2017/04/28 21:27:36 tom Exp $ --> <!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01//EN"> <html> @@ -15,22 +15,36 @@ </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>Updating within Lynx</h2> + <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 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>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 @@ -38,7 +52,8 @@ Menu</a>.</li> </ul> - <h2>Updating with a text editor</h2> + <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 diff --git a/lynx_help/keystrokes/cookie_help.html b/lynx_help/keystrokes/cookie_help.html index 0f7378b8..7ec6088c 100644 --- a/lynx_help/keystrokes/cookie_help.html +++ b/lynx_help/keystrokes/cookie_help.html @@ -1,4 +1,4 @@ -<!-- $LynxId: cookie_help.html,v 1.9 2014/01/07 09:14:46 tom Exp $ --> +<!-- $LynxId: cookie_help.html,v 1.11 2017/04/28 21:32:43 tom Exp $ --> <!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01//EN"> <html> @@ -15,7 +15,17 @@ </head> <body> - <h2>Overview</h2> + <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 @@ -32,11 +42,12 @@ 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> + <em>Cookie</em> MIME header. The “allow” setting for + accepting cookies from each domain (always, never, or via prompt) + also is indicated in the listing.</p> - <h2>Cookie Details Shown</h2> + <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 @@ -50,7 +61,8 @@ <em>Set-Cookie</em> MIME headers, those also are displayed in the listing.</p> - <h2>Removing Cookies</h2> + <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 @@ -58,10 +70,10 @@ <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> + <em>Gobbled</em>, or whether to change the “allow” + setting for that <em>domain</em>. Activating a cookie's + name=value link will cause that particular cookie to be + <em>Gobbled</em>. You will be prompted for confirmations of + deletions, to avoid any accidental <em>Gobbling</em>.</p> </body> </html> diff --git a/lynx_help/keystrokes/dired_help.html b/lynx_help/keystrokes/dired_help.html index bf5701be..51a169dc 100644 --- a/lynx_help/keystrokes/dired_help.html +++ b/lynx_help/keystrokes/dired_help.html @@ -1,4 +1,4 @@ -<!-- $LynxId: dired_help.html,v 1.9 2014/01/08 01:15:55 tom Exp $ --> +<!-- $LynxId: dired_help.html,v 1.11 2017/04/28 21:36:59 tom Exp $ --> <!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01//EN"> <html> @@ -15,12 +15,25 @@ </head> <body> - <h2>Overview</h2> + <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>Key bindings</h2> + <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> @@ -46,7 +59,7 @@ 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 + one highlighted. Press “<em>t</em>” again to untag a file. U)pload - Upload a file to the current directory using @@ -54,6 +67,9 @@ </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> @@ -67,7 +83,7 @@ </pre> </blockquote> - <h2>Notes</h2> + <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 diff --git a/lynx_help/keystrokes/edit_help.html b/lynx_help/keystrokes/edit_help.html index eb8b0c62..cc3983ad 100644 --- a/lynx_help/keystrokes/edit_help.html +++ b/lynx_help/keystrokes/edit_help.html @@ -1,4 +1,4 @@ -<!-- $LynxId: edit_help.html,v 1.17 2014/01/08 21:24:50 tom Exp $ --> +<!-- $LynxId: edit_help.html,v 1.20 2017/04/28 21:40:03 tom Exp $ --> <!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01//EN"> <html> @@ -15,7 +15,19 @@ </head> <body> - <h2>Overview</h2> + <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="#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 @@ -23,8 +35,8 @@ 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> + 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> @@ -45,7 +57,8 @@ <p>Note: setting emacs/vi keys ON has no effect on line-editor bindings.</p> - <h2>Regular Keymap</h2> + <h2><a name="regular_keymap" id="regular_keymap">Regular + Keymap</a></h2> <p>This is the <em>Default Binding</em> keymap:</p> <pre> @@ -75,7 +88,8 @@ </pre> - <h2>Editing Keymap</h2> + <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> (see note 3):</p> @@ -86,7 +100,7 @@ Grow textarea - Ctrl-X g </pre> - <h2>Notes</h2> + <h2><a name="notes" id="notes">Notes</a></h2> <ol> <li>"next" means the character "under" a box or underline style diff --git a/lynx_help/keystrokes/environments.html b/lynx_help/keystrokes/environments.html index 68425cb4..babf0a7a 100644 --- a/lynx_help/keystrokes/environments.html +++ b/lynx_help/keystrokes/environments.html @@ -1,4 +1,4 @@ -<!-- $LynxId: environments.html,v 1.16 2014/01/08 01:38:23 tom Exp $ --> +<!-- $LynxId: environments.html,v 1.21 2017/04/28 22:16:55 tom Exp $ --> <!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01//EN"> <html> @@ -15,9 +15,29 @@ </head> <body> - <h2>ENVIRONMENT</h2> + <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 + 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>. @@ -26,8 +46,8 @@ 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. +"#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 @@ -36,8 +56,7 @@ variables. </pre> - <h2><a name="env" id="env">Environment Variables Used By - Lynx</a></h2> + <h2><a name="env" id="env">Variables Used By Lynx</a></h2> <pre> COLORTERM If set, color capability for the terminal @@ -130,7 +149,7 @@ UNIX, it will override the contents of an /etc/organization file, if present. - PROTOCOL_proxy + <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 @@ -139,22 +158,22 @@ Each protocol used by <strong>Lynx</strong> (http, ftp, gopher, etc), can be mapped separately by setting environment variables of - the form PROTOCOL_proxy (literally: + the form <em>PROTOCOL</em>_proxy (literally: http_proxy, ftp_proxy, gopher_proxy, - etc), to "http://some.server.dom:port/". + etc), to “http://some.server.dom:port/”. See <a href= "#proxy">Proxy details and examples</a>. - WWW_access_GATEWAY + WWW_<em>access</em>_GATEWAY <strong>Lynx</strong> still supports use of gateway servers, with the servers specified - via "WWW_access_GATEWAY" variables - (where "access" is lower case and can - be "http", "ftp", "gopher" or "wais"), + 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 PROTOCOL_proxy + include a terminal “/” for gateways, + but do for proxies specified by <em>PROTOCOL</em>_proxy environment variables. See <a href= "#proxy">Proxy details</a>. @@ -164,52 +183,52 @@ any of the <strong>Lynx</strong> configuration files. </pre> - <h2><a name="setenv" id="setenv">Environment Variables Set or - Modified By Lynx</a></h2> + <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 + 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. + 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. + 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. + 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. + 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. + 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 + 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. + 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 @@ -228,7 +247,7 @@ <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 + 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 @@ -238,14 +257,14 @@ variables may also be changed. </pre> - <h2><a name="cgi" id="cgi">SIMULATED CGI SUPPORT</a></h2> + <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 + <p>When executing such “lynxcgi scripts” (if + enabled), the following variables may be set for simulating a CGI environment:</p> <pre> CONTENT_LENGTH @@ -286,8 +305,8 @@ should be consulted for general information on CGI script programming.</p> - <h2><a name="language" id="language">NATIVE LANGUAGE - SUPPORT</a></h2> + <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 @@ -332,8 +351,8 @@ <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> + 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> @@ -355,17 +374,20 @@ define/system NNTPSERVER "news.server.dom" <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 '/' + “WWW_access_GATEWAY”, where “access” is + lower case and can be “http”, “ftp”, + “gopher” or “wais”. Most of the gateway + servers have been discontinued, but + “http://www.w3.org:8001” is available for wais + searches (note that you do not include a terminal “/” for gateways, but do for proxies; see below).</p> <p><strong>Lynx</strong> version 2.2 and beyond supports the use of proxy servers that can act as firewall gateways and caching servers. They are preferable to the older gateway servers. Each protocol used by <strong>Lynx</strong> can be mapped separately - using PROTOCOL_proxy environment variables of the form:</p> + using <em>PROTOCOL</em>_proxy environment variables as shown + below:</p> <dl> <dt>UNIX</dt> @@ -373,20 +395,20 @@ define/system NNTPSERVER "news.server.dom" <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/" +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> @@ -396,37 +418,38 @@ setenv cso_proxy "http://some.server.dom:port/" <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 "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/" +define "nntp_proxy" "http://some.server.dom:port/" +define "wais_proxy" "http://some.server.dom:port/" +define "finger_proxy" "http://some.server.dom:port/" +define "cso_proxy" "http://some.server.dom:port/" </pre> </blockquote> <p>(Encase *BOTH* strings in double-quotes to maintain lower - case for the PROTOCOL_proxy variable and for the http access - type; include /system if you want proxying for all clients on - your system.)</p> + 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> + 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> @@ -449,20 +472,22 @@ define "no_proxy" "host.domain.dom, domain1.dom, domain2" <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> + “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> + 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 @@ -473,8 +498,8 @@ define "no_proxy" "host.domain.dom, domain1.dom, domain2" <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> + 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 @@ -482,18 +507,19 @@ define "no_proxy" "host.domain.dom, domain1.dom, domain2" <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>(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> + 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. @@ -511,14 +537,17 @@ define "no_proxy" "host.domain.dom, domain1.dom, domain2" <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> + “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>In lynx_386, a typical batch file might look like: +</pre> + + <p>In lynx_386, a typical batch file might look like:</p> <pre> @echo off set HOME=f:/lynx2-8 diff --git a/lynx_help/keystrokes/follow_help.html b/lynx_help/keystrokes/follow_help.html index 4f18fc29..b9648c4b 100644 --- a/lynx_help/keystrokes/follow_help.html +++ b/lynx_help/keystrokes/follow_help.html @@ -1,4 +1,4 @@ -<!-- $LynxId: follow_help.html,v 1.13 2014/01/07 01:38:19 tom Exp $ --> +<!-- $LynxId: follow_help.html,v 1.16 2017/04/28 21:42:43 tom Exp $ --> <!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01//EN"> <html> @@ -15,7 +15,24 @@ </head> <body> - <h2>Overview</h2> + <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 @@ -37,7 +54,8 @@ potentially multiple digit number corresponding to an indicated link number.</p> - <h2>Zero and other digits</h2> + <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, @@ -54,7 +72,7 @@ <em>F_LINK_NUM</em> command for invoking the <em>Follow link (or goto link or page) number:</em> prompt.</p> - <h2>Suffixes</h2> + <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> @@ -72,26 +90,27 @@ <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> + <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> + <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 @@ -123,7 +142,8 @@ </dd> </dl> - <h2>Specifics for Form Fields</h2> + <h2><a name="form_fields" id="form_fields">Specifics for Form + Fields</a></h2> <p>Numbers are associated with form fields only when</p> @@ -150,26 +170,27 @@ 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>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>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> + “<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 @@ -182,10 +203,11 @@ whether or not <em>keypad mode</em> is <em>Form fields are numbered</em> or <em>Links and form fields are numbered</em> since options are numbered internally. If form field numbering is - turned off, the option numbers won't appear on screen, but the + turned off, the option numbers will not appear on screen, but the user can still navigate using these commands.</p> - <h2>Hidden Links</h2> + <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 @@ -230,34 +252,39 @@ <em>-hiddenlinks</em> flag at all is equivalent to <em>-hiddenlinks=listonly</em>.</p> - <h2>Navigating to Hidden Links</h2> + <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 + 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> + 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> + nor assigns it a number for the F_LINK_NUM + (“<em>0</em>”) command and <em>Form fields are + numbered</em> or <em>Links and form fields are numbered</em> + keypad mode handling, nor includes an entry for it in the menus + created for the LIST (“<em>l</em>”) or ADDRLIST + (“<em>A</em>”) commands. However, the HIDDEN + name/value pairs are included in any displays of submitted form + content in the <em>Information about the current document</em> + that is invoked by the INFO (“<em>=</em>”) + command.</p> </body> </html> diff --git a/lynx_help/keystrokes/gopher_types_help.html b/lynx_help/keystrokes/gopher_types_help.html index d71ca008..2f5c16ec 100644 --- a/lynx_help/keystrokes/gopher_types_help.html +++ b/lynx_help/keystrokes/gopher_types_help.html @@ -1,4 +1,4 @@ -<!-- $LynxId: gopher_types_help.html,v 1.11 2014/01/09 00:17:28 tom Exp $ --> +<!-- $LynxId: gopher_types_help.html,v 1.12 2017/04/28 20:47:13 tom Exp $ --> <!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01//EN"> <html> @@ -15,7 +15,14 @@ </head> <body> - <h1>Listing of Gopher types</h1> + <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> diff --git a/lynx_help/keystrokes/history_help.html b/lynx_help/keystrokes/history_help.html index dd396093..b3992cce 100644 --- a/lynx_help/keystrokes/history_help.html +++ b/lynx_help/keystrokes/history_help.html @@ -1,4 +1,4 @@ -<!-- $LynxId: history_help.html,v 1.7 2014/01/07 09:17:47 tom Exp $ --> +<!-- $LynxId: history_help.html,v 1.9 2017/04/28 21:44:00 tom Exp $ --> <!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01//EN"> <html> @@ -15,7 +15,15 @@ </head> <body> - <h2>Overview</h2> + <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, @@ -27,7 +35,7 @@ link within that document, it <em>will</em> be in the history stack.</p> - <h2>Navigation</h2> + <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 @@ -47,7 +55,7 @@ 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> + “<em>d</em>”ownloaded or passed to a helper + application, and thus were not included in the history stack.</p> </body> </html> diff --git a/lynx_help/keystrokes/keystroke_help.html b/lynx_help/keystrokes/keystroke_help.html index 17912452..0191b69b 100644 --- a/lynx_help/keystrokes/keystroke_help.html +++ b/lynx_help/keystrokes/keystroke_help.html @@ -1,4 +1,4 @@ -<!-- $LynxId: keystroke_help.html,v 1.19 2014/01/07 01:45:02 tom Exp $ --> +<!-- $LynxId: keystroke_help.html,v 1.21 2017/04/28 21:52:57 tom Exp $ --> <!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01//EN"> <html> @@ -15,140 +15,167 @@ </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> - <a name="movement" href="movement_help.html" id= -"movement">MOVEMENT</a>: Down arrow - Highlight next topic - Up arrow - Highlight previous topic - Right arrow, - Jump to highlighted topic - Return, Enter - Follow selected link - Left arrow - Return to previous topic - - <a name="scrolling" href="scrolling_help.html" id= -"scrolling">SCROLLING</a>: + - Scroll down to next page (Page-Down) - - - Scroll up to previous page (Page-Up) - SPACE - Scroll down to next page (Page-Down) - b - Scroll up to previous page (Page-Up) - 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 - - <a name="dired" href="dired_help.html" id= -"dired">DIRED</a>: c - Create a new file - d - Download selected file - e - Edit selected file - f - Show a full menu of options for current file - 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 - - <a name="other" href="other_help.html" id= -"other">OTHER</a>: ? (or h) - Help (this screen) - a - Add the current link to a bookmark file - c - Send a comment to the document owner - d - Download the current link - 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= + 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= + 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= + 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= + 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= + 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= + 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-V - Outside of a text input line or field, - switch to <a href= + = - 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-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= + - 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. + 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= + 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. + - Outside of text input or field, + undo returning to previous topic. - CTRL-G - Cancel input or transfer + 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= + 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= + CTRL-X - Invoke the <a href= "../Lynx_users_guide.html#Cache">Cache Jar Page</a> - numbers - Invoke the prompt - <a href= + <em>numbers</em> - Invoke the prompt + <a href= "follow_help.html">Follow link (or goto link or page) number:</a> - or the - <a href= + or the + <a href= "follow_help.html#select-option">Select option (or page) number:</a> - prompt + prompt </pre> </body> </html> diff --git a/lynx_help/keystrokes/movement_help.html b/lynx_help/keystrokes/movement_help.html index 18277ee0..60d29165 100644 --- a/lynx_help/keystrokes/movement_help.html +++ b/lynx_help/keystrokes/movement_help.html @@ -1,4 +1,4 @@ -<!-- $LynxId: movement_help.html,v 1.9 2014/01/08 21:36:06 tom Exp $ --> +<!-- $LynxId: movement_help.html,v 1.10 2017/04/28 21:55:16 tom Exp $ --> <!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01//EN"> <html> @@ -15,7 +15,15 @@ </head> <body> - <h2>Keystroke Commands</h2> + <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 @@ -38,7 +46,7 @@ previous topic. </pre> - <h2>Notes</h2> + <h2><a name="notes" id="notes">Notes</a></h2> <ol> <li>If <em>VI Keys</em> are enabled from the options menu or diff --git a/lynx_help/keystrokes/option_help.html b/lynx_help/keystrokes/option_help.html index b9148607..19b16f5c 100644 --- a/lynx_help/keystrokes/option_help.html +++ b/lynx_help/keystrokes/option_help.html @@ -1,4 +1,4 @@ -<!-- $LynxId: option_help.html,v 1.28 2014/01/08 22:28:11 tom Exp $ --> +<!-- $LynxId: option_help.html,v 1.32 2017/04/28 21:12:53 tom Exp $ --> <!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01//EN"> <html> @@ -15,6 +15,8 @@ </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 @@ -23,153 +25,157 @@ have been compiled in or chosen in <code><strong>lynx.cfg</strong></code>.</p> - <ul> - <li> - <a href="#GP">General Preferences</a> + <div class="nav"> + <ul> + <li><a href="#overview">Options Menu</a></li> - <ul> - <li><a href="#UM">User Mode</a></li> + <li> + <a href="#GP">General Preferences</a> - <li><a href="#ED">Editor</a></li> + <ul> + <li><a href="#UM">User Mode</a></li> - <li><a href="#ST">Type of Search</a></li> - </ul> - </li> + <li><a href="#ED">Editor</a></li> - <li> - <a href="#SP">Security and Privacy</a> + <li><a href="#ST">Type of Search</a></li> + </ul> + </li> - <ul> - <li><a href="#CK">Cookies</a></li> + <li> + <a href="#SP">Security and Privacy</a> - <li><a href="#IK">Invalid-Cookie Prompting</a></li> + <ul> + <li><a href="#CK">Cookies</a></li> - <li><a href="#SK">SSL Prompting</a></li> - </ul> - </li> + <li><a href="#IK">Invalid-Cookie Prompting</a></li> - <li> - <a href="#KI">Keyboard Input</a> + <li><a href="#SK">SSL Prompting</a></li> + </ul> + </li> - <ul> - <li><a href="#KM">Keypad mode</a></li> + <li> + <a href="#KI">Keyboard Input</a> - <li><a href="#EM">Emacs keys</a></li> + <ul> + <li><a href="#KM">Keypad mode</a></li> - <li><a href="#VI">VI keys</a></li> + <li><a href="#EM">Emacs keys</a></li> - <li><a href="#LE">Line edit style</a></li> - </ul> - </li> + <li><a href="#VI">VI keys</a></li> - <li> - <a href="#DP">Display and Character Set</a> + <li><a href="#LE">Line edit style</a></li> + </ul> + </li> - <ul> - <li><a href="#LC">Use locale-based character set</a></li> + <li> + <a href="#DP">Display and Character Set</a> - <li><a href="#H5">Use HTML5 charset replacements</a></li> + <ul> + <li><a href="#LC">Use locale-based character set</a></li> - <li><a href="#DC">Display Character set</a></li> + <li><a href="#H5">Use HTML5 charset replacements</a></li> - <li><a href="#AD">Assumed document character set</a></li> + <li><a href="#DC">Display Character set</a></li> - <li><a href="#JK">Raw 8-bit or CJK mode</a></li> + <li><a href="#AD">Assumed document character set</a></li> - <li><a href="#DV">X DISPLAY variable</a></li> - </ul> - </li> + <li><a href="#JK">Raw 8-bit or CJK mode</a></li> - <li> - <a href="#AP">Document Appearance</a> + <li><a href="#DV">X DISPLAY variable</a></li> + </ul> + </li> - <ul> - <li><a href="#SC">Show color</a></li> + <li> + <a href="#AP">Document Appearance</a> - <li><a href="#CS">Color style</a></li> + <ul> + <li><a href="#SC">Show color</a></li> - <li><a href="#C0">Default colors</a></li> + <li><a href="#CS">Color style</a></li> - <li><a href="#CL">Show cursor for current link or - option</a></li> + <li><a href="#C0">Default colors</a></li> - <li><a href="#UK">Underline links</a></li> + <li><a href="#CL">Show cursor for current link or + option</a></li> - <li><a href="#SS">Show scrollbar</a></li> + <li><a href="#UK">Underline links</a></li> - <li><a href="#PU">Pop-ups for select fields</a></li> + <li><a href="#SS">Show scrollbar</a></li> - <li><a href="#tagsoup">HTML error recovery</a></li> + <li><a href="#PU">Pop-ups for select fields</a></li> - <li><a href="#BH">Bad HTML messages</a></li> + <li><a href="#tagsoup">HTML error recovery</a></li> - <li><a href="#SI">Show Images</a></li> + <li><a href="#BH">Bad HTML messages</a></li> - <li><a href="#VB">Verbose Images</a></li> - </ul> - </li> + <li><a href="#SI">Show Images</a></li> - <li> - <a href="#HP">Headers Transferred to Remote Servers</a> + <li><a href="#VB">Verbose Images</a></li> + </ul> + </li> - <ul> - <li><a href="#PM">Personal mail address</a></li> + <li> + <a href="#HP">Headers Transferred to Remote Servers</a> - <li><a href="#PN">Personal name for mail</a></li> + <ul> + <li><a href="#PM">Personal mail address</a></li> - <li><a href="#PW">Password for anonymous ftp</a></li> + <li><a href="#PN">Personal name for mail</a></li> - <li><a href="#PT">Preferred media type</a></li> + <li><a href="#PW">Password for anonymous ftp</a></li> - <li><a href="#PE">Preferred encoding</a></li> + <li><a href="#PT">Preferred media type</a></li> - <li><a href="#PC">Preferred Document Charset</a></li> + <li><a href="#PE">Preferred encoding</a></li> - <li><a href="#PL">Preferred Document Language</a></li> + <li><a href="#PC">Preferred Document Charset</a></li> - <li><a href="#SA">Send User-Agent header</a></li> + <li><a href="#PL">Preferred Document Language</a></li> - <li><a href="#UA">User Agent</a></li> - </ul> - </li> + <li><a href="#SA">Send User-Agent header</a></li> - <li> - <a href="#LP">Listing and Accessing Files</a> + <li><a href="#UA">User Agent</a></li> + </ul> + </li> - <ul> - <li><a href="#PF">Use Passive FTP</a></li> + <li> + <a href="#LP">Listing and Accessing Files</a> - <li><a href="#FT">FTP sort criteria</a></li> + <ul> + <li><a href="#PF">Use Passive FTP</a></li> - <li><a href="#LD">Local directory sort criteria</a></li> + <li><a href="#FT">FTP sort criteria</a></li> - <li><a href="#LO">Local directory sort order</a></li> + <li><a href="#LD">Local directory sort criteria</a></li> - <li><a href="#DF">Show dot files</a></li> + <li><a href="#LO">Local directory sort order</a></li> - <li><a href="#PZ">Pause when showing message</a></li> + <li><a href="#DF">Show dot files</a></li> - <li><a href="#LL">Execution links</a></li> + <li><a href="#PZ">Pause when showing message</a></li> - <li><a href="#TX">Show transfer rate</a></li> - </ul> - </li> + <li><a href="#LL">Execution links</a></li> - <li>Special Files and Screens + <li><a href="#TX">Show transfer rate</a></li> + </ul> + </li> - <ul> - <li><a href="#MB">Multi-bookmarks</a></li> + <li>Special Files and Screens - <li><a href="#BF">Bookmark file</a></li> + <ul> + <li><a href="#MB">Multi-bookmarks</a></li> - <li><a href="#AZ">Auto Session</a></li> + <li><a href="#BF">Bookmark file</a></li> - <li><a href="#SZ">Session file</a></li> + <li><a href="#AZ">Auto Session</a></li> - <li><a href="#VP">Visited Pages</a></li> - </ul> - </li> - </ul> + <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> @@ -249,10 +255,10 @@ <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, + <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 @@ -260,9 +266,9 @@ <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>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, @@ -313,8 +319,8 @@ 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> + 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> @@ -329,11 +335,12 @@ 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> + “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> @@ -357,9 +364,9 @@ <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> + 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 @@ -375,15 +382,15 @@ 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> + 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> @@ -462,8 +469,8 @@ <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> + 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> @@ -491,11 +498,11 @@ <h3><a name="SI" id="SI">Show Images</a></h3> - <p>This option combines the effects of the `*' & `[' keys as - follows:</p> + <p>This option combines the effects of the “*” & + “[” keys as follows:</p> <pre> <em>ignore</em> all images which lack an ALT= text string, - <em>show labels</em>, e.g. [INLINE] — see `Verbose Images' below — , + <em>show labels</em>, e.g. [INLINE] — see “Verbose Images” below — , <em>use links</em> for every image, enabling downloading. </pre> @@ -521,7 +528,7 @@ <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> + also be sent to HTTP servers in a “from:” field.</p> <h3><a name="PN" id="PN">Personal mail name</a></h3> @@ -592,17 +599,17 @@ 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> + 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> + 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> @@ -615,19 +622,20 @@ -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> + “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> + 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> @@ -639,8 +647,9 @@ <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> + 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> @@ -682,7 +691,8 @@ <dt>By type</dt> - <dd>by filename suffix, e.g., the text beginning with '.'</dd> + <dd>by filename suffix, e.g., the text beginning with + “.”</dd> <dt>By user</dt> @@ -706,10 +716,11 @@ <h3><a name="LL" id="LL">Execution links</a></h3> - <p>If set to 'ALWAYS ON', Lynx will locally execute commands - contained inside any links. This can be HIGHLY DANGEROUS, so it - is recommended that they remain 'ALWAYS OFF' or 'FOR LOCAL FILES - ONLY'.</p> + <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> @@ -737,7 +748,8 @@ <ul> <li>When OFF, the default bookmark file is used for the - 'v'iew-bookmarks and 'a'dd-bookmark link commands.</li> + “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, @@ -745,9 +757,9 @@ 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> + 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> @@ -756,19 +768,21 @@ <ul> <li>If non-empty and multi-bookmarks is OFF, it specifies your - default '<a href="bookmark_help.html">Bookmark file</a>'.</li> + 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> + <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> + “./” 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> + <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> diff --git a/lynx_help/keystrokes/other_help.html b/lynx_help/keystrokes/other_help.html index 38e4bded..a33cb406 100644 --- a/lynx_help/keystrokes/other_help.html +++ b/lynx_help/keystrokes/other_help.html @@ -1,4 +1,4 @@ -<!-- $LynxId: other_help.html,v 1.15 2014/01/10 20:51:10 tom Exp $ --> +<!-- $LynxId: other_help.html,v 1.18 2017/04/28 21:57:13 tom Exp $ --> <!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01//EN"> <html> @@ -15,7 +15,14 @@ </head> <body> - <h2>Summary of Commands</h2> + <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= @@ -71,7 +78,7 @@ o - Brings up a list of settable <a href= "option_help.html">options</a>. - q - Quits <strong>Lynx</strong>. ('Q' quits without asking) + q - Quits <strong>Lynx</strong>. (“Q” quits without asking) / - Search for a string of characters in the current document (case insensitive or case sensitive @@ -140,7 +147,7 @@ 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'll be ignored). If image_links mode is toggled on, + 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. @@ -151,7 +158,7 @@ requests always are sent to the http server, i.e., <strong>Lynx</strong> does not retrieve any previous server replies from its cache. Note that for form submissions, http servers vary - in whether they'll treat HEAD requests as valid and return + 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. diff --git a/lynx_help/keystrokes/print_help.html b/lynx_help/keystrokes/print_help.html index 2bd58a0e..d57563fc 100644 --- a/lynx_help/keystrokes/print_help.html +++ b/lynx_help/keystrokes/print_help.html @@ -1,4 +1,4 @@ -<!-- $LynxId: print_help.html,v 1.8 2014/01/07 23:47:13 tom Exp $ --> +<!-- $LynxId: print_help.html,v 1.9 2017/04/28 21:58:48 tom Exp $ --> <!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01//EN"> <html> @@ -15,7 +15,15 @@ </head> <body> - <h2>Overview</h2> + <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 @@ -23,7 +31,8 @@ removed. The number of options depends on the level of printing that your system allows.</p> - <h2>Print-command Options</h2> + <h2><a name="command_options" id="command_options">Print-command + Options</a></h2> <p>The following print options may be available:</p> diff --git a/lynx_help/keystrokes/scrolling_help.html b/lynx_help/keystrokes/scrolling_help.html index cedfac86..439fae77 100644 --- a/lynx_help/keystrokes/scrolling_help.html +++ b/lynx_help/keystrokes/scrolling_help.html @@ -1,4 +1,4 @@ -<!-- $LynxId: scrolling_help.html,v 1.10 2014/01/08 00:25:16 tom Exp $ --> +<!-- $LynxId: scrolling_help.html,v 1.12 2017/04/28 22:01:41 tom Exp $ --> <!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01//EN"> <html> @@ -15,12 +15,32 @@ </head> <body> - <h2>Paging shortcuts</h2> + <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 + 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 @@ -28,7 +48,8 @@ </pre> </blockquote> - <h2>Keypad shortcuts</h2> + <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 @@ -50,7 +71,8 @@ </pre> </blockquote> - <h2>Control-characters</h2> + <h2><a name="control_keys" id= + "control_keys">Control-characters</a></h2> <blockquote> <pre> @@ -72,7 +94,8 @@ </pre> </blockquote> - <h2>Ordinary characters</h2> + <h2><a name="other_keys" id="other_keys">Ordinary + characters</a></h2> <blockquote> <pre> diff --git a/lynx_help/keystrokes/test_display.html b/lynx_help/keystrokes/test_display.html index 8cc4ab21..eae010c6 100644 --- a/lynx_help/keystrokes/test_display.html +++ b/lynx_help/keystrokes/test_display.html @@ -1,4 +1,4 @@ -<!-- $LynxId: test_display.html,v 1.9 2014/01/08 00:05:32 tom Exp $ --> +<!-- $LynxId: test_display.html,v 1.11 2017/04/28 22:04:57 tom Exp $ --> <!-- do not use tidy for this page --> <!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01//EN"> @@ -16,6 +16,24 @@ </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 @@ -23,13 +41,17 @@ settings.</p> <blockquote> - <p><em>Press 'o' for Options menu and change "Display character - set"</em>.<br> + <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 @@ -59,7 +81,5 @@ 0xFB01 fi # LATIN SMALL LIGATURE FI </pre> - - <p>This is only a quick test to see obvious problems.</p> </body> </html> diff --git a/lynx_help/keystrokes/visited_help.html b/lynx_help/keystrokes/visited_help.html index a6dae243..01fa9ccc 100644 --- a/lynx_help/keystrokes/visited_help.html +++ b/lynx_help/keystrokes/visited_help.html @@ -1,4 +1,4 @@ -<!-- $LynxId: visited_help.html,v 1.9 2014/01/07 09:26:22 tom Exp $ --> +<!-- $LynxId: visited_help.html,v 1.11 2017/04/28 22:09:23 tom Exp $ --> <!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01//EN"> <html> @@ -15,21 +15,31 @@ </head> <body> - <h2>Overview</h2> + <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> + normally is mapped to uppercase “<em>V</em>”. The + list of Visited Links is normally in order of recency (most + recently visited links first), without repetitions in the list if + a link was visited more than once during the session (unless the + URLs differ due to appended fragments), and is supplementary to + the <a href="history_help.html">History Page</a>.</p> - <h2>Navigation</h2> + <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 @@ -40,11 +50,12 @@ <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> + “<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>Configuration</h2> + <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= diff --git a/lynx_help/keystrokes/xterm_help.html b/lynx_help/keystrokes/xterm_help.html index 0339f2dc..210d7ce4 100644 --- a/lynx_help/keystrokes/xterm_help.html +++ b/lynx_help/keystrokes/xterm_help.html @@ -1,4 +1,4 @@ -<!-- $LynxId: xterm_help.html,v 1.9 2014/01/09 00:17:28 tom Exp $ --> +<!-- $LynxId: xterm_help.html,v 1.10 2017/04/28 20:47:13 tom Exp $ --> <!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01//EN"> <html> @@ -15,7 +15,15 @@ </head> <body> - <h1>X Terminal Help</h1> + <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 @@ -33,8 +41,10 @@ like X Window terminals and are frequently used as X terminals.</p> + <h2>Notes</h2> + <dl> - <dt>Note:</dt> + <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 diff --git a/lynx_help/lynx-dev.html b/lynx_help/lynx-dev.html index d178e499..077ea462 100644 --- a/lynx_help/lynx-dev.html +++ b/lynx_help/lynx-dev.html @@ -1,4 +1,4 @@ -<!-- $LynxId: lynx-dev.html,v 1.17 2015/09/19 17:36:28 tom Exp $ --> +<!-- $LynxId: lynx-dev.html,v 1.18 2017/04/28 16:47:05 tom Exp $ --> <!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01//EN"> <html> @@ -25,7 +25,7 @@ <p><strong>Lynx</strong> is maintained and improved by an international co-operative of volunteers. Newcomers are welcome - to join the group: you needn't be a super programmer, but you + to join the group: you need not be a super programmer, but you should be prepared to listen and learn, as well as to contribute patches if you can. Since everyone is a volunteer, you will usually be expected to try to implement any suggestions you @@ -84,9 +84,9 @@ to <a href="mailto:lynx-dev@nongnu.org"> the list</a>. Since all subscribers are volunteers, you depend on their goodwill and will be more likely to get a response if you give the e-mail a - meaningful `Subject' and include details of your version of - <strong>Lynx</strong>, hardware and software. You can check the - Archive to find any responses.</p> + meaningful “Subject” and include details of your + version of <strong>Lynx</strong>, hardware and software. You can + check the Archive to find any responses.</p> <p>Messages from non-subscribers are not immediately distributed to avoid spam. Usually, if your message appears genuine, it will diff --git a/lynx_help/lynx_url_support.html b/lynx_help/lynx_url_support.html index ad4de44d..78849c23 100644 --- a/lynx_help/lynx_url_support.html +++ b/lynx_help/lynx_url_support.html @@ -1,4 +1,4 @@ -<!-- $LynxId: lynx_url_support.html,v 1.34 2015/05/07 00:18:49 tom Exp $ --> +<!-- $LynxId: lynx_url_support.html,v 1.36 2017/04/28 16:47:05 tom Exp $ --> <!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01//EN"> <html> @@ -67,13 +67,13 @@ </ul> <p>When entering a URL on the command line to be used as the - <em>startfile</em>, or at the prompt for a '<em>g</em>'oto entry, - a partial host field can be used and the scheme field can be - omitted if the scheme and fully qualified domain name can be - constructed internally by using the URL_DOMAIN_PREFIXES and - URL_DOMAIN_SUFFIXES definitions in the <strong>Lynx</strong> - configuration file. See the explanation of those definitions and - their use in your <em>lynx.cfg</em>.</p> + <em>startfile</em>, or at the prompt for a + “<em>g</em>”oto entry, a partial host field can be + used and the scheme field can be omitted if the scheme and fully + qualified domain name can be constructed internally by using the + URL_DOMAIN_PREFIXES and URL_DOMAIN_SUFFIXES definitions in the + <strong>Lynx</strong> configuration file. See the explanation of + those definitions and their use in your <em>lynx.cfg</em>.</p> <p>For example, <em>wfbr</em> will be treated as <em>http://www.wfbr.edu/</em>, and <em>wfbr/dir/lynx</em> will be @@ -93,9 +93,9 @@ <em>file://localhost/current/default/directory</em>.</p> <p>These expansions are <em>SOLELY</em> for <em>startfile</em> or - '<em>g</em>'oto entries! Any partial or relative URLs within HTML - documents are resolved according to the rules specified in - RFC1808 and subsequent IETF drafts.</p> + “<em>g</em>”oto entries! Any partial or relative URLs + within HTML documents are resolved according to the rules + specified in RFC1808 and subsequent IETF drafts.</p> <hr> <h2><a name="http_url" id="http_url">The <em>http</em> and @@ -272,16 +272,17 @@ For anonymous ftp, <strong>Lynx</strong> uses your <em>personal_mail_address</em> (user@host) as the <em>password</em> if it has been defined via the - '<em>o</em>'ptions menu. Otherwise, <strong>Lynx</strong> uses - the dummy password <em>WWWUser</em>. (A password can also be - embedded in the URL, by replacing <em>username</em> with - <em>username:password</em>. This is strongly discouraged for - 'real' passwords that must be kept secret, since URLs with the - completely unencrypted <em>password</em> may show up on the - screen, in HISTORY and LIST pages etc., and may even become - visible to remote sites for example through Referer headers.) Do - not include the <em>@</em> if neither <em>username</em> nor - <em>:password</em> is included.</p> + “<em>o</em>”ptions menu. Otherwise, + <strong>Lynx</strong> uses the dummy password <em>WWWUser</em>. + (A password can also be embedded in the URL, by replacing + <em>username</em> with <em>username:password</em>. This is + strongly discouraged for “real” passwords that must + be kept secret, since URLs with the completely unencrypted + <em>password</em> may show up on the screen, in HISTORY and LIST + pages etc., and may even become visible to remote sites for + example through Referer headers.) Do not include the <em>@</em> + if neither <em>username</em> nor <em>:password</em> is + included.</p> <p>The <em>;type=</em> parameter can be used with value <em>D</em>, <em>I</em>, or <em>A</em> to force handling of the @@ -547,17 +548,17 @@ <p>If <em>ENCTYPE="text/plain"</em> is specified for a FORM with a mailto ACTION, <strong>Lynx</strong> will not hex escape the name=value pairs of the FORM's content, and will use physical - newlines instead of '<em>&</em>' or '<em>;</em>' to separate - the pairs, so that the content will be readable directly. - Otherwise, <strong>Lynx</strong> will mail the content with the - default:</p> + newlines instead of “<em>&</em>” or + “<em>;</em>” to separate the pairs, so that the + content will be readable directly. Otherwise, + <strong>Lynx</strong> will mail the content with the default:</p> <pre> - <em>ENCTYPE="application/x-www-form-urlencoded"</em> ('<em>&</em>' separates pairs) + <em>ENCTYPE="application/x-www-form-urlencoded"</em> (“<em>&</em>” separates pairs) </pre> <p>or:</p> <pre> - <em>ENCTYPE="application/sgml-form-urlencoded"</em> ('<em>;</em>' separates pairs) + <em>ENCTYPE="application/sgml-form-urlencoded"</em> (“<em>;</em>” separates pairs) </pre> <p>if the latter was indicated.</p> @@ -694,13 +695,13 @@ </pre> <p>where <em>//localhost</em> is optional and always implied; the - full path should be specified, as `~' is not recognized; if the - script is in the directory <strong>Lynx</strong> was started - from, the simple file name is adequate. The output of the script - should be text/html and is rendered and displayed by - <strong>Lynx</strong>. Restrictions on use of lynxcgi and on - acceptable paths can be imposed in <em>userdefs.h</em> and - <em>lynx.cfg</em>, qv.</p> + full path should be specified, as “~” is not + recognized; if the script is in the directory + <strong>Lynx</strong> was started from, the simple file name is + adequate. The output of the script should be text/html and is + rendered and displayed by <strong>Lynx</strong>. Restrictions on + use of lynxcgi and on acceptable paths can be imposed in + <em>userdefs.h</em> and <em>lynx.cfg</em>, qv.</p> <p>This is a Lynxism and should be used only in local documents intended solely for <strong>Lynx</strong>, or for limited local @@ -748,8 +749,8 @@ behavior may be modified without notice, or the context in which it is allowed may change.</li> - <li>If it doesn't work as expected when used outside of the - intended purpose, don't expect anyone to "fix" it.</li> + <li>If it does not work as expected when used outside of the + intended purpose, do not expect anyone to "fix" it.</li> </ul> <p>For example, tempting though it might be, do not use @@ -759,8 +760,8 @@ <em>Review your <A HREF="LYNXKEYMAP:">Keymap</A></em> </pre> - <p>(No, they won't do any harm. Yes, they work. But don't rely on - it.)</p> + <p>(No, they will not do any harm. Yes, they work. But do not + rely on it.)</p> <p>If you must try one, the second is OK from the command line:<br></p> @@ -768,9 +769,10 @@ <em>lynx LYNXKEYMAP:</em> </pre> - <p>But within <strong>Lynx</strong>, use the '<em>K</em>' - keystroke command. Sometimes it may be convenient to use a - private scheme with '<em>g</em>'oto, as in:</p> + <p>But within <strong>Lynx</strong>, use the + “<em>K</em>” keystroke command. Sometimes it may be + convenient to use a private scheme with + “<em>g</em>”oto, as in:</p> <pre> <em>g LYNXMESSAGES:</em> <em>g LYNXCOMPILEOPTS:</em> |