[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: keep info and info.js compatible with the same features and keys?
From: |
Gavin Smith |
Subject: |
Re: keep info and info.js compatible with the same features and keys? |
Date: |
Mon, 27 Dec 2021 20:56:38 +0000 |
User-agent: |
Mutt/1.9.4 (2018-02-28) |
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.
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.
> 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.
> I think that it would be better in general to add he possibility from
> info.js to info, for instance the possibility to go forward in history
> in info and use the same key in both (possibly changing a not widely
> used key in info).
>
>
> As a side note, I tested info.js and it seems to me that it implements
> most if not all of the usefull features of info.
>
> --
> Pat