Re: simpler help texts, default key for delete-window

[Karl Berry]

    It would be nice, though, to have instead search-next and 
    search-previous bound to a single key by default.  In my .infokey 

I don't disagree, but I don't want to change existing bindings away from
what we've got at this point.  All the implications of that will require
considerably more work, and I just want to make this release to get the
new install-info out there (basically).  The Info key bindings haven't
changed since forever, so I don't think it's an emergency to optimize
them immediately.  

    Instead of the longest available key binding, it should mention the 
    shortest: Down and Up.  

Yes, it certainly should.  It's a bug and I already put an entry in TODO
about it.  I don't see why these cmds are coming out with the esc
sequences while others have the proper names, and I've already spent too
long trying to debug it.  Sorry.  If someone else (Ben? Stephane?) can
track this down soon (while we're doing pretests), that would be great.

    End         Go to the end of this node.
    Home        Go to the beginning of this node.

It seems strange to me to list End before Home, even though I realize it
is more "logical" in terms of the pairings.  Hmm.

    I don't see the point of this: it makes the list of commands seem 
    much longer than it actually is.  For the user the shortest key 

That second part of the help text is just dumping every function and
every binding as far as I can tell.  I am not enamored of the results
either, but it is not exactly obvious to me how to change it in any
meaningful way, so I need to postpone the whole idea.  Another thing
that would be good to file a bug report on.  (See next.)

    bs>     Also, when scrolling down through the help text, it should
    bs>     stop at the bottom, fully stop -- and not beep, say "No more
    bs>     nodes within this document", and go back to the top.
    
    kb> I agree, but this has to be postponed (unless someone else cares
    kb> to send me a patch within a couple days).  Can you put it in the
    kb> bug list?

    bs> You mean file a bug on Savannah?

Yes, that's what I meant, sorry for not saying explicitly.  Especially
in the case of Info, I've tried to submit many of its infelicities into
savannah, in the hope that more potential contributors will see them.

I think I got your other changes.

Thanks,
karl