RE: Let `C-h i' open all Info buffers that were quit?

["Drew Adams" <drew.adams@oracle.com>]

    > If you quit Info and reenter, apparently only the first Info buffer is
    > reentered (displayed) - the clones are not. The clone Info
    > buffers are still available, so you can get to them, e.g., via
    > `C-x C-b', but `C-h i' doesn't automatically display them.

    You need to give `C-h i' an argument.  For example, `C-u 3 C-h i' goes
    to the buffer `*info*<3>'.

Ah, I missed that when (mis)reading the doc string. I knew about regular
`C-u', but I missed the part about numeric prefix.

I notice that if there is no *info<8>* and you use `C-u 8 C-h i', then a new
*info<8>* is opened. And if you rename *info<3>* to Regexp Node, then the
`C-u N' technique doesn't help. Still, it's very good.

    > Anyway, my real suggestion here is this: It would be handy if
    > `C-h i' opened (displayed) *all* of the Info buffers.

    Perhaps what you lack is this piece of information: `C-x C-b' shows
    the Info manual's identification next to its *info*<N> buffer name,
    instead of the file name for buffers that have an associated file.
    So, if what you want is a fast way of getting back to a specific Info
    buffer, type `C-x C-b' and select the manual you want from the list.

No, I wasn't missing that information. That's why I mentioned `C-x C-b'.

The manual name doesn't help if you have 7 Info buffers pointing to the same
manual.  Without the node name, I can't use `C-x C-b' in this way most of
the time: I don't necessarily have just one Info buffer per manual.

If the node name were displayed in `C-x C-b', and if it were pointed out in
the doc string of `q' that you can use `C-x C-b' to get back to the Info
buffer, then that might be better than having `C-h i' display all Info
buffers.

And why not let `C-u 0 C-h i' display all Info buffers, if that's what you
really want at some time? Right now, this just opens a new Info buffer named
*info*<0> (which is not the same as *info*). This change could be made
before figuring out how to add the node name to the buffer list. It would be
trivial to implement and I, for one, would use it. I often have a set of
related nodes open at the same time. I close them for a while, and then I
want to get back to them all again, later.

And it would still be good to have an Info binding of, say, `x', to do `C-x
k'.

    I implemented this feature because I couldn't remember which buffer
    has what manual.

It's a good feature; thank you. I'm also interested in knowing which buffer
has which node of which manual.