diff options
author | Anil Madhavapeddy <avsm@cvs.openbsd.org> | 2004-06-22 04:01:52 +0000 |
---|---|---|
committer | Anil Madhavapeddy <avsm@cvs.openbsd.org> | 2004-06-22 04:01:52 +0000 |
commit | 07f9a9d13ea0b7f12cf124c7c25c9b01c96c9369 (patch) | |
tree | 63b3492941bfdd52a92247669895596bbb90b758 /gnu/usr.bin/lynx/lynx.hlp | |
parent | 48e173e619472dce9fa16a21cb6fb6ac6a9e3d24 (diff) |
update to lynx 2.8.5rel.1
tested todd@,naddy@. millert@ deraadt@ ok
Diffstat (limited to 'gnu/usr.bin/lynx/lynx.hlp')
-rw-r--r-- | gnu/usr.bin/lynx/lynx.hlp | 322 |
1 files changed, 183 insertions, 139 deletions
diff --git a/gnu/usr.bin/lynx/lynx.hlp b/gnu/usr.bin/lynx/lynx.hlp index 843cb202725..a4b260c1df8 100644 --- a/gnu/usr.bin/lynx/lynx.hlp +++ b/gnu/usr.bin/lynx/lynx.hlp @@ -39,7 +39,7 @@ intermixed in option names (in the reference below options are with one dash before them and with underscores). - - If the argument is only '-', then Lynx expects to + - If the argument is only `-', 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 -get_data or -post_data @@ -119,28 +119,40 @@ You can use the data written using the -cmd_log option. Lynx will ignore other information which the command-logging may have written to the - logfile. - - -color forces color mode on, if available. Default color - control sequences which work for many terminal - types are assumed if the terminal capability - description does not specify how to handle color. - Lynx needs to be compiled with the slang library - for this flag, it is equivalent to setting the - COLORTERM environment variable. (If color support + logfile. Each line of the command script contains + either a comment beginning with "#", or a keyword: + + exit causes the script to stop, and forces lynx to + exit immediately. + + key the character value, in printable form. Cursor + and other special keys are given as names, e.g., + "Down Arrow". Printable 7-bit ASCII codes are + given as-is, and hexadecimal values represent + other 8-bit codes. + + set followed by a "name=value" allows one to + override values set in the lynx.cfg file. + + -color forces color mode on, if available. Default color + control sequences which work for many terminal + types are assumed if the terminal capability + description does not specify how to handle color. + Lynx needs to be compiled with the slang library + for this flag, it is equivalent to setting the + COLORTERM environment variable. (If color support is instead provided by a color-capable curses library like ncurses, Lynx relies completely on the - terminal description to determine whether color - mode is possible, and this flag is not needed and - thus unavailable.) A saved show_color=always - setting found in a .lynxrc file at startup has the - same effect. A saved show_color=never found in + terminal description to determine whether color + mode is possible, and this flag is not needed and + thus unavailable.) A saved show_color=always + setting found in a .lynxrc file at startup has the + same effect. A saved show_color=never found in .lynxrc on startup is overridden by this flag. -connect_timeout=N - Sets the connection timeout, where N is given in - seconds. This is not available under DOS (use the - sockdelay parameter of WATTCP under DOS). + Sets the connection timeout, where N is given in + seconds. -cookie_file=FILENAME specifies a file to use to read cookies. If none @@ -155,7 +167,9 @@ -cookies toggles handling of Set-Cookie headers. - -core toggles forced core dumps on fatal errors. + -core toggles forced core dumps on fatal errors. Turn + this option off to ask lynx to force a core dump if + a fatal error occurs. -crawl with -traversal, output each page to a file. with -dump, format output as with -traversal, but to @@ -169,6 +183,8 @@ separate incremental display stages with MessageSecs delay + -delay add DebugSecs delay after each progress-message + -display=DISPLAY set the display variable for X rexec-ed programs. @@ -184,7 +200,7 @@ or one specified on the command line to standard output. This can be used in the following way: - lynx -dump http://www.trill-home.com/lynx.html + lynx -dump http://www.subir.com/lynx.html -editor=EDITOR enable external editing, using the specified @@ -209,13 +225,17 @@ include all versions of files in local VMS directory listings. + -find_leaks + toggle memory leak-checking. Normally this is not + compiled-into your executable, but when it is, it + can be disabled for a session. + -force_empty_hrefless_a - force HREF-less 'A' elements to be empty (close + force HREF-less `A' elements to be empty (close them as soon as they are seen). -force_html forces the first document to be interpreted as - HTML. -force_secure @@ -232,7 +252,7 @@ -get_data 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 '---'. + terminated by a line that starts with `---'. -head send a HEAD request for the mime headers. @@ -253,7 +273,7 @@ ignore hidden links do not appear even in listings. -historical - toggles use of '>' or '-->' as a terminator for + toggles use of `>' or `-->' as a terminator for comments. -homepage=URL @@ -294,6 +314,9 @@ -minimal toggles minimal versus valid comment parsing. + -nested_tables + toggles nested-tables logic (for debugging). + -newschunksize=NUMBER number of articles in chunked news listings. @@ -385,7 +408,7 @@ -post_data 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 '---'. + terminated by a line that starts with `---'. -preparsed show HTML source preparsed and reformatted when @@ -433,7 +456,6 @@ to all restricted, except for: inside_telnet, outside_telnet, inside_ftp, outside_ftp, inside_rlogin, outside_rlogin, inside_news, - outside_news, telnet_port, jump, mail, print, exec, and goto. The settings for these, as well as additional goto restrictions for specific URL @@ -467,7 +489,7 @@ file_url - disallow using G)oto, served links or bookmarks for file: URLs. - goto - disable the 'g' (goto) command. + goto - disable the `g' (goto) command. inside_ftp - disallow ftps for people coming from inside your domain (utmp required for selectivity). @@ -484,9 +506,10 @@ from inside your domain (utmp required for selectivity). - jump - disable the 'j' (jump) command. + jump - disable the `j' (jump) command. multibook - disallow multiple bookmarks. + mail - disallow mail. news_post - disallow USENET News posting. @@ -568,7 +591,7 @@ -soft_dquotes toggles emulation of the old Netscape and Mosaic - bug which treated '>' as a co-terminator for + bug which treated `>' as a co-terminator for double-quotes and tags. -source @@ -620,42 +643,48 @@ 1=SGML character parsing states 2=color-style 4=TRST (table layout) + 8=config (lynx.cfg and .lynxrc contents) + 16=binary string copy/append, used in form data + construction. -traversal - traverse all http links derived from startfile. - When used with -crawl, each link that begins with - the same string as startfile is output to a file, + traverse all http links derived from startfile. + When used with -crawl, each link that begins with + the same string as startfile is output to a file, intended for indexing. See CRAWL.announce for more information. trim_input_fields trim input text/textarea fields in forms. + -underline_links + toggles use of underline/bold attribute for links. + -underscore toggles use of _underline_ format in dumps. -use_mouse - turn on mouse support, if available. Clicking the + turn on mouse support, if available. Clicking the left mouse button on a link traverses it. Clicking the right mouse button pops back. Click on the top - line to scroll up. Click on the bottom line to - scroll down. The first few positions in the top - and bottom line may invoke additional functions. - Lynx must be compiled with ncurses or slang to + line to scroll up. Click on the bottom line to + scroll down. The first few positions in the top + and bottom line may invoke additional functions. + Lynx must be compiled with ncurses or slang to support this feature. If ncurses is used, clicking - the middle mouse button pops up a simple menu. - Mouse clicks may only work reliably while Lynx is + the middle mouse button pops up a simple menu. + Mouse clicks may only work reliably while Lynx is idle waiting for input. -useragent=Name set alternate Lynx User-Agent header. -validate - accept only http URLs (for validation). Complete + accept only http URLs (for validation). Complete security restrictions also are implemented. -verbose - toggle [LINK], [IMAGE] and [INLINE] comments with + toggle [LINK], [IMAGE] and [INLINE] comments with filenames of these images. -version @@ -665,65 +694,70 @@ enable vi-like key movement. -wdebug - enable Waterloo tcp/ip packet debug (print to watt - debugfile). This applies only to DOS versions + enable Waterloo tcp/ip packet debug (print to watt + debugfile). This applies only to DOS versions compiled with WATTCP or WATT-32. -width=NUMBER - number of columns for formatting of dumps, default + number of columns for formatting of dumps, default is 80. -with_backspaces - emit backspaces in output if -dumping or -crawling - (like 'man' does) + emit backspaces in output if -dump'ing or + -crawl'ing (like `man' does) 2 Commands - o Use Up arrow and Down arrow to scroll through hypertext + o Use Up arrow and Down arrow to scroll through hypertext links. - o Right arrow or Return will follow a highlighted + o Right arrow or Return will follow a highlighted hypertext link. o Left Arrow will retreat from a link. o Type "H" or "?" for online help and descriptions of key- stroke commands. - o Type "K" for a complete list of the current key-stroke + o Type "K" for a complete list of the current key-stroke command mappings. 2 Environment - In addition to various "standard" environment variables - such as HOME, PATH, USER, DISPLAY, TMPDIR, etc, Lynx - utilizes several Lynx-specific environment variables, if + In addition to various "standard" environment variables + such as HOME, PATH, USER, DISPLAY, TMPDIR, etc, Lynx + utilizes several Lynx-specific environment variables, if they exist. - Others may be created or modified by Lynx to pass data to - an external program, or for other reasons. These are + Others may be created or modified by Lynx to pass data to + an external program, or for other reasons. These are listed separately below. - See also the sections on SIMULATED CGI SUPPORT and NATIVE + See also the sections on SIMULATED CGI SUPPORT and NATIVE LANGUAGE SUPPORT, below. Note: Not all environment variables apply to all types of - platforms supported by Lynx, though most do. Feedback on + platforms supported by Lynx, though most do. Feedback on platform dependencies is solicited. Environment Variables Used By Lynx: - COLORTERM If set, color capability for the + COLORTERM If set, color capability for the terminal is forced on at startup time. - The actual value assigned to the + The actual value assigned to the variable is ignored. This variable is only meaningful if Lynx was built - using the slang screen-handling + 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 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 + userdefs.h file, during installation. + See the userdefs.h file for more information. + LYNX_LOCALEDIR If set, this variable overrides the + compiled-in location of the locale + directory which contains native + language (NLS) message text. + LYNX_LSS This variable, if set, specifies the location of the default Lynx character style sheet file. [Currently only @@ -755,7 +789,6 @@ 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). @@ -785,6 +818,12 @@ Lynx Users Guide for additional details and examples. + SSL_CERT_DIR Set to the directory containing + trusted certificates. + + SSL_CERT_FILE Set to the full path and filename for + your file of trusted certificates. + WWW_access_GATEWAY Lynx still supports use of gateway servers, with the servers specified via "WWW_access_GATEWAY" variables @@ -792,7 +831,7 @@ be "http", "ftp", "gopher" or "wais"), however most gateway servers have been discontinued. Note that you do not - include a terminal '/' for gateways, + include a terminal `/' for gateways, but do for proxies specified by PROTOCOL_proxy environment variables. See Lynx Users Guide for details. @@ -853,35 +892,41 @@ file as if the -trace option were supplied. - LYNX_VERSION This variable is always set by Lynx, + LYNX_TRACE_FILE If set, overrides the compiled-in name + of the trace file, which is either + Lynx.trace or LY-TRACE.LOG (the latter + on the DOS platform). The trace file + is in either case relative to the home + directory. + + 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 + 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 + 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 (see OPTIONS section above), 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 + 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. 2 Simulated Cgi Support - If built with the cgi-links option enabled, Lynx allows - access to a cgi script directly without the need for an + 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 + When executing such "lynxcgi scripts" (if enabled), the + following variables may be set for simulating a CGI environment: CONTENT_LENGTH @@ -910,115 +955,114 @@ SERVER_SOFTWARE - Other environment variables are not inherited by the + 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 + 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 + should be consulted for general information on CGI script programming. 2 Native Language Support - 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 + 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 + The following environment variables may be used to alter default settings: - LANG This variable, if set, will override - the default message language. It is + 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 language. Language codes are NOT the same as the country codes given in ISO 3166. - LANGUAGE This variable, if set, will override + LANGUAGE This variable, if set, will override the default message language. This is - a GNU extension that has higher - priority for setting the message + 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 + 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 + LINGUAS This variable, if set prior to configuration, limits the installed languages to specific values. It is a - space-separated list of two-letter + 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 + NLSPATH This variable, if set, is used as the path prefix for message catalogs. 2 Notes This is the Lynx v2.8.4 Release - If you wish to contribute to the further development of - Lynx, subscribe to our mailing list. Send email to - <majordomo@sig.net> with "subscribe lynx-dev" as the only + If you wish to contribute to the further development of + Lynx, subscribe to our mailing list. Send email to + <majordomo@sig.net> with "subscribe lynx-dev" as the only line in the body of your message. - Send bug reports, comments, suggestions to <lynx- + Send bug reports, comments, suggestions to <lynx- dev@sig.net> after subscribing. - Unsubscribe by sending email to <majordomo@sig.net> with - "unsubscribe lynx-dev" as the only line in the body of - - your message. Do not send the unsubscribe message to the + Unsubscribe by sending email to <majordomo@sig.net> with + "unsubscribe lynx-dev" as the only line in the body of + your message. Do not send the unsubscribe message to the lynx-dev list, itself. 2 See Also - catgets(3), curses(3), environ(7), execve(2), ftp(1), - gettext(GNU), localeconv(3), ncurses(3), setlocale(3), + catgets(3), curses(3), environ(7), execve(2), ftp(1), + gettext(GNU), localeconv(3), ncurses(3), setlocale(3), slang(?), termcap(5), terminfo(5), wget(GNU) - Note that man page availability and section numbering is - somewhat platform dependent, and may vary from the above + Note that man page availability and section numbering is + somewhat platform dependent, and may vary from the above references. - A section shown as (GNU), is intended to denote that the - topic may be available via an info page, instead of a man - page (i.e., try "info subject", rather than "man subject"). + A section shown as (GNU), is intended to denote that the + topic may be available via an info page, instead of a man + page (i.e., try "info subject", rather than "man subject"). - A section shown as (?) denotes that documentation on the + A section shown as (?) denotes that documentation on the topic exists, but is not part of an established documentation - retrieval system (see the distribution files associated - with the topic, or contact your System Administrator + retrieval system (see the distribution files associated + with the topic, or contact your System Administrator for further information). 2 Acknowledgments Lynx has incorporated code from a variety of sources along the way. The earliest versions of Lynx included code from - Earl Fogel of Computing Services at the University of - Saskatchewan, who implemented HYPERREZ in the Unix envi- - ronment. HYPERREZ was developed by Niel Larson of - Think.com and served as the model for the early versions - of Lynx. Those versions also incorporated libraries from - the Unix Gopher clients developed at the University of - Minnesota, and the later versions of Lynx rely on the WWW - client library code developed by Tim Berners-Lee and the - WWW community. Also a special thanks to Foteos Macrides - who ported much of Lynx to VMS and did or organized most - of its development since the departures of Lou Montulli - and Garrett Blythe from the University of Kansas in the - summer of 1994 through the release of v2.7.2, and to ev- - eryone on the net who has contributed to Lynx's develop- + Earl Fogel of Computing Services at the University of + Saskatchewan, who implemented HYPERREZ in the Unix envi- + ronment. HYPERREZ was developed by Niel Larson of + Think.com and served as the model for the early versions + of Lynx. Those versions also incorporated libraries from + the Unix Gopher clients developed at the University of + Minnesota, and the later versions of Lynx rely on the WWW + client library code developed by Tim Berners-Lee and the + WWW community. Also a special thanks to Foteos Macrides + who ported much of Lynx to VMS and did or organized most + of its development since the departures of Lou Montulli + and Garrett Blythe from the University of Kansas in the + summer of 1994 through the release of v2.7.2, and to ev- + eryone on the net who has contributed to Lynx's develop- ment either directly (through patches, comments or bug re- - ports) or indirectly (through inspiration and development + ports) or indirectly (through inspiration and development of other systems). 2 Authors - Lou Montulli, Garrett Blythe, Craig Lavender, Michael + Lou Montulli, Garrett Blythe, Craig Lavender, Michael Grobe, Charles Rezac Academic Computing Services University of Kansas |