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: Philip Webb
Subject: Re: lynx-dev dev.15 patch 7 - doc updates for recent changes
Date: Tue, 30 Nov 1999 14:02:08 -0500 (EST)

991130 Klaus Weide updated some documentation: 

no doubt due to haste, there are a few errors: maybe TD could fix them?
 
> Index: 2.25/lynx.cfg
> --- 2.25/lynx.cfg Sun, 28 Nov 1999 13:18:29 -0600
> +++ 2.25(w)/lynx.cfg Mon, 29 Nov 1999 21:09:26 -0600
> @@ -1968,6 +1950,96 @@
-- snip --
> +# If the OTHER BINDING field does not specify DIRED, then it is taken as a
> +# line-editor action.  It is possible to keep the MAIN LYNX FUNCTION field
> +# empty in that case, for changing only the line-editin behavior.
                                                          ^
> +# If alternative line edit styles are compiled in, and modifying a key's
> +# line-editor binding on a per style basis is possible, then SELECT can be
> +# used to specify which styles are affected.  By default, or if SELECT is
-- snip --
> 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,
*** where/how? *** ->                                         ^^^^^^^^^^^^
> +    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
*** as LP points out, this sb `Right' presumably *** ->                  ^^^^
> +    Arrow</em>.  This mode can be used to avoid "getting stuck" in input
> +    fields, especially by users that rearely fill out forms.
*** English `who' ***              ^^^^  ^
> +
> +    <DIV ID="CtrlVNote">
> +    <p><em>NOTE:</em> If you have a text input field selected you will not
> +    have access to most of the Lynx keystroke commands, because they are
> +    interpreted by the <a href="keystrokes/edit_help.html"
> +    >Line Editor</a> as either text entries or editing commands.  Select a
> +    button or box when you want to use Lynx keystrokes; or prefix your
> +    keystroke with <em>^V</em> to temporarily escape from line editing.
> +    <p>
> +    Some flavors of UNIX, shells &amp; terminal settings require
> +    that you enter <em>^V^Ve</em> in order to start the external editor,
> +    as they also use <em>^V</em> as default command-line quote key
> +    (called `lnext' in stty man pages and `stty -a' output);
> +    to avoid this, you can put `stty lnext undef' in your .cshrc
> +    file (or .profile or .bashrc, depending on what shell you use),
> +    or invoke Lynx with a wrapper script, e.g.<p>
> +
> +    <code>
> +    &nbsp;&nbsp;#!/bin/sh<br>
> +    &nbsp;&nbsp;stty lnext undef<br>
> +    &nbsp;&nbsp;$HOME/bin/lynx "$@"<br>
> +    &nbsp;&nbsp;stty lnext ^V<br>
> +    &nbsp;&nbsp;exit</code><p>
> +
> +    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 ***
> +    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>
                                   ^^^^we're in pre
> +    &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>
*** for future maintenance, don't break the previous 3 lines ***
> +
>  <dt>TEXTAREA Fields
> -<dd>TEXTAREA fields are handled as if they were a series of text entry
> -    (INPUT) fields for which successive lines imply a newline at the end of
> +<dd>TEXTAREA fields are for most purposes handled as if they were a series of
> +    text entry (INPUT) fields
> +    for which successive lines imply a newline at the end of
>      the preceding line.  You enter text on each line to construct the overall
>      message.  Any blank lines at the bottom of the TEXTAREA field will be
>      eliminated from the submission.  The <em>up-arrow</em>, and
>      <em>down-arrow</em> or <em>Return</em> keys move you to the preceding,
> -    or next line of the overall message, as for INPUT fields, and the
> +    or next line of the overall message, as for INPUT fields.  The
>      <em>TAB</em> key will move you down beyond the bottom of the TEXTAREA
> -    field.
> +    field, and <em>Back Tab</em> (if available, e.g. as Shift-Tab, and
> +    correctly mapped in the terminal description) will move backward to
> +    a link or field before the TEXTAREA.
>  
>  <dt>Editing TEXTAREA Fields and Special TEXTAREA Functions
>  <dd>TEXTAREA fields can be edited using an external editor.
>      The statusline should tell you when this is possible and what
>      key to use, it might for example say
>  
> -<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? ***
>  
>      An external editor has to be defined, for example in the <a
>      href="#InteractiveOptions">Options Menu</a>, before you can start
> @@ -1408,46 +1462,47 @@
-- snip --
> +    If you have some single keys (or control keys) to spare that you
> +    do not need for their normal purposes, you can dedicated those keys
                                                              ^
> +    to invoke the special functions (without requiring a prefix key).
> +    For example, to use
> +    the <em>^E</em> key for the DWIMEDIT action, and
> +    the <em>Insert</em> key for the INSERTFILE action,
> +    use<br>
> +    &nbsp;&nbsp;KEYMAP:^E:DWIMEDIT:PASS<br>
> +    &nbsp;&nbsp;KEYMAP:0x10C:INSERTFILE:PASS<br>
> +    (see lynx.cfg for other keystroke codes to use).
> +
> +    <p>Note that the default bindings that use <em>^X</em> as a prefix key
> +    <em>may</em> also work by substituting the <kbd>Escape</kbd> key
> +    for ^X.  If your keyboard has a modifier (Meta) key that gets
> +    transmitted as an ESC prefix, for example <kbd>Alt</kbd>, you can
> +    then even us <em>Alt-e</em> instead of <em>^Xe</em>, <em>Alt-g</em>
                   ^
> +    instead of <em>^Xg</em>, and so on.  But this does not work reliably
> +    everywhere (it depends on the way Lynx is compiled, including which
> +    libraries are used, and behavior of the connection and terminal type).
>  </dl>
>  
>  In general, you can move around the form using the standard Lynx navigation
> @@ -1665,6 +1712,50 @@
>  for PRE content, construct the <em>table</em> using <a
>  href="#Tabs">HTML Tabs</a>.  An example <em>table</em> using <em>TAB</em>
>  elements is included in the test subdirectory of the Lynx distribution.
> +
> +<DIV ID="TRST">
> +<p>Starting with version 2.8.3, Lynx can now render some tables in tabular
                                            ^^^^omit
> +form.  This tabular representation for <em>simple</em> tables
> +(<dfn>TRST</dfn>) does not attempt to implement full support for any table
> +model.  Limitations are:
-- snip --
> 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
                                                 ^
> +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>
> +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 ***
> +<LI>The schemes, or their meanings, may change between Lynx versions.
> +<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
                                                                      ^
> +    may change.
> +<LI>If it doesn't work as expected when used outside of the intented
                                                                    ^
> +    purpose, don't expect anyone to "fix" it.
> +</UL>
-- snip --  
> Index: 2.25/samples/lynx-keymaps
> --- 2.25/samples/lynx-keymaps Sat, 12 Jun 1999 17:10:16 -0500
> +++ 2.25(w)/samples/lynx-keymaps Mon, 29 Nov 1999 02:40:23 -0600
> @@ -131,15 +131,18 @@
>  #setkey "\033e"          Meta-'e'
>  #setkey "\033\033[28~"   Meta-F1
>  #
> -# The following extension, introduced after lynx2.8.2, allows to map
> +# The following extensions, introduced after lynx2.8.2, allow to map
*** English `mapping' *** ->                                     ^^^^^^
>  # escape sequences directly to key commands (lynxactioncodes).
>  #
>  #       setkey ESC-SEQUENCE  LAC:LYNX_ACTION
> +#       setkey ESC-SEQUENCE  LAC:LYNX_ACTION:LYNX_EDITACTION
-- snip --

-- 
========================,,============================================
SUPPORT     ___________//___,  Philip Webb : address@hidden
ELECTRIC   /] [] [] [] [] []|  Centre for Urban & Community Studies
TRANSIT    `-O----------O---'  University of Toronto

reply via email to

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