snapshot of project "lynx", label v2-7-1ac_0-105

4 files changed, 57 insertions, 21 deletions

diff --git a/lynx_help/Lynx_users_guide.html b/lynx_help/Lynx_users_guide.html
index 1843e1d8..cd0c36d0 100644
--- a/lynx_help/Lynx_users_guide.html
+++ b/lynx_help/Lynx_users_guide.html
@@ -597,10 +597,10 @@ return to Lynx or the '<em>&gt;</em>' command to save the options to a
    <dt>Display Character set
 	<dd>This option 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
+	    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
+	    other than 7-bit ASCII can be displayed correctly, using
 	    approximations if necessary.  You must have the selected
 	    character set installed on your terminal.
 
@@ -630,7 +630,7 @@ return to Lynx or the '<em>&gt;</em>' command to save the options to a
 	    NEVER are not offered in anonymous accounts.  If saved to a
 	    <em>.lynxrc</em> 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
+	    If Lynx is built with the slang library, this is equivalent to
 	    having included the <em>-color</em> command line switch or having the
 	    <em>COLORTERM</em> environment variable set. If color support is
 	    provided by curses or ncurses, this is equivalent to the default
@@ -648,7 +648,7 @@ return to Lynx or the '<em>&gt;</em>' command to save the options to a
 	    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
+	    slang library is used) if forced on via the
 	    <em>-color</em> switch or <em>COLORTERM</em> variable.  This
 	    default behavior always is used in anonymous accounts, or if
 	    the <em>option_save</em> restriction is set explicitly.  If
@@ -1058,6 +1058,18 @@ commands.
 	    buffer for goto URLs, and can be accessed for further
 	    modification via the '<em>g</em>' command.
 
+   <dt><em>E</em>
+  	<dd>The '<em>E</em>' command allows you to edit the URL (or ACTION)
+	    of the current link and then use that as a goto URL.  Pressing
+  	    the '<em>E</em>' command will bring up a prompt asking you
+	    to edit the current link's URL.  If you do not modify it, or
+	    completely delete it, or enter Control-G, the command will be
+	    cancelled.  Otherwise, the request for the 'E'dited URL will be
+	    sent with method GET, and will be entered into the circular
+	    buffer for goto URLs so that it can be accessed for further
+	    modification via the '<em>g</em>' command.  Note that lower
+	    case 'e' invokes the editor for the current document.
+
    <dt><em>=</em>
   	<dd>The '<em>=</em>' command shows information about the current
 	    document and the currently selected link if there is one.  The
@@ -1877,7 +1889,7 @@ where
              <dt><code>-child</code>
     		<dd>exit on left-arrow in startfile, and disable save to disk.
              <dt><code>-color</code>
-    		<dd>forces color mode on, if available.  Default color control sequences
+		<dd>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.
@@ -2234,8 +2246,8 @@ of Academic Computing Services at The University of Kansas.  Lynx was
 implemented by Lou Montulli and maintained by Garrett Arch Blythe and
 Craig Lavender.
 
-<p><em>Foteos Macrides</em> and members of the <a href="lynx-dev.html">
-lynx-dev</a> list have developed and supported Lynx since release of v2.3
+<p><em>Foteos Macrides</em> and members of the
+<a href="lynx-dev.html">lynx-dev</a> list have developed and supported Lynx since release of v2.3
 in May 1994. The Lynx2-3FM code set was released as v2.4 in June 1995.
 The Lynx2-4FM code set was released as v2.5 in May 1996. The Lynx2-5FM
 code set was released as v2.6 in September 1996. The Lynx2-6FM code set
diff --git a/lynx_help/keystrokes/keystroke_help.html b/lynx_help/keystrokes/keystroke_help.html
index e41a7a9e..f3a57bc3 100644
--- a/lynx_help/keystrokes/keystroke_help.html
+++ b/lynx_help/keystrokes/keystroke_help.html
@@ -32,7 +32,9 @@
   <A HREF="dired_help.html">DIRED</A>:       c	      -	Create a new file
 	       d	      -	Download selected file
 	       e	      - Edit selected file
-               f              - Show a full menu of options for current file
+	       E	      - Edit the current link's URL (or ACTION) and
+                                use that as a goto URL.
+	       f	      - Show a full menu of options for current file
 	       m	      - Modify the name or location of selected file
 	       r              - Remove selected file
 	       t              - Tag highlighted file
diff --git a/lynx_help/keystrokes/other_help.html b/lynx_help/keystrokes/other_help.html
index b43f8326..511ddaac 100644
--- a/lynx_help/keystrokes/other_help.html
+++ b/lynx_help/keystrokes/other_help.html
@@ -21,6 +21,12 @@
 		Can also be used when positioned on a form SUBMIT
 		button to download the reply to a form submission.
 
