From d97a65137382daf2f896a947ba680c095f7ab664 Mon Sep 17 00:00:00 2001 From: "Thomas E. Dickey" Date: Mon, 18 Jan 1999 12:35:47 -0500 Subject: snapshot of project "lynx", label v2-8-2dev_14 --- lynx_help/keystrokes/environments.html | 28 +++-- lynx_help/keystrokes/keystroke_help.html | 12 +- lynx_help/keystrokes/option_help.html | 188 +++++++++++++++---------------- lynx_help/keystrokes/other_help.html | 34 +++--- 4 files changed, 136 insertions(+), 126 deletions(-) (limited to 'lynx_help/keystrokes') diff --git a/lynx_help/keystrokes/environments.html b/lynx_help/keystrokes/environments.html index 7a832e8a..a735894a 100644 --- a/lynx_help/keystrokes/environments.html +++ b/lynx_help/keystrokes/environments.html @@ -97,12 +97,12 @@ Environment Variables Used By Lynx: 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, + 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, + by setting environment variables of + the form PROTOCOL_proxy (literally: + http_proxy, ftp_proxy, gopher_proxy, etc), to "http://some.server.dom:port/". See details and examples. @@ -343,8 +343,11 @@ Proxy: 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. Here is - an example use of "no_proxy": + 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" @@ -360,9 +363,13 @@ Proxy: 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 "*". + "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. @@ -374,8 +381,9 @@ Proxy: Other WWW clients may require that the http server's configuration file have "Map file:* ftp:*" in it to perform that conversion. - The proxy and no_proxy variables also can be set at run time via - lynx.cfg. + 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). Win32 (95/NT) and 386 DOS diff --git a/lynx_help/keystrokes/keystroke_help.html b/lynx_help/keystrokes/keystroke_help.html index 3a2724ae..aa7a3da1 100644 --- a/lynx_help/keystrokes/keystroke_help.html +++ b/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 - + OTHER: ? (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 alternative parsing of HTML documents CTRL-W - Refresh the screen CTRL-U - Erase input line (more input line commands) 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 Cookie Jar Page - numbers - Invoke the prompt + numbers - Invoke the prompt Follow link (or goto link or page) number: or the diff --git a/lynx_help/keystrokes/option_help.html b/lynx_help/keystrokes/option_help.html index 594010d9..6d9ae0f6 100644 --- a/lynx_help/keystrokes/option_help.html +++ b/lynx_help/keystrokes/option_help.html @@ -17,7 +17,6 @@ compiled in or chosen in `lynx.cfg':

  • Cookies
  • Editor
  • Emacs keys -
  • Execution links
  • Keypad mode
  • Line edit style
  • Personal Mail Address @@ -26,10 +25,13 @@ compiled in or chosen in `lynx.cfg':

  • Show cursor for current link or option
  • User Mode
  • VI keys +
  • Display Character set
  • X DISPLAY variable
  • Document Layout @@ -37,16 +39,12 @@ compiled in or chosen in `lynx.cfg':

    -
  • Character Set Options -
  • File Management Options +
  • Show dot files +
  • Execution links
  • Headers transferred to remote server
    • Preferred Document Charset @@ -70,7 +68,7 @@ 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). -

      Note: setting emacs keys does not affect the line-editor bindings. +

      Note: setting emacs keys does not affect the line-editor bindings.

      Execution links

      @@ -85,13 +83,13 @@ 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. -

      Line edit style

      - -This allows you to set alternate key bindings for the built-in line editor, -if your system administrator has installed -Alternate Bindings. -Otherwise, Lynx uses the Default Binding. - +

      Line edit style

      + +This allows you to set alternate key bindings for the built-in line editor, +if your system administrator has installed +Alternate Bindings. +Otherwise, Lynx uses the Default Binding. +

      Personal Mail Address

      You may set your mail address here so that when mailing messages @@ -167,38 +165,67 @@ for beginners.
      Advanced: The URL is shown on the status line. -

      HTML error tolerance

      - -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: -"SortaSGML" attempts to enforce valid nesting of most tags -at an earlier stage of processing, while "TagSoup" 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. - -

      -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 -help on following links by -number 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. - -

      -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. +

      Assumed document character set

      + +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. + +

      Raw 8-bit or CJK mode

      + +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. + +

      HTML error recovery

      + +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: +"SortaSGML" attempts to enforce valid nesting of most tags +at an earlier stage of processing, while "TagSoup" 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. + +

      +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 +help on following links by +number 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. + +

      +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.