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: Klaus Weide
Subject: Re: lynx-dev dev.15 patch 7 - doc updates for recent changes
Date: Fri, 3 Dec 1999 04:38:23 -0600 (CST)

On Tue, 30 Nov 1999, Philip Webb wrote:

> 991130 Klaus Weide updated some documentation: 
> 
> no doubt due to haste, there are a few errors: maybe TD could fix them?

I'll go throudh dev.16 for these.

> > Index: 2.25/lynx.cfg
> > +# empty in that case, for changing only the line-editin behavior.
>                                                           ^

> > Index: 2.25/lynx_help/Lynx_users_guide.html
> > +    If <A NAME="tna">"Textfields Need Activation"</A> mode is turned on,
> *** where/how? *** ->                                         ^^^^^^^^^^^^

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

Ok

> > +    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).
> *** for future maintenance, don't break the previous 3 lines ***

Actually, maintenance can be easier (smaller diffs) if lines are not
always filled...

> > +    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>
>                                    ^^^^we're in pre

No we aren't (but yes, this will be changed / has already been changed)

> > +    &nbsp;&nbsp;KEYMAP:^_::LKCMD:1<pre></pre>
>                                      ^^^^^
> > +    would move <em>^V</em>'s Line Editor binding as command escape to

> > -<PRE>          <strong>(Textarea) Enter text. </strong>[...] <strong>(^Xe 
> > for editor).</strong></PRE>
> > +<PRE>          <strong
> > +    >(Textarea) Enter text. </strong>[ ..... ]<strong> (^Xe for 
> > editor).</strong></PRE>
> *** what is the purpose of this change? ***

It "looked better".  Feel free to change it back...

> > +<DIV ID="TRST">
> > +<p>Starting with version 2.8.3, Lynx can now render some tables in tabular
>                                             ^^^^omit

Ok

> > +Lynx uses a variety of private URL schemes form communication among its
>                                                  ^

Ok

> > +As you discover what they are, and are tempted to use them externally in
> > +documents, you should <em>resist</em> that temptation:
> > +<UL><LI>There already is too much browser-specific markup around...
> *** drop this line? it's really rather silly ***

Is
    "Lynx users often suffer from browser-specific markup that works only
    in the author's favorite browser.  We shouldn't make the same mistake
    ourselces."

better?  Anyway, if it annoys you enough submit a patch to remove it.
I won't object.

> > +<LI>Even if a scheme stays the same, some aspect of its behavior may
> > +    be modified without notice, or the context in which it is allows
>                                                                       ^

Ok, "allowed"

> > +    may change.
> > +<LI>If it doesn't work as expected when used outside of the intented
>                                                                     ^

Ok

> > Index: 2.25/samples/lynx-keymaps
> > -# The following extension, introduced after lynx2.8.2, allows to map
> > +# The following extensions, introduced after lynx2.8.2, allow to map
> *** English `mapping' *** ->                                     ^^^^^^

Ok

  Klaus


reply via email to

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