[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: |
Klaus Weide |
Subject: |
Re: lynx-dev dev.15 patch 7 - doc updates for recent changes |
Date: |
Fri, 3 Dec 1999 04:28:23 -0600 (CST) |
On Tue, 30 Nov 1999, Leonid Pauzner wrote:
> 30-Nov-99 06:34 Klaus Weide wrote:
> > Some doc changes only.
> few typos:
>
> > Index: 2.25/lynx_help/Lynx_users_guide.html
> > + 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" ?
Yes indeed.
> > + 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>
> ^^^^^^^^^^^?
> > + KEYMAP:^V:DO_NOTHING<br>
> > + 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>
> ^^^^^^^^^^^?
> > + KEYMAP:^V::NOP:1<br>
> > + KEYMAP:^_::LKCMD:1<pre></pre>
Those were intentional, to get one empty line. In other places, <p> at
the end of a line is used, which didn't look clean to me, <br> isn't it,
either, so I used <pre></pre>... well I agree that isn't very good
either. Anyway it seems Tom hasn't kept it this way, I will check again.
> > Index: 2.25/lynx_help/lynx_url_support.html
> > -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)
> > But within Lynx, use the '<em>K</em>' keystroke command.
> > +Sometimes it may be convenient to use an internal scheme with
> ^^^^^^^^^^^^^^^???
Yes, that should probably be "private", too.
Thanks for checking,
Klaus