Re: keep info and info.js compatible with the same features and keys?

[Patrice Dumas]

On Mon, Dec 27, 2021 at 08:56:38PM +0000, Gavin Smith wrote:
> On Mon, Dec 27, 2021 at 01:05:22PM +0100, Patrice Dumas wrote:
> > Hello,
> > 
> > I think that it would be nice if info.js could be as compatible as
> > possible with info (and with a local html texinfo doc browsing reader).
> > 
> > It seems to me to be an issue 'r' which selects xrefs in info and
> > goes forward in history in info.js.
> 
> It would be quite a lot of work to implement this in the stand-alone
> Info program as the later history isn't saved when going back in the
> history.  Possible to do of course, but I for one have never missed
> this feature in info.

Ok.

> I checked and 'r' goes forwards in the Emacs Info mode too.
> 
> I agree that 'r' to select a cross-reference would likely be a rarely
> used command in Info.

Then I think that it would be better if it was changed such that 'r' is
pre-reserved for going forward in history if it is what most info viewer
use.  The point is that it would be better if the selection of keyboard
shortcuts were the same in all the info viewers irrespective of their
actually implemented features.

> > Also '?' does not have the same
> > meaning, it should be 'h' in info.js to be the same as in info.
> 
> It's 'H' not 'h' in info that loads the help.  'h' loads the tutorial.
> I don't see why 'H' couldn't load the help in info.js too.

Indeed.

-- 
Pat