lynx-dev
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: lynx-dev dev.15 patch 7 - doc updates for recent changes


From: Leonid Pauzner
Subject: Re: lynx-dev dev.15 patch 7 - doc updates for recent changes
Date: Tue, 30 Nov 1999 18:44:58 +0300 (MSK)

30-Nov-99 06:34 Klaus Weide wrote:
> Some doc changes only.

few typos:

> Index: 2.25/lynx_help/Lynx_users_guide.html
> --- 2.25/lynx_help/Lynx_users_guide.html Thu, 25 Nov 1999 13:27:27 -0600
> +++ 2.25(w)/lynx_help/Lynx_users_guide.html Mon, 29 Nov 1999 20:43:25 -0600
> @@ -1375,23 +1375,77 @@
>      href="#submit">submit</a> the form if the text entry field is the
>      only non-hidden field in the form.

> +    If <A NAME="tna">"Textfields Need Activation"</A> mode is turned on,
> +    then text entry fields do not become active immediately upon being
> +    selected, as normally.  Keystrokes have their normal command meaning
> +    unless the Line Editor gets activated with <em>Return</em> or <em>Left
                                                                         ^^^^
should that be "Right Arrow" ?

> +    Arrow</em>.  This mode can be used to avoid "getting stuck" in input
> +    fields, especially by users that rearely fill out forms.
...

> +    NB when NOT in the Line Editor, <em>^V</em> is by default bound
> +    to the command
> +    to switch between SortaSGML and TagSoup HTML parsing
> +    (i.e., SWITCH_DTD).
> +    To avoid confusion, either of these separate functions could be changed
> +    (mapped away) with a KEYMAP directive in <em>lynx.cfg</em>.  For
> +    example,<pre></pre>
               ^^^^^^^^^^^?
> +    &nbsp;&nbsp;KEYMAP:^V:DO_NOTHING<br>
> +    &nbsp;&nbsp;KEYMAP:#:SWITCH_DTD<pre></pre>
> +    would map SWITCH_DTD away from <em>^V</em> to <em>#</em>, while leaving
> +    its default Line Editor function as a command escape in place.  On the
> +    other hand,<pre></pre>
                  ^^^^^^^^^^^?
> +    &nbsp;&nbsp;KEYMAP:^V::NOP:1<br>
> +    &nbsp;&nbsp;KEYMAP:^_::LKCMD:1<pre></pre>
> +    would move <em>^V</em>'s Line Editor binding as command escape to
> +    <em>^_</em> for the first Line Edit style, letting <em>^V</em> still
> +    act as SWITCH_DTD
> +    outside of text input fields.
> +    </DIV>

> Index: 2.25/lynx_help/lynx_url_support.html
> --- 2.25/lynx_help/lynx_url_support.html Thu, 25 Nov 1999 07:30:47 -0600
> +++ 2.25(w)/lynx_help/lynx_url_support.html Mon, 29 Nov 1999 06:03:12 -0600
> @@ -594,22 +594,42 @@

>  <H2><a name="internal">The <em>LYNXfoo</em> internal URLs:</a></H2>

> -Lynx uses a variety of internal URL schemes as structured stream
> -objects for communication among its display modules.  If you discover
> -what they are, and are tempted to use them externally in documents,
> -find the self-restraint to <em>resist</em> that temptation!!!
> +Lynx uses a variety of private URL schemes form communication among its
                          ^^^^^^^^^^^^^^^^^^^ (OK)
> +internal modules.  They start with uppercase letters <code>LYNX</code>
> +by convention, although, as input, URL schemes are recognized in a
> +case-insensitive manner.
...

> -<p>If you <em>must</em> try one, the second is OK from the command line:<BR>
> +<p>If you must try one, the second is OK from the command line:<BR>
>  <pre>
>        <em>lynx LYNXKEYMAP:</em>
>  </pre>
>  But within Lynx, use the '<em>K</em>' keystroke command.
> +Sometimes it may be convenient to use an internal scheme with
                                            ^^^^^^^^^^^^^^^???
> +'<em>g</em>'oto, as in:
> +<pre>
> +      <em>g LYNXMESSAGES:</em>
> +      <em>g LYNXCOMPILEOPTS:</em>
> +      <em>g LYNXCFG:</em>
> +</pre>
> +But again, there usually is a way in which those special pages are
> +meant to be reached that is more convenient.




reply via email to

[Prev in Thread] Current Thread [Next in Thread]