diff options
Diffstat (limited to 'lynx_help')
| -rw-r--r-- | lynx_help/Lynx_users_guide.html | 2 | ||||
| -rw-r--r-- | lynx_help/keystrokes/follow_help.html | 33 | ||||
| -rw-r--r-- | lynx_help/keystrokes/keystroke_help.html | 8 | ||||
| -rw-r--r-- | lynx_help/keystrokes/scrolling_help.html | 2 | ||||
| -rw-r--r-- | lynx_help/lynx_url_support.html | 73 |
5 files changed, 75 insertions, 43 deletions
diff --git a/lynx_help/Lynx_users_guide.html b/lynx_help/Lynx_users_guide.html index 64d84119..73a08910 100644 --- a/lynx_help/Lynx_users_guide.html +++ b/lynx_help/Lynx_users_guide.html @@ -831,7 +831,7 @@ return to Lynx or the '<em>></em>' command to save the options to a to distinguish the current link or OPTION from the others in the screen display. - <dt>Keypad as arrows, numbered links, or numbered links and form fields + <dt>Keypad as arrows, numbered links, numbered fields, or numbered links and form fields <dd>This option gives the choice among navigating with the arrow keys, or having every link numbered so that the links may be selected or made current by numbers as well as using the arrow diff --git a/lynx_help/keystrokes/follow_help.html b/lynx_help/keystrokes/follow_help.html index b5893963..901c0af8 100644 --- a/lynx_help/keystrokes/follow_help.html +++ b/lynx_help/keystrokes/follow_help.html @@ -8,9 +8,11 @@ <h1>+++ Follow link (or goto link or page) number Help +++<br> +++ Select option (or page) number Help +++</h1> -If a user has set <em>Keypad mode</em> to <em>Links are numbered</em> -or <em>Links and form fields are numbered</em> as the default or for -the current session via the <em>Options menu</em>, then hypertext links +If a user has set <em>Keypad mode</em> to <em>Links are numbered</em>, +or <em>Form fields are numbered</em>, +or <em>Links and form fields are numbered</em> +as the default or for the current session via the <em>Options menu</em>, +then hypertext links (and form fields, depending on the keypad mode) are prefixed with numbers in square brackets. Entering a keyboard or keypad number is treated as an <em>F_LINK_NUM</em> command, and should @@ -23,8 +25,10 @@ the document for that link as if you had paged or used other navigation commands to make it the current link and then ACTIVATE-ed it. The prompt can be invoked via '<em>0</em>', but it will not be treated as the lead digit for the number entry, whereas '<em>1</em>' through '<em>9</em>' both -invoke the prompt and are treated as the first digit. In <em>Links and -form fields are numbered</em> mode, if the number corresponds to a form +invoke the prompt and are treated as the first digit. +In <em>Form fields are numbered</em> +or <em>Links and form fields are numbered</em> mode, +if the number corresponds to a form field you will be positioned on that field, but if it is a submit button it will not be ACTIVATE-ed. @@ -32,8 +36,9 @@ it will not be ACTIVATE-ed. <em>123g</em>), then Lynx will make the link corresponding to that number the current link, paging as appropriate if the link does not appear in the currently displayed page. The '<em>g</em>' suffix is inferred (need -not be entered) for form fields in <em>Links and form fields are -numbered</em> mode. +not be entered) for form fields in +<em>Form fields are numbered</em> or +<em>Links and form fields are numbered</em> mode. <p>Alternatively, if the number is given a '<em>p</em>' suffix (e.g., <em>123p</em>), Lynx will make the page corresponding to that number @@ -72,8 +77,10 @@ then only '<em>0</em>', rather than every number, will be treated as an number:</em> prompt. The '<em>0</em>' will not be treated as the first digit for the number, or number plus suffix, entry. -<p>Numbers are associated with form fields only when <em>Links and form -fields are numbered</em> mode has been selected. If you have selected +<p>Numbers are associated with form fields only when +<em>Form fields are numbered</em> or +<em>Links and form fields are numbered</em> mode has been selected. +If you have selected <em>Numbers act as arrows</em> or <em>Links are numbered</em> mode, you can seek form fields in the document via WHEREIS searches for strings in their displayed values. If they are INPUT or TEXTAREA fields with no @@ -83,8 +90,10 @@ displayed document. <p ID="select-option">When you have invoked a popup window for a list of OPTIONs in a form's SELECT block, each OPTION is associated with a number, -and that number will be displayed in <em>Links and form fields are -numbered</em> mode. In any keypad mode, the <em>F_LINK_NUM</em> +and that number will be displayed in +<em>Form fields are numbered</em> or +<em>Links and form fields are numbered</em> mode. +In any keypad mode, the <em>F_LINK_NUM</em> ('<em>0</em>') command will invoke a <em>Select option (or page) number:</em> prompt, and you can enter a number, and optionally a '<em>g</em>' or '<em>p</em>' suffix, to select or seek an OPTION in that @@ -106,6 +115,7 @@ while viewing a popup window, the user can type to skip ahead 3 pages, and <em>50g-</em> will move the current selection back 50 options. This will work whether or not <em>keypad mode</em> is +<em>Form fields are numbered</em> or <em>Links and form fields are numbered</em> since options are numbered internally. If form field numbering is turned off, the option numbers won't appear on screen, @@ -159,6 +169,7 @@ a name/value pair for the fields should be included in the content submitted for the form, but the value should not be displayed in the rendered form. 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>Form fields are numbered</em> or <em>Links and form fields are numbered</em> keypad mode handling, nor includes an entry for it in the menus created for the LIST ('<em>l</em>') or ADDRLIST ('<em>A</em>') diff --git a/lynx_help/keystrokes/keystroke_help.html b/lynx_help/keystrokes/keystroke_help.html index d3ca4ede..699d01f8 100644 --- a/lynx_help/keystrokes/keystroke_help.html +++ b/lynx_help/keystrokes/keystroke_help.html @@ -105,6 +105,14 @@ CTRL-V prompts for a key command (allows <A HREF="../Lynx_users_guide.html#CtrlVNote" >escaping</A> from the field). + + Note that on most UNIX hosts, CTRL-V is bound + via stty to the lnext (literal-next) code but + the exact behavior of that is implementation + specific. On Solaris you must type CTRL-V + twice to use it, since it quotes the following + keystroke. + CTRL-U - Erase input line (<a href="edit_help.html" >more input line commands</a>) CTRL-G - Cancel input or transfer diff --git a/lynx_help/keystrokes/scrolling_help.html b/lynx_help/keystrokes/scrolling_help.html index 71a401d7..6ddec1ed 100644 --- a/lynx_help/keystrokes/scrolling_help.html +++ b/lynx_help/keystrokes/scrolling_help.html @@ -14,7 +14,7 @@ - (or b, - If you have moved down in a document, this or CTRL-B) will bring you back up one page (Page-Up). - If the 'Num Lock' on your keyboard is on, Lynx will translate + If the 'Num Lock' on your keyboard is on, Lynx translates the numbers of your keypad into movement commands as follows: 9 - page up diff --git a/lynx_help/lynx_url_support.html b/lynx_help/lynx_url_support.html index bee82050..ac2ccbb9 100644 --- a/lynx_help/lynx_url_support.html +++ b/lynx_help/lynx_url_support.html @@ -7,21 +7,22 @@ <BODY> <blockquote> -<em>[</em><a href="#http">http, https</a> <em>|</em> -<a href="#telnet">telnet, tn3270, rlogin</a> <em>|</em> -<a href="#gopher">gopher</a> <em>|</em> -<a href="#file">file</a> <em>|</em> -<a href="#ftp">ftp</a> <em>|</em> -<a href="#wais">wais</a> <em>|</em> -<a href="#news">news, nntp, snews</a> <em>|</em> -<a href="#newspost">newspost, newsreply, snewspost, snewsreply</a> <em>|</em> -<a href="#mailto">mailto</a> <em>|</em> -<a href="#finger">finger</a> <em>|</em> -<a href="#cso">cso</a> <em>|</em> -<a href="#bibp">bibp</a> <em>|</em> -<a href="#exec">lynxexec, lynxprog</a> <em>|</em> -<a href="#cgi">lynxcgi</a><em>|</em> -<a href="#internal">internal</a><em>]</em> +<em>[</em><a href="#http_url">http, https</a> <em>|</em> +<a href="#telnet_url">telnet, tn3270, rlogin</a> <em>|</em> +<a href="#gopher_url">gopher</a> <em>|</em> +<a href="#file_url">file</a> <em>|</em> +<a href="#ftp_url">ftp</a> <em>|</em> +<a href="#wais_url">wais</a> <em>|</em> +<a href="#news_url">news, nntp, snews</a> <em>|</em> +<a href="#newspost_url">newspost, newsreply, snewspost, snewsreply</a> <em>|</em> +<a href="#mailto_url">mailto</a> <em>|</em> +<a href="#finger_url">finger</a> <em>|</em> +<a href="#cso_url">cso</a> <em>|</em> +<a href="#bibp_url">bibp</a> <em>|</em> +<a href="#exec_url">lynxexec, lynxprog</a> <em>|</em> +<a href="#cgi_url">lynxcgi</a><em>|</em> +<a href="#ncftp_url">NcFTP</a> <em>|</em> +<a href="#internal_url">internal</a><em>]</em> </blockquote> <H1><em>URL Schemes Supported in Lynx</em></H1> @@ -74,7 +75,7 @@ Any partial or relative URLs within HTML documents are resolved according to the rules specified in RFC1808 and subsequent IETF drafts. <HR> -<H2><a name="http">The <em>http</em> and <em>https</em> URLs:</a></H2> +<H2><a name="http_url">The <em>http</em> and <em>https</em> URLs:</a></H2> Lynx handles http URLs exactly as specified in RFC1738. The format is: @@ -99,7 +100,7 @@ and associated red tape pose severe impediments to inclusion of this support in the general distributions of freeware WWW clients such as Lynx. Sorry. <HR> -<H2><a name="telnet" +<H2><a name="telnet_url" >The <em>telnet</em>, <em>tn3270</em>, and <em>rlogin</em> URLs:</a></H2> A <em>telnet</em> URL generally results in Lynx spawning a telnet @@ -123,7 +124,7 @@ for most TCP-IP software you will be prompted for a password whether or not one was included in the URL. <HR> -<H2><a name="gopher">The <em>gopher</em> URL:</a></H2> +<H2><a name="gopher_url">The <em>gopher</em> URL:</a></H2> The gopher URL takes the form: <pre> @@ -172,7 +173,7 @@ listings returned by gopher servers, but should be considered Lynxisms and UMN Gopherisms. <HR> -<H2><a name="file">The <em>file</em> URL:</a></H2> +<H2><a name="file_url">The <em>file</em> URL:</a></H2> The file URL is used to retrieve files or generate a directory listing on the local host. The host field can be <em>localhost</em> or a domain @@ -206,7 +207,7 @@ use the <em>showinfo</em> command (<em>=</em>) to see the file URL which Lynx created for it. <HR> -<H2><a name="ftp">The <em>ftp</em> URL:</a></H2> +<H2><a name="ftp_url">The <em>ftp</em> URL:</a></H2> The ftp URL has the general format: <pre> @@ -267,7 +268,7 @@ tilde (<em>~</em>) as for <a href="#file">file</a> URLs, e.g.: </pre> <HR> -<H2><a name="wais">The <em>wais</em> URL:</a></H2> +<H2><a name="wais_url">The <em>wais</em> URL:</a></H2> The wais URL is used to retrieve resources using the Wide Area Information System protocol. The format is: @@ -289,7 +290,7 @@ convert the server's reply into a hit list with URLs that include the the hit list. <HR> -<H2><a name="news" +<H2><a name="news_url" >The <em>news</em>, <em>nntp</em>, and <em>snews</em> URLs:</a></H2> The news and nntp URLs are handled by Lynx as specified in RFC1738, but @@ -349,7 +350,7 @@ are specific to each nntp server, unlike the unique identifiers for news messages. <HR> -<H2><a name="newspost" +<H2><a name="newspost_url" >The <em>newspost</em>, <em>newsreply</em>, <em>snewspost</em>, and <em>snewsreply</em> URLs:</a></H2> @@ -395,7 +396,7 @@ href="#mailto">mailto</a> URLs, with the qualification that they presently are supported only by Lynx. <HR> -<H2><a name="mailto">The <em>mailto</em> URL:</a></H2> +<H2><a name="mailto_url">The <em>mailto</em> URL:</a></H2> The mailto URL is used to provide links that when activated can be used to send a comment or the content of a FORM to an Internet email @@ -483,7 +484,7 @@ and the prefixed inclusion should be trimmed by the user to just those passages relevant to the message which will be sent. <HR> -<H2><a name="finger">The <em>finger</em> URL:</a></H2> +<H2><a name="finger_url">The <em>finger</em> URL:</a></H2> Lynx has full support for the finger protocol, but a format for finger URLs has not yet been adopted by the IETF. The formats supported by Lynx @@ -517,7 +518,7 @@ Lynx will handle such URLs equivalently to overt finger URLs, including creation of links for any strings which appear to be supported URLs. <HR> -<H2><a name="cso">The <em>cso</em> URL:</a></H2> +<H2><a name="cso_url">The <em>cso</em> URL:</a></H2> The cso URL is intended to provide a gateway to CSO/PH (QI) servers. The requests are made on port 105 by default (<em>:105</em>), with the @@ -539,7 +540,7 @@ to the server. Any strings in the reports returned for these requests converted into a link for accessing that URL. <HR> -<H2><a name="bibp">The <em>bibp</em> URL:</a></H2> +<H2><a name="bibp_url">The <em>bibp</em> URL:</a></H2> <p>Lynx provides built-in support for bibliographic protocol (BibP). BibP links are links to published works such as books or journal articles, @@ -548,7 +549,7 @@ by a local bibhost server (http://bibhost/) if it exists. Otherwise, resolution is performed by a document-specified server or a known global server. -<H2><a name="exec">The <em>lynxexec</em> and <em>lynxprog</em> URLs:</a></H2> +<H2><a name="exec_url">The <em>lynxexec</em> and <em>lynxprog</em> URLs:</a></H2> If execution of spawned commands has been enabled in your Lynx image, the lynxexec and lynxprog URLs can be used to execute arbitrary system commands @@ -575,7 +576,7 @@ from the utility invoked via lynxprog. solely for Lynx. <HR> -<H2><a name="cgi">The <em>lynxcgi</em> URL:</a></H2> +<H2><a name="cgi_url">The <em>lynxcgi</em> URL:</a></H2> The lynxcgi URL is implemented only on Unix, can be used as the ACTION for a FORM, and if enabled in your Lynx image has the format: @@ -602,7 +603,19 @@ more efficient and comprehensive than any code which might be incorporated within Lynx. <HR> -<H2><a name="internal">The <em>LYNXfoo</em> internal URLs:</a></H2> +<H2><a name="ncftp_url">The <em>NcFTP</em> URL:</a></H2> + +Lynx recognizes the NcFTP-style ftp URL, e.g., +<pre> + <cite>ftpHost</cite>:<cite>fileSpecification</cite> +</pre> +for example +<pre><code> + ftp.gnu.org:/pub/gnu +</code></pre> +<HR> + +<H2><a name="internal_url">The <em>LYNXfoo</em> internal URLs:</a></H2> Lynx uses a variety of private URL schemes for communication among its internal modules. They start with uppercase letters <code>LYNX</code> |