Re: lynx-dev LYNX: reverse-search

[Vlad Harchev]

On Wed, 7 Apr 1999, Klaus Weide wrote:

> On Wed, 7 Apr 1999, Leonid Pauzner wrote:
> 
> > It was discussed recently about adding a revere search functionality,
> > one of the main problems was a lack of hot-key space since most of the
> > keys are already used by lynx.
> > 
> > Currently we have 'n' key for forward next search.
> > It would be logical enough to use capital "N" for backward search
> .....
> > 
> > Any ideas?
> 
> Currently:
>                                                     direction
> 
> It should be obvious how to map WHEREIS, NEXT, WHEREIS_BACKW, and
> NEXT_REVERSE by default so that the keys act as in other programs.
> People who want '?' to be WHEREIS_BACKW map it to WHEREIS_BACKW in
> lynx.cfg.  People who want '?' to be HELP as before map it to HELP in
> lynx.cfg.  The only remaining questions are what the default mapping
> for '?' should be if no mapping is specified in lynx.cfg, and, if the
> answer to that first question is "HELP as before", what other default
> default mapping (if any) should be provided for WHEREIS_BACKW.
> 
> No new ideas here, just a repetition (as was your question).
> 
>    Klaus
> 
  Here are my thoughts:
 1) Since pressing '/' now will jump to the next page (if there is no links
near found text) or will highlight the link closest to the found text
(starting from current "virtual" position) ) it will be good if there will be
a command/key that will _unconditionally_ go to the next page with found 
text, ie it won't highlight closest link if there is one.
2) I suggest the following key combinations:
 '}' - search forward, to next link or next page
 'n' - same
 '{' - reverse search
 'N' - may be reverse search, same as '{'
 ']' - to the next page (unconditionally)
 '[' - to the previous page (unconditionally)
3) Objections against the scheme in 2)
  '[' and ']' are currently bound to inline images toggle and send HEAD
   request. May be that's why that functionality can be implemented later.
4) When key sequences support will be written, IMO it will be good to move all
  seldom-used commands like  (assuming default mapping)
        "
        '
        *
        ;
        `
        @
        [  
        ] -free last to to use them as described in 2)
 to key sequences rather than single keys to free one-key sequences to
commands that are used more often. Also a lot of one-letter commands IMO
should be rebound to key sequences, like
        k
        o
        ^K
        ^V

 As of '?', 'F1' invokes help screen too, and IMO it's more convenient for
people that didn't use UNIX. IMO the '?' is not used by the people who wish to
view help - such sort of people use F1 more often, so rebinding '?' to reverse
search won't be such pain for lynx users.
5) Different variants of key bindings can be distributed with lynx (as
standalone files, not as sections in lynx.cfg), so user can 'include' the one
he/she prefer rather than composing new one. 
        


 Best regards,
  -Vlad