Re: LYNX-DEV erroneous statements in CHANGES.new and follow_help.html

[Klaus Weide]

On Sat, 10 May 1997, Laura Eaves wrote:

> > Index: lynx2-7-1/CHANGES.new
> > --- 10,68 ----
> > ...
> > ! * Tweaked yesterday's LYList.c mods so that an OL with the CONTINUE
> > !   attribute is used when a "Hidden links:" list is appended to a
> > !   "Visible links:" list and NUMBERS_AS_ARROWS mode is on.  This allows
> > !   you to see the number to enter at "Follow link (or page) number:"
> > !   prompts, as when LINKS_ARE_NUMBERED mode is on. - FM
> > ...
> 
> This is false, as when NUMBERS_AS_ARROWS is set, numbers "act as arrows"
> (like the name says) and don't invoke the prompt.  (At least that's what
> happens with my keyboard...)

I took that entry from FOTEMODS without changing it.  Maybe I should have
changed it.  The devel code currently does not have a way to get the
"Follow link (or..." prompt in NUMBERS_AS_ARROWS mode, while Fote's code
does (with the '5' key; which you would know if you had read the message
announcing it).

I was thinking of doing this with the '0' key, which is currently unused
in NUMBERS_AS_ARROWS mode, instead of '5'.  The 0 could just be used as
the first digit on the prompt line, instead of having to discard it and
keeping track of an extra state as for the '5', because leading 0's are
insignificant anyway...  Does that sound more natual?  I am not sure.

Anyway, CHANGES.* is a log of changes, don't expect that
(especially older) entries always describe current behavior.

> > Index: lynx2-7-1/lynx_help/keystroke_commands/follow_help.html
> > ...
[ This part written by Fote - except for a change of the prompt text by
me for the devel code - kw]
> > + numbers in square brackets.  Entering a keyboard or keypad number should
> > + invoke the <em>Follow link (or goto link or page) number:</em> statusline 
> > prompt for
> > + a potentially multiple digit number corresponding to an indicated link
> > + number.  If RETURN is pressed to terminate the number entry (e.g.,
> > + <em>123</em>), Lynx will retrieve the document for that link as if you
> > + had paged or used other navigation commands to make it the current link
> > + and then ACTIVATE-ed it.
> 
> This is also false.  When the user types 123<RETURN> this acts like "g)oto 
> URL".
> It does not move the current link to link 123 before activating it (unless you
> changed the default behavior of this command).

Read that sentence again.  It says "Lynx will _retrieve the document_ ...
as if...".  It doesn't say "Lynx will act in every way ... as if..."

Anyway, how about providing a better description if you feel that is
needed, instead of just claiming that things are "false".

   Klaus

;
; To UNSUBSCRIBE:  Send a mail message to address@hidden
;                  with "unsubscribe lynx-dev" (without the
;                  quotation marks) on a line by itself.
;