Re: lynx-dev Redundant link movement cmds? (was: Some thought on additional TEXTAREA functions)

[Leonid Pauzner]

30-Jan-99 11:01 Kim DeVaughn wrote:
> Which led me to look at the existing code for the LYK_NEXT_LINK and
> LYK_PREV_LINK cases.

> Whereon, I also discovered cases for LYK_DOWN_LINK and LYK_UP_LINK,
> which I don't think I realized were distinctly different commands before.

> Looking at the keybinding descriptions, we have:

>  <           UP_LINK       move up the page to a previous link
>  >           DOWN_LINK     move down the page to another link

> and

>  Up Arrow    PREV_LINK     make the previous link current
>  Down Arrow  NEXT_LINK     make the next link current

Wow!  I have tried these keys and found the difference:
they acts differently when you have several anchors at the same line,
try "Supported URLs" page from lynx main help page.

">" moves between "first anchor on a line"
"<" moves between "last anchor on a line"
while "down arrow" and "up arrow" moves between nearest anchors hornestly.

This is not contradict with keybinding descriptions but you wouldn't guess
the difference until you saw it, yes.

> And a quick look at the code for the corresponding pairs, looks quite
> similar (cosmetic differences such as error msgs aside).

> So ... what am I missing ...?  Why the need for the UP/DOWN commands,
> when we have the PREV/NEXT ones?  A quick comparison between the "<"
> and "UpArrow" keystrokes, and between the ">" and "DownArrow" keystrokes
> didn't seem to do anything different.  So again ... what am I missing?

> BTW, glancing through the UserGuide didn't seem to mention "<" and ">",
> but then I really didn't look very hard.

> Curiously ...

> /kim

> ===============================================================
> "I think I speak for everyone here when I say, 'Huh?'"  --Buffy