diff options
| author | Mats O Jansson <maja@cvs.openbsd.org> | 2000-03-25 18:17:20 +0000 |
|---|---|---|
| committer | Mats O Jansson <maja@cvs.openbsd.org> | 2000-03-25 18:17:20 +0000 |
| commit | eebca53173b43fcb801ad06804b1b183038298d2 (patch) | |
| tree | 6ff7bc38513004836052fce9056c48bb680167a3 /gnu/usr.bin/lynx/lynx_help/keystrokes | |
| parent | 0270bc013175ccc71004e1c5f79171acbbc9ae3d (diff) | |
Upgrade to Lynx 2.8.2. -moj
Diffstat (limited to 'gnu/usr.bin/lynx/lynx_help/keystrokes')
10 files changed, 1063 insertions, 334 deletions
diff --git a/gnu/usr.bin/lynx/lynx_help/keystrokes/alt_edit_help.html b/gnu/usr.bin/lynx/lynx_help/keystrokes/alt_edit_help.html new file mode 100644 index 00000000000..bd79c6e89cd --- /dev/null +++ b/gnu/usr.bin/lynx/lynx_help/keystrokes/alt_edit_help.html @@ -0,0 +1,54 @@ +<!DOCTYPE html public "-//IETF//DTD HTML 3.0//EN"> +<html> +<head> +<title>Lynx Line Editor Alternate Key Binding</title> +<link rev="made" href="mailto:lynx-dev@sig.net"> +</head> +<body> +<h1>+++ALTERNATE BINDINGS+++</h1> + +Lynx invokes a built-in <em>Line Editor</em> for entering strings in +response to prompts, in forms, and for email messages if an external editor +has not been defined. Administrators can offer additional alternate key +bindings 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>Note: setting emacs/vi keys ON has no effect on line-editor bindings. + +<p>This is the <em>Alternate Bindings</em> keymap: + +<p><pre> + ENTER Input complete - RETURN + TAB Input complete - TAB, Do + ABORT Input cancelled - Ctrl-G, Ctrl-O, (Ctrl-C on some systems) + ERASE Erase the line - Ctrl-U + + BACK Cursor back char - Left-Arrow, Ctrl-B + FORW Cursor forward char - Right-Arrow, Ctrl-F + BACKW Cursor back word - Ctrl-P + FORWW Cursor forward word - Ctrl-N + BOL Go to begin of line - Ctrl-A, Home, Find + EOL Go to end of line - Ctrl-E, End, Select + + DELP Delete prev char - Ctrl-H, DELETE, Remove + DELN Delete next [1] char - Ctrl-D + DELPW Delete prev word - Ctrl-R + DELNW Delete next word - Ctrl-T + DELBL Delete to beg of line - Ctrl-X + DELEL Delete to end of line - Ctrl-K + + UPPER Upper case the line - Ctrl-^ + LOWER Lower case the line - Ctrl-_ + + LKCMD Invoke cmd prompt - Ctrl-V (in form text fields, only) [2] + +[1] "next" means the character "under" a box or underline style cursor; it + means "to the immediate right of" an I-beam (between characters) type + cursor. + +[2] Follow Ctrl-V with the key "e" bound to the EDIT function, + to edit the form's textarea field using an external editor. +</pre> +</body> +</html> diff --git a/gnu/usr.bin/lynx/lynx_help/keystrokes/cookie_help.html b/gnu/usr.bin/lynx/lynx_help/keystrokes/cookie_help.html index 0fd5b255f4e..081bb3e52bf 100644 --- a/gnu/usr.bin/lynx/lynx_help/keystrokes/cookie_help.html +++ b/gnu/usr.bin/lynx/lynx_help/keystrokes/cookie_help.html @@ -10,7 +10,7 @@ The Cookie Jar Page displays all of the unexpired cookies you have accumulated in the hypothetical <em>Cookie Jar</em>. The cookies are obtained via <em>Set-Cookie</em> MIME headers in replies from http servers, -and are used for <A HREF="../Lynx_users_guide.html#30">State Management</A> +and are used for <A HREF="../Lynx_users_guide.html#Cookies">State Management</A> across successive requests to the servers. <p>The cookies are listed by <em>domain</em> (server's Fully Qualified @@ -29,13 +29,10 @@ for the request which caused the cookie to be sent, and whether the <em>secure</em> flag is set for the cookie, in which case it will be sent only via secure connections (presently, only SSL). The <em>Maximum Gobble Date</em>, i.e., when the cookie is intended to -expire, also is indicated. Note, however, that Lynx presently gobbles -all of it's accumulated cookies on exit from the current session, even -if the server indicated an expiration in the distant future. Also, a -server may change the expiration date, or cause the cookie to be deleted, -in its replies to subsequent requests from Lynx. If the server included -any explanatory comments in its <em>Set-Cookie</em> MIME headers, those -also are displayed in the listing. +expire, also is indicated. Also, a server may change the expiration date, +or cause the cookie to be deleted, in its replies to subsequent requests +from Lynx. If the server included any explanatory comments in its +<em>Set-Cookie</em> MIME headers, those also are displayed in the listing. <p>The <em>domain</em>=value pairs, and each cookie's name=value, are links in the listing. Activating a <em>domain</em>=value link will @@ -44,7 +41,7 @@ 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>. +name=value link will cause that particular cookie to be <em>Gobbled</em>. You will be prompted for confirmations of deletions, to avoid any accidental <em>Gobbling</em>. </BODY> diff --git a/gnu/usr.bin/lynx/lynx_help/keystrokes/edit_help.html b/gnu/usr.bin/lynx/lynx_help/keystrokes/edit_help.html index 52c081b2d20..92008a637e7 100644 --- a/gnu/usr.bin/lynx/lynx_help/keystrokes/edit_help.html +++ b/gnu/usr.bin/lynx/lynx_help/keystrokes/edit_help.html @@ -10,31 +10,48 @@ Lynx invokes a built-in <em>Line Editor</em> for entering strings in response to prompts, in forms, and for email messages if an external editor has not been defined. Administrators can offer alternate key bindings -by adding them in LYEditmap.c before compiling Lynx, and they can -be selected via the 'o'ptions menu. This is the <em>Default Binding</em>: -<pre> - ENTER Input complete - RETURN - TAB Input complete - TAB, Do - ABORT Input cancelled - Ctrl-G, Ctrl-O, Ctrl-C - ERASE Erase the line - Ctrl-U, Ctrl-X - - BACK Cursor back char - Left-Arrow - FORW Cursor forward char - Right-Arrow - BACKW Cursor back word - Ctrl-P - FORWW Cursor forward word - Ctrl-N - BOL Go to begin of line - Ctrl-A, Home, Find - EOL Go to end of line - Ctrl-E, End, Select - - DELP Delete prev char - Ctrl-H, DELETE, Remove - DELC Delete current char - Ctrl-D - DELN Delete next char - Ctrl-R - DELPW Delete prev word - Ctrl-B - DELNW Delete next word - Ctrl-F - - LOWER Lower case the line - Ctrl-K - UPPER Upper case the line - Ctrl-T - - LKCMD Invoke cmd prompt - Ctrl-V (in form text fields, only) +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>One such alternate key binding, which may be available on your system, +is the <A HREF="alt_edit_help.html">Alternate Bindings</A> keymap. + +<p>Note: setting emacs/vi keys ON has no effect on line-editor bindings. + +<p>This is the <em>Default Binding</em> keymap: + +<p><pre> + ENTER Input complete - RETURN + TAB Input complete - TAB, Do + ABORT Input cancelled - Ctrl-G, Ctrl-O, (Ctrl-C on some systems) + ERASE Erase the line - Ctrl-U, Ctrl-X + + BACK Cursor back char - Left-Arrow + FORW Cursor forward char - Right-Arrow + BACKW Cursor back word - Ctrl-P + FORWW Cursor forward word - Ctrl-N + BOL Go to begin of line - Ctrl-A, Home, Find + EOL Go to end of line - Ctrl-E, End, Select + + DELP Delete prev char - Ctrl-H, DELETE, Remove + DELN Delete next [1] char - Ctrl-D, Ctrl-R + DELPW Delete prev word - Ctrl-B + DELNW Delete next word - Ctrl-F + DELEL Delete to end of line - Ctrl-_ + + UPPER Upper case the line - Ctrl-T + LOWER Lower case the line - Ctrl-K + + LKCMD Invoke cmd prompt - Ctrl-V (in form text fields, only) [2] + SWMAP Switch input keymap - Ctrl-^ + +[1] "next" means the character "under" a box or underline style cursor; it + means "to the immediate right of" an I-beam (between characters) type + cursor. + +[2] Follow Ctrl-V with the key "e" bound to the EDIT function, + to edit the form's textarea field using an external editor. </pre> </body> </html> diff --git a/gnu/usr.bin/lynx/lynx_help/keystrokes/environments.html b/gnu/usr.bin/lynx/lynx_help/keystrokes/environments.html new file mode 100644 index 00000000000..9e578fdc35c --- /dev/null +++ b/gnu/usr.bin/lynx/lynx_help/keystrokes/environments.html @@ -0,0 +1,437 @@ +<!DOCTYPE html public "-//IETF//DTD HTML 3.0//EN"> +<html> +<head> +<title>Help on Environment variables</title> +<LINK rev="made" href="mailto:lynx-dev@sig.net"> +</head> +<body> +<pre> + +<em>ENVIRONMENT</em> + In addition to various "standard" environment variables + such as HOME, PATH, USER, DISPLAY, TMPDIR, etc, Lynx utilizes + several Lynx-specific environment variables, <a href="#env">if they exist</a>. + + Others may be created or modified by Lynx to pass data to + an external program, or for other reasons. These are + listed separately <a href="#setenv">below</a>. + + See also the sections on <a href="#cgi">SIMULATED CGI SUPPORT</a> and + <a href="#language">NATIVE LANGUAGE SUPPORT</a>, below. + + Note: Not all environment variables apply to all types of + platforms supported by Lynx, though most do. Feedback on + platform dependencies is solicited. See also <a href="#dos">win32/dos</a> specific + variables. + +<a name="env"><em> +Environment Variables Used By Lynx: +</em></a> + COLORTERM + If set, color capability for the terminal + is forced on at startup time. The actual + value assigned to the variable is ignored. + This variable is only meaningful if Lynx + was built using the slang screen-handling + library. + + LYNX_CFG + This variable, if set, will override + the default location and name of the + global configuration file (normally, + lynx.cfg) that was defined by the + LYNX_CFG_FILE constant in the + userdefs.h file, during installation. + See the userdefs.h file for more + information. + + LYNX_LSS + This variable, if set, specifies the + location of the default Lynx character + style sheet file. [Currently only + meaningful if Lynx was built using + experimental color style support.] + + LYNX_SAVE_SPACE + This variable, if set, will override + the default path prefix for files + saved to disk that is defined in the + lynx.cfg SAVE_SPACE: statement. See + the lynx.cfg file for more information. + + LYNX_TEMP_SPACE + This variable, if set, will override + the default path prefix for temporary + files that was defined during installation, + as well as any value that may + be assigned to the TMPDIR variable. + + MAIL + This variable specifies the default + inbox Lynx will check for new mail, if + such checking is enabled in the + lynx.cfg file. + + NEWS_ORGANIZATION + This variable, if set, provides the + string used in the Organization: + header of USENET news postings. It will + override the setting of the ORGANIZATION + environment variable, if it is also set + (and, on UNIX, the contents of an + /etc/organization file, if present). + + NNTPSERVER + If set, this variable specifies the + default NNTP server that will be used + for USENET news reading and posting + with Lynx, via news: URL's. + + ORGANIZATION + This variable, if set, provides the + string used in the Organization: + header of USENET news postings. On + UNIX, it will override the contents of + an /etc/organization file, if present. + + PROTOCOL_proxy + Lynx supports the use of proxy servers + that can act as firewall gateways and + caching servers. They are preferable + to the older gateway servers (see + WWW_access_GATEWAY, below). + Each protocol used by Lynx (http, ftp, + gopher, etc), can be mapped separately + by setting environment variables of + the form PROTOCOL_proxy (literally: + http_proxy, ftp_proxy, gopher_proxy, + etc), to "http://some.server.dom:port/". + See <a href="#proxy">details and examples</a>. + + WWW_access_GATEWAY + Lynx 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"), + 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 + environment variables. See <a href="#proxy">details</a>. + + WWW_HOME + This variable, if set, will override + the default startup URL specified in + any of the Lynx configuration files. + +<a name="setenv"><em> +Environment Variables Set or Modified By Lynx: +</em></a> + + LYNX_PRINT_DATE This variable is set by the Lynx + p(rint) function, to the Date: string + seen in the document's "Information + about" page (= cmd), if any. It is + created for use by an external program, + as defined in a lynx.cfg + PRINTER: definition statement. If the + field does not exist for the document, + the variable is set to a null string + under UNIX, or "No Date" under VMS. + + LYNX_PRINT_LASTMOD This variable is set by the Lynx + p(rint) function, to the Last Mod: + string seen in the document's "Information + about" page (= cmd), if any. + It is created for use by an external + program, as defined in a lynx.cfg + PRINTER: definition statement. If the + field does not exist for the document, + the variable is set to a null string + under UNIX, or "No LastMod" under VMS. + + LYNX_PRINT_TITLE This variable is set by the Lynx + p(rint) function, to the Linkname: + string seen in the document's "Information + about" page (= cmd), if any. + It is created for use by an external + program, as defined in a lynx.cfg + PRINTER: definition statement. If the + field does not exist for the document, + the variable is set to a null string + under UNIX, or "No Title" under VMS. + + LYNX_PRINT_URL This variable is set by the Lynx + p(rint) function, to the URL: string + seen in the document's "Information + about" page (= cmd), if any. It is + created for use by an external program, + as defined in a lynx.cfg + PRINTER: definition statement. If the + field does not exist for the document, + the variable is set to a null string + under UNIX, or "No URL" under VMS. + + LYNX_VERSION This variable is always set by Lynx, + and may be used by an external program + to determine if it was invoked by + Lynx. See also the comments in the + distribution's sample mailcap file, + for notes on usage in such a file. + + TERM Normally, this variable is used by + Lynx to determine the terminal type + being used to invoke Lynx. If, however, + it is unset at startup time (or + has the value "unknown"), or if the + -term command-line option is used, + Lynx will set or modify its value + to the user specified terminal type + (for the Lynx execution environment). + Note: If set/modified by Lynx, the values of + the LINES and/or COLUMNS environment + variables may also be changed. + + +<a name="cgi"><em> +SIMULATED CGI SUPPORT +</em></a> + If built with the cgi-links option enabled, Lynx allows + access to a cgi script directly without the need for an + http daemon. + + When executing such "lynxcgi scripts" (if enabled), the + following variables may be set for simulating a CGI environment: + + CONTENT_LENGTH + + CONTENT_TYPE + + DOCUMENT_ROOT + + HTTP_ACCEPT_CHARSET + + HTTP_ACCEPT_LANGUAGE + + HTTP_USER_AGENT + + PATH_INFO + + PATH_TRANSLATED + + QUERY_STRING + + REMOTE_ADDR + + REMOTE_HOST + + REQUEST_METHOD + + SERVER_SOFTWARE + + Other environment variables are not inherited by the + script, unless they are provided via a LYNXCGI_ENVIRONMENT + statement in the configuration file. See the lynx.cfg + file, and the (draft) CGI 1.1 Specification + <http://Web.Golux.Com/coar/cgi/draft-coar-cgi-v11-00.txt> + for the definition and usage of these variables. + + The CGI Specification, and other associated documentation, + should be consulted for general information on CGI script + programming. + +<a name="language"><em> +NATIVE LANGUAGE SUPPORT +</em></a> + If configured and installed with Native Language Support, + Lynx will display status and other messages in your local + language. See the file ABOUT_NLS in the source distribution, + or at your local GNU site, for more information about + internationalization. + + The following environment variables may be used to alter + default settings: + + LANG This variable, if set, will override + the default message language. It is + an ISO 639 two-letter code identifying + the language. Language codes are NOT + the same as the country codes given in + ISO 3166. + + LANGUAGE This variable, if set, will override + the default message language. This is a + GNU extension that has higher priority for + setting the message catalog than LANG or + LC_ALL. + + LC_ALL and + + LC_MESSAGES These variables, if set, specify the + notion of native language formatting + style. They are POSIXly correct. + + LINGUAS This variable, if set prior to configuration, + limits the installed languages to specific values. + It is a space-separated list of two-letter codes. + Currently, it is hard-coded to a wish list. + + NLSPATH This variable, if set, is used as the + path prefix for message catalogs. + +<a name="proxy"><em> +Proxy: +</em></a> + + To set your site's NTTP server as the default host for news reading + and posting via Lynx, set the environment variable NNTPSERVER so that + it points to its Internet address. The variable "NNTPSERVER" is used + to specify the host which will be used as the default for news URLs. + + UNIX + setenv NNTPSERVER "news.server.dom" + + VMS + define/system NNTPSERVER "news.server.dom" + + Lynx still supports use of gateway servers, with the servers specified + via the variables "WWW_access_GATEWAY", where "access" is lower case + and can be "http", "ftp", "gopher" or "wais". Most of the gateway + servers have been discontinued, but "http://www.w3.org:8001" is + available for wais searches (note that you do not include a + terminal '/' for gateways, but do for proxies; see below). + + Lynx version 2.2 and beyond supports the use of proxy servers that + can act as firewall gateways and caching servers. They are + preferable to the older gateway servers. Each protocol used by + Lynx can be mapped separately using PROTOCOL_proxy environment + variables of the form: + + UNIX + setenv http_proxy "http://some.server.dom:port/" + setenv https_proxy "http://some.server.dom:port/" + setenv ftp_proxy "http://some.server.dom:port/" + setenv gopher_proxy "http://some.server.dom:port/" + setenv news_proxy "http://some.server.dom:port/" + setenv newspost_proxy "http://some.server.dom:port/" + setenv newsreply_proxy "http://some.server.dom:port/" + setenv snews_proxy "http://some.server.dom:port/" + setenv snewspost_proxy "http://some.server.dom:port/" + setenv snewsreply_proxy "http://some.server.dom:port/" + setenv nntp_proxy "http://some.server.dom:port/" + setenv wais_proxy "http://some.server.dom:port/" + setenv finger_proxy "http://some.server.dom:port/" + setenv cso_proxy "http://some.server.dom:port/" + + VMS + define "http_proxy" "http://some.server.dom:port/" + define "https_proxy" "http://some.server.dom:port/" + define "ftp_proxy" "http://some.server.dom:port/" + define "gopher_proxy" "http://some.server.dom:port/" + define "news_proxy" "http://some.server.dom:port/" + define "newspost_proxy" "http://some.server.dom:port/" + define "newsreply_proxy" "http://some.server.dom:port/" + define "snews_proxy" "http://some.server.dom:port/" + define "snewspost_proxy" "http://some.server.dom:port/" + define "snewsreply_proxy" "http://some.server.dom:port/" + define "nntp_proxy" "http://some.server.dom:port/" + define "wais_proxy" "http://some.server.dom:port/" + define "finger_proxy" "http://some.server.dom:port/" + define "cso_proxy" "http://some.server.dom:port/" + (Encase *BOTH* strings in double-quotes to maintain + lower case for the PROTOCOL_proxy variable and for + the http access type; include /system if you want + proxying for all clients on your system.) + + If you wish to override the use of a proxy server for specific hosts or + entire domains you may use the "no_proxy" environment variable. + The no_proxy variable can be a comma-separated list of strings defining + no-proxy zones in the DNS domain name space. If a tail substring of the + domain-path for a host matches one of these strings, transactions with that + node will not be proxied. Here is an example use of "no_proxy": + + UNIX + setenv no_proxy "host.domain.dom, domain1.dom, domain2" + + VMS + define "no_proxy" "host.domain.dom, domain1.dom, domain2" + + You can include a port number in the no_proxy list to override use + of a proxy server for the host accessed via that port, but not via + other ports. For example, if you use "host.domain.dom:119" and/or + "host.domain.dom:210", then news (port 119) URLs and/or any wais + (port 210) searches on that host would be excluded, but http, ftp, + and gopher services (if normally proxied) would still be included, + as would any news or wais services on other hosts. + + Warning: Note that setting 'il' as an entry in this list + will block proxying for the .mil domain as well as the .il domain. + If the entry is '.il' this will not happen. + + If you wish to override the use of a proxy server completely (i.e., + globally override any existing proxy variables), set the value of + "no_proxy" to "*". This is the only allowed use of * in no_proxy. + + Note that Lynx treats file URLs on the local host as requests for + direct access to the file, and does not attempt ftp if that fails. + It treats both ftp URLs and file URLs on remote hosts as ftp URLs, + and does not attempt direct file access for either. If ftp URLs are + being proxied, file URLs on a remote host will be converted to ftp + URLs before submission by Lynx to the proxy server, so no special + procedure for inducing the proxy server to handle them is required. + Other WWW clients may require that the http server's configuration + file have "Map file:* ftp:*" in it to perform that conversion. + + If you have not set NNTPSERVER, proxy or no_proxy environment variables + you can set them at run time via the configuration file lynx.cfg + (this will not override external settings). + +<a name="dos"><em> +Win32 (95/NT) and 386 DOS +</em></a> + (adapted from "readme.txt" by Wayne Buttles + and "readme.dos" by Doug Kaufman) + + Here are some environment variables that should be set, usually in a + batch file that runs the lynx executable. Make sure that you have enough + room left in your environment. You may need to change your "SHELL=" + setting in config.sys. In addition, lynx looks for a "SHELL" environment + variable when shelling to DOS. If you wish to preserve the environment + space when shelling, put a line like this in your AUTOEXEC.BAT file also + "SET SHELL=C:\COMMAND.COM /E:2048". It should match CONFIG.SYS. + + HOME Where to keep the bookmark file and personal config files. + TEMP or TMP Bookmarks are kept here with no HOME. Temp files here. + USER Set to your login name + LYNX_CFG Set to the full path and filename for lynx.cfg + + 386 version only: + WATTCP.CFG Set to the full path for the WATTCP.CFG directory + (Depending on how you compiled libtcp.a, you may have to use WATCONF.) + + Define these in your batch file for running Lynx. For example, if your + application line is "D:\win32\lynx.bat", lynx.bat for Win32 may look like: + @ECHO OFF + set home=d:\win32 + set temp=d:\tmp + set lynx_cfg=d:\win32\lynx.cfg + d:\win32\lynx.exe %1 %2 %3 %4 %5 + + In lynx_386, a typical batch file might look like: + + @echo off + set HOME=f:/lynx2-8 + set USER=your_login_name + set LYNX_CFG=%HOME%/lynx.cfg + set WATTCP.CFG=%HOME% + f:\lynx2-8\lynx %1 %2 %3 %4 %5 %6 %7 %8 %9 + + You will also need to make sure that the WATTCP.CFG file has the + correct information for IP number, Gateway, Netmask, and Domain Name + Server. This can also be automated in the batch file. + + +</pre> +</body> +</html> diff --git a/gnu/usr.bin/lynx/lynx_help/keystrokes/follow_help.html b/gnu/usr.bin/lynx/lynx_help/keystrokes/follow_help.html index f30fbb7754b..76f5b93460d 100644 --- a/gnu/usr.bin/lynx/lynx_help/keystrokes/follow_help.html +++ b/gnu/usr.bin/lynx/lynx_help/keystrokes/follow_help.html @@ -14,7 +14,7 @@ the current session via the <em>Options menu</em>, then hypertext links (and form fields, depending on the keypad mode) are prefixed with numbers in square brackets. Entering a keyboard or keypad number is treated as an <em>F_LINK_NUM</em> command, and should -invoke the <em>Follow link (or goto link or page) number:</em> statusline +invoke the <em>Follow link (or goto link or page) number:</em> statusline prompt for a potentially multiple digit number corresponding to an indicated link number. If RETURN is pressed to terminate the number entry (e.g., @@ -39,10 +39,33 @@ numbered</em> mode. <em>123p</em>), Lynx will make the page corresponding to that number the currently displayed page, and the first link on that page, if any, the current link. The '<em>g</em>' and '<em>p</em>' suffixes thus -convert the +convert the <em>Follow link (or goto link or page) number:</em> feature to an advanced navigation aid. +<p>Finally, a user may add a <em>+</em> or <em>-</em> suffix to a number +command to indicate jumping forward or back relative to the current link or +page. +For example, typing <em>1g+</em> followed by RETURN will move the current +link to the next numbered link, skipping any intervening pages +or unnumbered links; <em>1g-</em> goes to the preceding numbered link. +On a page without links, <em>3g+</em> goes to the 3rd link <em>following</em> +the page. <em>5p+</em> skips ahead 5 pages, and so on. +You can also enter <em>5+</em> or <em>5-</em>, which will activate +the 5th link ahead/behind where you are currently positioned. +Note that typing <em>1g+</em> is different from typing a down arrow +in that <em>1g+</em> may skip pages containing no links, or +intervening non-numbered links, such as form fields when +form fields are not numbered. It also differs from +the <em><tab></em> command in that <em>1g+</em> +does not skip over whole textareas, unless form fields +are not numbered. + +<p> +<em>NOTE:</em> <em>1+g 1-g 1+p 1-p</em> are all recognized as equivalent<br> +to <em>1g+ 1g- 1p+ 1p-</em> . Any other (mistyped) characters terminate<br> +the formula: e.g. <em>1gh+</em> is treated as <em>1g</em>. + <p>If the user has set <em>Keypad mode</em> to <em>Numbers act as arrows</em>, then only '<em>0</em>', rather than every number, will be treated as an <em>F_LINK_NUM</em> command for invoking the <em>Follow link (or goto link or page) @@ -74,6 +97,19 @@ command when positioned on the OPTION. For purposes of paging (e.g., in conjunction with the '<em>p</em>' suffix), a <em>page</em> is defined as the number of OPTIONs displayed within the vertical dimension of the popup window. +Finally, the <em>+</em> and <em>-</em> suffixes can be used +to move forward or back from the current option or page in +a popup menu, +similarly to the way they are used for links For example, +while viewing a popup window, the user can type +<em>3p+</em> and RETURN +to skip ahead 3 pages, and <em>50g-</em> will move the +current selection back 50 options. +This will work whether or not <em>keypad mode</em> is +<em>Links and form fields are numbered</em> since options +are numbered internally. If form field numbering is +turned off, the option numbers won't appear on screen, +but the user can still navigate using these commands. <p>Note that HTML can be structured so that it includes <em>hidden links</em>, i.e., without a visible link name intended for ACTIVATE-ing @@ -84,7 +120,7 @@ have support for image handling available. They also can be created by having truly empty Anchor content, in cases for which the value of an Anchor's HREF attribute is intended as a navigation aid for robots (typically indexers) and not as content for a browser's rendition of the -document. With the <em>-ismap</em> command line switch, Lynx will +document. With the <em>-ismap</em> command line switch, Lynx will additionally treat a link to a server-side image maps as hidden if there also is a client-side map for the same image. Finally, in some cases links which are not intended to be hidden @@ -92,14 +128,14 @@ may effectively become <em>hidden links</em> because of bad HTML. The <em>hidden links</em> differ from Anchors which have only a NAME or ID attribute name/value pair (intended as positioning targets from other links which do have HREF attributes and values that include a -fragment). +fragment). <p>Lynx respects instructions for <em>hidden links</em> and normally does not include them in the rendition of the document. However, if the command line switch <em>-hiddenlinks=merge</em> is used, such links will still be numbered in sequence with other links which are not hidden, and if <em>Links are numbered</em> mode is also on, link numbers will appear for them in the -displayed text (except for links to image maps which are hidden because of +displayed text (except for links to image maps which are hidden because of <em>-ismap</em>). If <em>-hiddenlinks=listonly</em> or <em>-hiddenlinks=ignore</em> is in effect, <em>hidden links</em> will not be shown in the text even in <em>links are numbered</em> mode. Not using a @@ -108,13 +144,13 @@ shown in the text even in <em>links are numbered</em> mode. Not using a <p>If a document includes <em>hidden links</em>, they will be reported, with appropriate labeling, -in the menu created for the LIST ('<em>l</em>') command, -unless <em>-hiddenlinks=ignore</em> is used. They can then be -ACTIVATE-ed via that menu. Also, if a link was hidden due to an ALT +in the menus created for the LIST ('<em>l</em>') or ADDRLIST ('<em>A</em>') +commands, unless <em>-hiddenlinks=ignore</em> is used. They can then be +ACTIVATE-ed via those menus. Also, if a link was hidden due to 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 attritute values of IMG elements, because this indicates that the -user does have some form of image handling enabled via a helper application, +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 browsers or other suitable software. @@ -124,8 +160,9 @@ for the form, but the value should not be displayed in the rendered form. Lynx respects this attribute as well, and neither displays the HIDDEN field, nor assigns it a number for the F_LINK_NUM ('<em>0</em>') command and <em>Links and form fields are numbered</em> keypad mode handling, nor -includes an entry for it in the menu created for the LIST ('<em>l</em>') -command. However, the HIDDEN name/value pairs are included in any displays +includes an entry for it in the menus created for the LIST ('<em>l</em>') +or ADDRLIST ('<em>A</em>') +commands. However, the HIDDEN name/value pairs are included in any displays of submitted form content in the <em>Information about the current document</em> that is invoked by the INFO ('<em>=</em>') command. </BODY> diff --git a/gnu/usr.bin/lynx/lynx_help/keystrokes/keystroke_help.html b/gnu/usr.bin/lynx/lynx_help/keystrokes/keystroke_help.html index f3a57bc35d9..aa7a3da110a 100644 --- a/gnu/usr.bin/lynx/lynx_help/keystrokes/keystroke_help.html +++ b/gnu/usr.bin/lynx/lynx_help/keystrokes/keystroke_help.html @@ -39,10 +39,10 @@ r - Remove selected file t - Tag highlighted file u - Upload a file into the current directory - + <A HREF="other_help.html">OTHER</A>: ? (or h) - Help (this screen) a - Add the current link to a bookmark file - c - Send a comment to the document owner + c - Send a comment to the document owner d - Download the current link e - Edit the current file g - Goto a user specified <a @@ -83,16 +83,17 @@ ] - 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-V - Switch to alternative parsing of HTML documents + CTRL-V - Switch to <A HREF="option_help.html#tagsoup" + >alternative parsing</A> of HTML documents CTRL-W - Refresh the screen - CTRL-U - Erase input line + CTRL-U - Erase input line (<a href="edit_help.html" + >more input line commands</a>) CTRL-G - Cancel input or transfer CTRL-T - Toggle trace mode on and off - ; - View the Lynx Trace Log for the current - session. + ; - View the Lynx Trace Log for the current session CTRL-K - Invoke the <A HREF="cookie_help.html" >Cookie Jar Page</A> - numbers - Invoke the prompt + numbers - Invoke the prompt <a href="follow_help.html" >Follow link (or goto link or page) number:</a> or the diff --git a/gnu/usr.bin/lynx/lynx_help/keystrokes/option_help.html b/gnu/usr.bin/lynx/lynx_help/keystrokes/option_help.html index 2ef8151ce4d..17205d779fe 100644 --- a/gnu/usr.bin/lynx/lynx_help/keystrokes/option_help.html +++ b/gnu/usr.bin/lynx/lynx_help/keystrokes/option_help.html @@ -5,258 +5,385 @@ <LINK rev="made" href="mailto:lynx-dev@sig.net"> </HEAD> <BODY> -<h1>+++ Options Screen Help +++</h1> -<PRE> - The Options Screen allows you to set and - modify many of Lynx's features. The following - options may be set. - - Editor - If non-empty it defines the editor to spawn - when editing a local file or sending mail. - Any valid text editor may be entered here. - - DISPLAY variable - If non-empty it specifies your <A HREF="xterm_help.html">X terminal</A> - display address. - - Multi-bookmarks - When OFF, the default bookmark file is used - for the 'v'iew bookmarks and 'a'dd bookmark - link commands. If set to STANDARD, 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 in that menu. If set to - ADVANCED, you instead are 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. - - Bookmark file - If non-empty and multi-bookmarks is OFF, it - specifies your default '<A HREF="bookmark_help.html">Bookmark file</A>'. - If multi-bookmarks is STANDARD or ADVANCED, - entering 'B' will invoke a menu in which you - can specify the filepaths and descriptions - of up to 26 bookmark files. The filepaths - must be from your home directory, and begin - with dot-slash (./) if subdirectories are - included (e.g, ./BM/lynx_bookmarks.html). - Lynx will create bookmark files when you - first 'a'dd a link, but any subdirectories - in the filepath must already exist. - - FTP sort criteria - This option allows you to specify how files - will be sorted within FTP listings. The - current options include "By Filename", - "By Size", "By Type", and "By Date". - - Personal Mail - You may set your mail address here so that - Address 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. - - Searching type - If set to 'case sensitive', user searches - invoked by the '/' command will be case - sensitive substring searches. The - default is 'Case Insensitive' substring - searches - - Preferred Document - The language you prefer if multi-language files - Language are available from servers. Use RFC 1766 tags, - e.g., en for English, fr for French, etc. Can be - a comma-separated list, which may be interpreted - by servers as descending order of preferences. - You can also make your order of preference explicit - by using q factors as defined by the HTTP protocol, - for servers which understand it, for example: - <kbd>da, en-gb;q=0.8, en;q=0.7</kbd> - - Preferred Document - The character set you prefer if sets in addition - Charset to ISO-8859-1 and US-ASCII are available from - servers. Use MIME notation (e.g., ISO-8859-2) - and do not include ISO-8859-1 or US-ASCII, since - those values are always assumed by default. Can - be a comma-separated list, which may be interpreted - by servers as descending order of preferences. - You can also make your order of preference explicit - by using q factors as defined by the HTTP protocol, - for servers which understand it, for example: - <kbd>iso-8859-5, unicode-1-1;q=0.8</kbd> - - Display Character - This option allows you to set up the default - set character set for your specific terminal. - The character set provides a mapping of 8-bit ISO - Latin character entities and/or Asian (CJK) or - Unicode characters into viewable characters and - should be set according to your terminal's - character set if you will be viewing such - characters with Lynx. You must have the selected - character set installed on your terminal. - - Raw 8-bit or CJK - Toggles whether 8-bit characters are assumed to - mode correspond with the selected character set and - therefore are processed without translation via - the chartrans conversion tables. Should be ON - by default when the selected character set is one - of the Asian (CJK) sets and the 8-bit characters - are Kanji multibytes. Should be OFF for the other - character sets, but can be turned ON when the - document's charset is unknown (e.g., is not - ISO-8859-1 and no charset parameter was included in - a reply 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. The setting also can be - toggled via the RAW_TOGGLE command, normally mapped - to '@', and at startup via the -raw switch. - - Show color - This option will be present if color support is - available. If set to ON or ALWAYS, color mode will - be forced on if possible. If (n)curses color - support is available but cannot be used for the - current terminal type, selecting ON is rejected - with a message. If set to OFF or NEVER, color mode - will be turned off. - 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. If Lynx - is built with the slang library, this is equivalent - to having included the -color command line switch - or having the COLORTERM environment variable - set. If color support is provided by curses or - ncurses, this is equivalent to the default behavior - of using color when the terminal type supports it. - If (n)curses color support is available but cannot - be used for the current terminal type, the - preference can still be saved but will have no - effect. - A saved value of NEVER will cause Lynx to assume a - monochrome terminal at startup. 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 - startup 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 the slang library 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 startup color mode is incorrect for your - terminal, set it appropriately on or off via this - option. - - VI keys - 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. The - uppercase H, J, K, and L keys remain mapped to - their configured bindings (normally HELP, JUMP, - KEYMAP, and LIST, respectively). - - Emacs keys - 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). - - Show dot files - If display/creation of hidden (dot) - files/directories is enabled, you can turn - the feature on or off via this setting. - - Popups for select - Lynx normally uses a popup window for the - fields OPTIONs in form SELECT fields when the field - does not have the MULTIPLE attribute specified, - and thus only one OPTION can be selected. The - use of popup windows can be disabled by changing - this setting to OFF, in which case the OPTIONs - will be rendered as a list of radio buttons. - Note that if the SELECT field does have the - MULTIPLE attribute specified, the OPTIONs always - are rendered as a list of checkboxes. - - Show cursor for - Lynx normally hides the cursor by positioning it - current link or to the right and if possible the very bottom of - option the screen, so that the current link or OPTION - is indicated solely by its highlighting or color. - If show cursor is set to ON, the cursor will be - positioned at the left of the current link or - OPTION. This is helpful when Lynx is being used - with a speech or braille interface. It also is - useful for sighted users when the terminal cannot - distinguish the character attributes used to - distinguish the current link or OPTION from the - others in the screen display. - - Keypad mode - This option gives the choice between navigating - with the keypad (as arrows; see Lynx Navigation) - and having every link numbered (numbered links) - so that the links may be selected by numbers - instead of moving to them with the arrow keys. - - Line edit style - This option allows you to set alternate key - bindings for the built-in line editor, if your - system administrator has installed alternates. - Otherwise, Lynx uses the <A HREF="edit_help.html">Default Binding</A>. - - List directory - Applies to Directory Editing. Files and - style directories can be presented in the following - ways: - Mixed style - Files and directories are listed together in - alphabetical order. - Directories first - Files and directories are separated into two - alphabetical lists. Directories are listed - first. - Files first - Files and directories are separated into two - alphabetical lists. Files are listed first. - - User Mode - Beginner - Shows two extra lines of help at the bottom - of the screen - Intermediate (normal mode) - The "normal" statusline messages appear. - Advanced - The URL is shown on the statusline. - - User Agent - The header string which Lynx sends to servers - to indicate the User-Agent is displayed here. - Changes may be disallowed via the -restrictions - switch. Otherwise, the header can be changed - temporarily to a string such as L_y_n_x/2.7.2 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 the Options Menu. Changes - of the header are not saved in the RC file. - NOTE that Netscape Communications Corp. has - claimed that false transmissions of "Mozilla" as - the User-Agent are a copyright infringement, which - will be prosecuted. DO NOT misrepresent Lynx as - Mozilla. The Options Menu issues a warning about - possible copyright infringement whenever the header - is changed to one which does not include "Lynx" or - "lynx". - - Local execution - If set to 'ALWAYS ON', Lynx will locally execute - links commands contained inside of any links. This - can be HIGHLY DANGEROUS so it is recommended - that they remain 'ALWAYS OFF' or 'FOR LOCAL - FILES ONLY' unless otherwise set by your system - administrator. This option may not be available - on most versions of Lynx. - -</PRE> +<h1>OPTIONS SCREEN HELP</h1> + +The Options Screen allows you to set and modify many Lynx features.<BR> +Note: some options appear on the screen only if they have been +compiled in or chosen in `lynx.cfg':<P> + +<UL> +<LI>Personal Preferences +<UL> +<LI><A HREF="#CK">Cookies</A> +<LI><A HREF="#ED">Editor</A> +<LI><A HREF="#EM">Emacs keys</A> +<LI><A HREF="#KM">Keypad mode</A> +<LI><A HREF="#LE">Line edit style</A> +<LI><A HREF="#PM">Personal Mail Address</A> +<LI><A HREF="#ST">Searching type</A> +<LI><A HREF="#SC">Show color</A> +<LI><A HREF="#CL">Show cursor for current link or option</A> +<LI><A HREF="#UM">User Mode</A> +<LI><A HREF="#VI">VI keys</A> +<LI><A HREF="#DC">Display Character set</A> +<LI><A HREF="#DV">X DISPLAY variable</A></UL> +<LI>Document Layout +<UL> +<LI><A HREF="#AD">Assumed document character set</A> +<LI><A HREF="#JK">Raw 8-bit or CJK mode</A> +<LI><A HREF="#tagsoup">HTML error recovery</A> +<LI><A HREF="#PU">Pop-ups for select fields</A> +<LI><A HREF="#SI">Show Images</A> +<LI><A HREF="#VB">Verbose Images</A></UL> +<LI>Bookmark Options +<UL> +<LI><A HREF="#MB">Multi-bookmarks</A> +<LI><A HREF="#BF">Bookmark file</A></UL> +<LI>File Management Options +<UL> +<LI><A HREF="#FT">FTP sort criteria</A> +<LI><A HREF="#LD">Local directory sort criteria</A> +<LI><A HREF="#DF">Show dot files</A> +<LI><A HREF="#LL">Execution links</A></UL> +<LI>Headers transferred to remote server +<UL> +<LI><A HREF="#PC">Preferred Document Charset</A> +<LI><A HREF="#PL">Preferred Document Language</A> +<LI><A HREF="#UA">User Agent</A></UL> +</UL> + +<H1><A NAME="CK">Cookies</A></H1> + +This can be set to accept or reject all cookies or to ask each time. +See the Users Guide for details of <A HREF="../Lynx_users_guide.html#Cookies" +>cookie usage</A>. + +<H1><A NAME="ED">Editor</A></H1> + +This is the editor to be invoked when editing browsable files, +sending mail or comments, or filling form's textarea (multiline input field). +The full pathname of the editor command should be specified when possible. +It is assumed the text editor supports the same character set +you have for "display character set" in Lynx. + +<H1><A NAME="EM">Emacs keys</A></H1> + +If set to 'ON' then the CTRL-P, CTRL-N, CTRL-F and CTRL-B keys will be mapped +to up-arrow, down-arrow, right-arrow and left-arrow respectively. Otherwise, +they remain mapped to their configured bindings (normally UP_TWO lines, +DOWN_TWO lines, NEXT_PAGE and PREV_PAGE respectively). +<p>Note: setting emacs keys does not affect the line-editor bindings. + +<H1><A NAME="LL">Execution links</A></H1> + +If set to 'ALWAYS ON', Lynx will locally execute commands contained +inside any links. This can be HIGHLY DANGEROUS, so it is recommended +that they remain 'ALWAYS OFF' or 'FOR LOCAL FILES ONLY'. + +<H1><A NAME="KM">Keypad mode</A></H1> + +This gives the choice between navigating with the keypad (as arrows; +see Lynx Navigation) and having every link numbered (numbered links) +so that the links may be selected by numbers instead of moving to them +with the arrow keys. You can also number form fields. + +<H1><A NAME="LE">Line edit style</A></H1> + +This allows you to set alternate key bindings for the built-in line editor, +if your system administrator has installed +<A HREF="alt_edit_help.html">Alternate Bindings</A>. +Otherwise, Lynx uses the <A HREF="edit_help.html">Default Binding</A>. + +<H1><A NAME="PM">Personal Mail Address</A></H1> + +You may set your mail address here so that when mailing messages +to other people or mailing files to yourself, your email address can be +automatically filled in. Your email address will also be sent +to HTTP servers in a `from:' field. + +<H1><A NAME="PU">Pop-ups for select fields</A></H1> + +Lynx normally uses a pop-up window for the OPTIONs in form SELECT fields +when the field does not have the MULTIPLE attribute specified, and thus +only one OPTION can be selected. The use of pop-up windows can be disabled +by changing this setting to OFF, in which case the OPTIONs will be rendered +as a list of radio buttons. Note that if the SELECT field does have +the MULTIPLE attribute specified, the OPTIONs always are rendered +as a list of checkboxes. + +<H1><A NAME="ST">Searching type</A></H1> + +If set to 'case sensitive', user searches invoked by '/' will be +case-sensitive substring searches. Default is 'Case Insensitive'. + +<H1><A NAME="SC">Show color</A></H1> + +This will be present if color support is available. +<ul> +<li>If set to ON or ALWAYS, +color mode will be forced on if possible. If (n)curses color support +is available but cannot be used for the current terminal type, selecting ON +is rejected with a message. +<li>If set to OFF or NEVER, color mode will be +turned off. +<li>ALWAYS and NEVER are not offered in anonymous accounts. +If saved to a '.lynxrc' file in non-anonymous accounts, ALWAYS will cause Lynx +to set color mode on at startup if supported. +</ul> +If Lynx is built with slang, +this is equivalent to having included the -color command line switch +or having the COLORTERM environment variable set. If color support is +provided by curses or ncurses, this is equivalent to the default behavior +of using color when the terminal type supports it. If (n)curses color support +is available but cannot be used for the current terminal type, the preference +can still be saved but will have no effect. + +<p>A saved value of NEVER will +cause Lynx to assume a monochrome terminal at start-up. It is similar +to the -nocolor switch, but (when the slang library is used) can be overridden +with the -color switch. If the setting is OFF or ON when the current options +are saved to a '.lynxrc' file, the default start-up behavior is retained, +such that color mode will be turned on at startup only if the terminal info +indicates that you have a color-capable terminal, or (when slang is used) +if forced on via the -color switch or COLORTERM variable. This default +behavior always is used in anonymous accounts, or if the 'option'_save +restriction is set explicitly. If for any reason the start-up color mode +is incorrect for your terminal, set it appropriately on or off via this option. + +<H1><A NAME="CL">Show cursor for current link or option</A></H1> + +Lynx normally hides the cursor by positioning it to the right and if possible +the very bottom of the screen, so that the current link or OPTION is indicated +solely by its highlighting or color. If show cursor is set to ON, the cursor +will be positioned at the left of the current link or OPTION. This is helpful +when Lynx is being used with a speech or braille interface. It is also useful +for sighted users when the terminal cannot distinguish the character attributes +used to distinguish the current link or OPTION from the others in the display. + +<H1><A NAME="UM">User Mode</A></H1> + +<dl> +<dt><EM>Novice</EM>: Shows 2 extra lines of help at the bottom of the screen +for beginners. +<dt><EM>Intermediate (normal)</EM>: Normal status-line messages appear. +<dt><EM>Advanced</EM>: The URL is shown on the status line. +</dl> + +<H1><A NAME="AD">Assumed document character set</A></H1> + +This changes the handling of documents which do not explicitly specify +a charset. Normally Lynx assumes that 8-bit characters in those documents +are encoded according to iso-8859-1 (the official default for HTTP protocol). +Unfortunately, many non-English web pages forget to include proper charset +info; this option helps you browse those broken pages if you know somehow +what the charset is. When the value given here or by an -assume_charset +command-line flag is in effect, Lynx will treat documents as if they were +encoded accordingly. Option is active when 'Raw 8-bit or CJK Mode' is OFF. + +<H1><A NAME="JK">Raw 8-bit or CJK mode</A></H1> + +This is set automatically, but can be toggled manually in certain cases: +it toggles whether 8-bit characters are assumed to correspond with the display +character set and therefore are processed without translation +via the chartrans conversion tables. ON by default when the display +character set is one of the Asian (CJK) sets and the 8-bit characters +are Kanji multibytes. OFF for the other display character sets, +but can be turned ON when the document's charset is unknown +(e.g., is not ISO-8859-1 and no charset parameter was specified +in a reply header from an HTTP server to indicate what it is), +but you have no better idea than viewing it as from display character set +(see 'assumed document character set' for best choice). Should be OFF +when an Asian (CJK) set is selected but the document is ISO-8859-1 +or another 'assumed document character set'. The setting can also be toggled +via the RAW_TOGGLE command, normally mapped to '@', and at startup +via the -raw switch. + +<H1><A NAME="tagsoup">HTML error recovery</A></H1> + +Lynx often has to deal with invalid HTML markup. It always tries to +recover from errors, but there is no universally correct way for doing +this. As a result, there are two parsing modes: +"<DFN>SortaSGML</DFN>" attempts to enforce valid nesting of most tags +at an earlier stage of processing, while "<DFN>TagSoup</DFN>" relies +more on the HTML rendering stage to mimic the behavior of some other +browsers. +You can also switch between these modes with the CTRL-V key, and the +default can be changed in lynx.cfg or with the -tagsoup command line +switch. + +<P> +The "SortaSGML" mode will often appear to be more strict, and makes +some errors apparent that are otherwise unnoticeable. One particular +difference is the handling of block elements or +<li>..</li> inside <a HREF="some.url">..</a>. +Invalid nesting like this may turn anchors into hidden links which +cannot be easily followed, this is avoided in "TagSoup" mode. See the +<a href="follow_help.html">help on following links by +number</a> for more information on hidden links. Often pages may be +more readable in "TagSoup" mode, but sometimes the opposite is true. +Most documents with valid HTML, and documents with only minor errors, +should be rendered the same way in both modes. + +<P> +If you are curious about what goes on behind the scenes, but find that +the information from the -trace switch is just too much, Lynx can be +started with the -preparsed switch; going into SOURCE mode ('\' key) +and toggling the parsing mode (with CTRL-V) should then show some of +the differences. + +<!-- +LP's version - for reference - TD + +While the proper HTML markup should be canonical, badly nested HTML pages +may be recovered in different ways. There are two error recovery modes +in Lynx: SortaSGML with the recovery at SGML stage and TagSoup mode +with the recovery at HTML parsing stage, the latter gives more +recovery and was the default in Lynx 2.7.2 and before, +and the first may be useful for page validation purposes. +One particular difference is known for <li>..</li> +or similar strong markup inside <a HREF="some.url">..</a> +anchor text - those links are not reachable in SortaSGML +(such markup should be placed outside <a>..</a> indeed). +Default recovery mode can also be switched with CTRL-V key, +from lynx.cfg or command line switch. +--> + + +<H1><A NAME="SI">Show Images</A></H1> + +Text-based browser cannot show images directly, so we have a choice: +<em>ignore all</em> images without ALT= text string +(this is also switched by <A HREF="../Lynx_users_guide.html#[-key">'[' key</A>), +<em>show labels</em> (see also "verbose images" for choice between [IMAGE] and filename), +<em>use links</em> for every image to make it possible to download them +(also switched by <A HREF="../Lynx_users_guide.html#*-key">'*' key</A>). +Changing these settings will not be saved but could be made permanent +by changing the respective settings in lynx.cfg. + +<H1><A NAME="VB">Verbose Images</A></H1> + +Controls whether or not Lynx replaces the [LINK], [INLINE] and [IMAGE] comments +(for images without ALT) with filenames of these images. This is extremely +useful because now we can determine immediately which images are decorations +(button.gif, line.gif) and which are important. + +<H1><A NAME="VI">VI keys</A></H1> + +If set to 'ON' then the lowercase h, j, k and l keys will be mapped +to left-arrow, down-arrow, up-arrow and right-arrow respectively. +<p>The uppercase H, J, K, and L keys remain mapped to their configured bindings +(normally HELP, JUMP, KEYMAP and LIST, respectively). +<p>Note: setting vi keys does not affect the line-editor bindings. + +<H1><A NAME="DC">Display Character set</A></H1> + +This allows you to set up the default character set for your specific terminal. +The display character set provides a mapping from the character encodings +of viewed documents and from HTML entities into viewable characters. +It should be set according to your terminal's character set +so that characters other than 7-bit ASCII can be displayed correctly, +using approximations if necessary, +<A HREF="test_display.html">try the test here</A>. +Since Lynx now supports a wide range of platforms +it may be useful to note that cpXXX codepages are used within IBM PC computers, +and windows-xxxx within native MS-Windows applications. + +<H1><A NAME="DV">X DISPLAY variable</A></H1> + +This option is only relevant to X Window users. It specifies +the DISPLAY (Unix) or DECW$DISPLAY (VMS) variable. It is picked up +automatically from the environment if it has been previously set. + +<H1><A NAME="MB">Multi-bookmarks</A></H1> + +Manage multiple bookmark files: +<ul> +<li>When OFF, the default bookmark file is used for the 'v'iew-bookmarks +and 'a'dd-bookmark link commands. +<li>If set to STANDARD, a menu of available +bookmarks is always invoked when you seek to view a bookmark file +or add a link, and you select the bookmark file by its letter token +in that menu. +<li>If set to ADVANCED, you are instead prompted for the letter +of the desired bookmark file, but can enter '=' to invoke the STANDARD +selection menu, or RETURN for the default bookmark file. +</ul> + +<H1><A NAME="BF">Bookmark file</A></H1> + +Manage the default bookmark file: +<ul> +<li>If non-empty and multi-bookmarks is OFF, +it specifies your default '<A HREF="bookmark_help.html">Bookmark file</A>'. +<li>If multi-bookmarks is STANDARD or ADVANCED, +entering 'B' will invoke a menu in which you can specify +filepaths and descriptions of up to 26 bookmark files. +</ul> +The filepaths must be from your home directory and begin with './' +if subdirectories are included (e.g., './BM/lynx_bookmarks.html'). +<P> +Lynx will create bookmark files when you first 'a'dd a link, +but any subdirectories in the filepath must already exist. + +<H1><A NAME="FT">FTP sort criteria</A></H1> + +This allows you to specify how files will be sorted within FTP listings. +The current options include +`By Filename', `By Size', `By Type', `By Date'. + +<H1><A NAME="LD">List directory style</A></H1> + +Applies to Directory Editing. +Files and directories can be presented in the following ways: +<dl> +<dt><EM>Mixed style</EM>: Files and directories are listed together +in alphabetical order. +<dt><EM>Directories first</EM>: Files and directories are separated +into 2 alphabetical lists: directories are listed first. +<dt><EM>Files first</EM>: Files and directories are separated +into 2 alphabetical lists: files are listed first. +</dl> + +<H1><A NAME="DF">Show dot files</A></H1> + +If display/creation of hidden (dot) files/directories is enabled, +you can turn the feature on or off via this setting. + +<H1><A NAME="PC">Preferred Document Charset</A></H1> + +The character set you prefer if sets in addition to ISO-8859-1 and US-ASCII +are available from servers. Use MIME notation (e.g., ISO-8859-2) +and do not include ISO-8859-1 or US-ASCII, since those values are always +assumed by default. Can be a comma-separated list, which may be interpreted +by servers as descending order of preferences; you can make your order +of preference explicit by using `q factors' as defined by the HTTP protocol, +for servers which understand it: e.g., <kbd>iso-8859-5, utf-8;q=0.8</kbd>. + +<H1><A NAME="PL">Preferred Document Language</A></H1> + +The language you prefer if multi-language files are available from servers. +Use RFC 1766 tags, e.g., `en' English, `fr' French. Can be a comma-separated +list, and you can use `q factors' (see previous help item): +e.g., <kbd>da, en-gb;q=0.8, en;q=0.7</kbd> . + +<H1><A NAME="UA">User Agent</A></H1> + +The header string which Lynx sends to servers to indicate the User-Agent +is displayed here. Changes may be disallowed via the -restrictions switch. +Otherwise, the header can be changed temporarily to e.g., L_y_n_x/2.8.2 +for access to sites which discriminate against Lynx based on checks +for the presence of `Lynx' in the header. If changed during a Lynx session, +the default User-Agent header can be restored by deleting the modified string +in the Options Menu. Whenever the User-Agent header is changed, the current +document is reloaded, with the no-cache flags set, on exit from Options Menu. +Changes of the header are not saved in the .lynxrc file. +<P> +NOTE Netscape Communications Corp. has claimed that false transmissions +of `Mozilla' as the User-Agent are a copyright infringement, which will +be prosecuted. DO NOT misrepresent Lynx as Mozilla. The Options Menu issues +a warning about possible copyright infringement whenever the header is changed +to one which does not include `Lynx' or `lynx'. + </BODY> </HTML> + diff --git a/gnu/usr.bin/lynx/lynx_help/keystrokes/other_help.html b/gnu/usr.bin/lynx/lynx_help/keystrokes/other_help.html index 511ddaac4b7..2aa7f337493 100644 --- a/gnu/usr.bin/lynx/lynx_help/keystrokes/other_help.html +++ b/gnu/usr.bin/lynx/lynx_help/keystrokes/other_help.html @@ -17,7 +17,7 @@ d - Downloads the file pointed to by the current link and displays an option menu allowing the file to - be saved or transfered by configurable options. + be saved or transferred by configurable options. Can also be used when positioned on a form SUBMIT button to download the reply to a form submission. @@ -29,22 +29,22 @@ g - Allows you to enter any <a href="http://www.ncsa.uiuc.edu/demoweb/url-primer.html">URL</a> or filename that you wish to view, and then <em>goto</em> it. - + G - Allows you to edit the current document's URL and use that as a <em>goto</em> URL. - + ? or H - Hypertext help to explain how to navigate in Lynx and use its features. - i - Shows an index of files or subjects. This is - configurable by the System administrator, or + i - Shows an index of files or subjects. This is + configurable by the System administrator, or within documents that you may be viewing. - j - Allows you to enter a "short" name to execute a + j - Allows you to enter a "short" name to execute a jump command configured by your system administrator. Press "?" and ENTER to see a list of defined jump commands. - + k - Shows a list of key mappings. Keys remapped in "lynx.cfg" show up in this list. @@ -52,34 +52,36 @@ document, which can be used for rapid access to the links in large documents. - m - Returns to the first screen and empties the + m - Returns to the first screen and empties the history stack. p - Brings up a list of <A HREF="print_help.html">print commands</A>. - o - Brings up a list of setable <A HREF="option_help.html">options</A>. + o - Brings up a list of settable <A HREF="option_help.html">options</A>. - q - Quits Lynx. ('Q' quits without asking) + q - Quits Lynx. ('Q' quits without asking) - / - Search for a string of characters in the current - document case insensitive or case sensitive - depending on the options set. (see <A HREF="option_help.html">options)</A>. + / - Search for a string of characters in the current document + (case insensitive or case sensitive + depending on the <A HREF="option_help.html">options</A> set). s - Search through an external searchable indexed document. - n - Move to the next instance of a search string if you + n - Move to the next instance of a search string if you have searched previously. v - View a <A HREF="bookmark_help.html">Bookmark file</A>. + V - Go to the <A HREF="visited_help.html">Visited Links Page</A> + x - Force submission of form or link with no-cache. z - Abort a network transfer in progress. If any partial - data has been transfered it will be displayed. + data has been transferred it will be displayed. - <backspace> - displays the <a href="history_help.html">history page</A>. + <backspace> - displays the <a href="history_help.html">History Page</A>. - = - Show information about the file and link that you + = - Show information about the file and link that you are currently viewing. \ - Toggles between viewing the HTML source of a @@ -101,7 +103,7 @@ Note that any protected documents that are still in cache can still be accessed. - ` - Toggles minimal or valid comment parsing. When minimal, any + ` - Toggles minimal or valid comment parsing. When minimal, any two successive dashes followed by a close-angle-bracket will be treated as a comment terminator, emulating the parsing bug in Netscape v2.0. If historical comment parsing is set, that @@ -110,14 +112,15 @@ * - Toggles image_links mode on and off. When on, links will be created for all images, including inlines. - @ - Toggles raw 8-bit translations or CJK mode on and off. + @ - Toggles raw 8-bit translations or CJK mode on and off, only + for documents which does not specify character set explicitely. Should be on when the document's charset matches the - selected character set, and otherwise off so that 8-bit - characters will be reverse translated with respect to the - ISO-8859-1 conversion table for the character set (see - <A HREF="option_help.html">options)</A>. + display character set, and otherwise off so that 8-bit + characters will be translated by Lynx with respect to the + Assumed document charset, using approximations if necessary + (see <A HREF="option_help.html">options</A>). - [ - Toggles pseudo_inlines mode on and off. When on, inline + [ - Toggles pseudo_inlines mode on and off. When on, inline images which have no ALT string specified will have an "[INLINE]" pseudo-ALT string inserted in the Lynx display. When off, they will be treated as having ALT="" (i.e., @@ -134,7 +137,7 @@ 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. + an error message. " - Toggles valid or "soft" double-quote parsing. When soft, a close-angle-bracket will serve as both a close-double- @@ -145,7 +148,8 @@ CTRL-V - Switches to an alternative way of parsing HTML documents. This may help to get a more readable rendering of some - documents with invalidly placed HTML tags. + documents with invalidly placed HTML tags, <A + HREF="option_help.html#tagsoup">more details</A>. CTRL-W - Resets or cleans up the display. diff --git a/gnu/usr.bin/lynx/lynx_help/keystrokes/test_display.html b/gnu/usr.bin/lynx/lynx_help/keystrokes/test_display.html new file mode 100644 index 00000000000..b053daeb068 --- /dev/null +++ b/gnu/usr.bin/lynx/lynx_help/keystrokes/test_display.html @@ -0,0 +1,55 @@ +<!DOCTYPE html public "-//IETF//DTD HTML 3.0//EN"> +<HTML> +<HEAD> +<TITLE>Quick test for identifying display character set</TITLE> +<LINK rev="made" href="mailto:lynx-dev@sig.net"> +</HEAD> +<BODY> +<h1 ALIGN=LEFT>Try this page with Lynx 2.7.2 or above:</h1> + +If you see several letters instead of a single - your promised display charset +does not support this character so "7 bit approximation" is in effect. +If you see any single letter which definitely far from being supposed +you have a wrong lynx settings. +<em>Press 'o' for Options menu and change "Display character set"</em>. +Try again if necessary.<br> +When you are satisfied save your changes in Options menu, thanks. +<PRE> + + +0x00A9 © # COPYRIGHT SIGN + +0x00C7 Ç # LATIN CAPITAL LETTER C WITH CEDILLA + +0x00DC Ü # LATIN CAPITAL LETTER U WITH DIAERESIS + +0x00D1 Ñ # LATIN CAPITAL LETTER N WITH TILDE + +0x0107 ć # LATIN SMALL LETTER C WITH ACUTE +0x0108 Ĉ # LATIN CAPITAL LETTER C WITH CIRCUMFLEX +0x010C Č # LATIN CAPITAL LETTER C WITH CARON + + +0x03BB λ # GREEK SMALL LETTER LAMDA + +0x041B Л # CYRILLIC CAPITAL LETTER EL +0x042E Ю # CYRILLIC CAPITAL LETTER YU +0x043B л # CYRILLIC SMALL LETTER EL +0x044E ю # CYRILLIC SMALL LETTER YU + +0x2026 … # HORIZONTAL ELLIPSIS +0x2122 ™ # TRADE MARK SIGN + +0x255D ╝ # BOX DRAWINGS DOUBLE UP AND LEFT +0x255E ╞ # BOX DRAWINGS VERTICAL SINGLE AND RIGHT DOUBLE + +0xFB01 fi # LATIN SMALL LIGATURE FI + + + +</PRE> +This is only a quick test to see obvious problems. + + +</BODY> +</HTML> diff --git a/gnu/usr.bin/lynx/lynx_help/keystrokes/visited_help.html b/gnu/usr.bin/lynx/lynx_help/keystrokes/visited_help.html index ebb03a709b8..0a6874f3fc9 100644 --- a/gnu/usr.bin/lynx/lynx_help/keystrokes/visited_help.html +++ b/gnu/usr.bin/lynx/lynx_help/keystrokes/visited_help.html @@ -20,8 +20,8 @@ the URLs differ due to appended fragments), and is supplementary to the <p>You may <A HREF="movement_help.html">select</A> any link on the Visited Links Page to retrieve a document that you had previously visited, or you can use this list to save such links in your <A HREF="bookmark_help.html" ->bookmark files</A>, or to <A HREF="../Lynx_users_guide.html#9">Download</A> -them. +>bookmark files</A>, or to <A HREF="../Lynx_users_guide.html#RemoteSource" +>Download</A> them. <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 |