+       e      - Allows you to edit the current document if it is a
+		local file.
+
+       E      - Allows you to edit the current link's URL (or ACTION) and
+		use that as a <em>goto</em> URL.
+
        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.
                         
diff --git a/lynx_help/lynx_url_support.html b/lynx_help/lynx_url_support.html
index 0237733d..154371e1 100644
--- a/lynx_help/lynx_url_support.html
+++ b/lynx_help/lynx_url_support.html
@@ -397,17 +397,17 @@ ENCTYPE="text/plain"<BR>
 <tab indent="14">...<BR>
 <tab indent="12">&lt;/FORM&gt;</em>
 
-<p>Note that a TITLE attribute for FORM has been proposed but not included
-in any HTML specifications or drafts, and should be considered a Lynxism
-until/unless it is.  Some clients use a SUBJECT attribute for this purpose
+<p>Note that a TITLE attribute for FORM is now included in the HTML
+specifications.  Some clients use a SUBJECT attribute for this purpose
 in FORM tags, and Lynx recognizes that as a synonym for TITLE.
 
-<p>Lynx also will process any <em>cc=someone@host</em> and/or
-<em>body=Blah</em> fields in <em>?searchpart</em> tack-ons to mailto
-URLs.  The <em>cc</em> values can be single addresses, or comma- or
-semi-colon-separated lists of addresses.  All addresses, and any
-<em>body</em> values, will be offered for approval by the user before
-proceeding with a mailing, and any other name=value pairs in the
+<p>Lynx also will process any <em>to=address(es)</em>,
+<em>cc=address(es)</em>, <em>keywords=word_list</em> and/or
+<em>body=message</em> fields in <em>?searchpart</em> tack-ons to mailto
+URLs.  The <em>to</em> and/or <em>cc</em> values can be single addresses,
+or comma- or semi-colon-separated lists of addresses.  All addresses,
+and any <em>body</em> values, will be offered for approval by the user
+before proceeding with a mailing.   Any other name=value pairs in the
 <em>?searchpart</em> will be ignored.  Also, if the mailto URL is the
 ACTION for a FORM, any <em>body</em> in a <em>?searchpart</em> tack-on
 will be ignored, because the body of the mailing must be constructed
@@ -415,9 +415,12 @@ solely from the the FORM's content.  Lynx expects multiple name=value
 pairs in a <em>?searchpart</em> tack-on to be separated by ampersands,
 as in the original Netscape implementation, and in an equally ill-advised
 IETF draft of that implementation (<a
-href="ftp://ftp.isi.edu/internet-drafts/draft-hoffman-mailto-url-00.txt"
->draft-hoffman-mailto-url-00.txt</a>).  These should be represented as
-entities (<em>&amp;amp;</em>) in the HTML markup.
+href="ftp://ftp.isi.edu/internet-drafts/draft-hoffman-mailto-url-03.txt"
+>draft-hoffman-mailto-url-03.txt</a>).  These should be represented as
+entities (<em>&amp;amp;</em>) in the HTML markup.  This functionality
+is generally desired, but the IETF backward compatibility principal
+normally would lead to a new scheme being used (e.g., <em>mail:</em>, or
+<em>smtp:</em>), rather than breaking <em>mailto:</em> implementations.
 
 <p>If <em>ENCTYPE="text/plain"</em> is specified for a FORM with a mailto
 ACTION, Lynx will not hex escape the name=value pairs of the FORM's content,
@@ -500,6 +503,19 @@ to the server.   Any strings in the reports returned for these requests
 converted into a link for accessing that URL.
 <HR WIDTH="100%">
 
+<H2><a name="chargen">The <em>chargen</em> URL:</a></H2>
+
+The chargen URL is intended to provide a gateway to the chargen service.
+The requests are made on port 19 (<em>:19</em>).  You can omit the port,
+and no other value is allowed.  The format is:<BR>
+<tab indent="12"><em>chargen://host</em><BR>
+
+<p>Lynx will accept approximately 55 lines of characters in the stream
+returned by the server, then close the connection and display the lines
+as PRE formatted text.  Note that if port 19 is used for a URL with a
+scheme other than chargen, the URL will be rejected by Lynx.
+<HR WIDTH="100%">
+
 <H2><a name="exec">The <em>lynxexec</em> and <em>lynxprog</em> URLs:</a></H2>
 
 If execution of spawned commands has been enabled in your Lynx image, the