Bug in Info pages when using indirect buffer

Bug in Info pages when using indirect buffer

[Jay Bingham]

On the Indirect Buffers info node it says:

----------------------------------------------------------------------
These commands come in handy if you want to create new
`*info*' or `*Help*' buffers, for example.
----------------------------------------------------------------------

When I create an indirect buffer of an info node I can no longer navigate thought the info nodes.

I am running Emacs 21.1 on Win2K.


__
J_)
C_)ingham


______________________________________________________________________
Call Anyone, Anytime, Anywhere in the World - FREE!
Free Internet calling from NetZero Voice
Visit http://www.netzerovoice.com today!

Re: Bug in Info pages when using indirect buffer

[Eli Zaretskii]

> From: "Jay Bingham" <b.jc-emacs@netzero.com>
> Date: Tue, 17 Jan 2006 21:28:07 GMT
> 
> On the Indirect Buffers info node it says:
> 
> ----------------------------------------------------------------------
> These commands come in handy if you want to create new
> `*info*' or `*Help*' buffers, for example.
> ----------------------------------------------------------------------
> 
> When I create an indirect buffer of an info node I can no longer navigate thought the info nodes.
> 
> I am running Emacs 21.1 on Win2K.

Thank you for your report.  In the current development sources, the
manual no longer says that.  So this problem is already fixed.

Re: Bug in Info pages when using indirect buffer

[Richard M. Stallman]

    These commands come in handy if you want to create new
    `*info*' or `*Help*' buffers, for example.

It looks like we've deleted that already in the development sources on
savannah.gnu.org.  Thanks anyway for reporting it.

    I am running Emacs 21.1 on Win2K.

In hacker terminology, calling something a "win" is a form of praise.
If you wish to praise Microsoft Windows, you're free to do so; but if you
don't, then you might want to think twice about using the term "win2k".

Re: Bug in Info pages when using indirect buffer

[Juri Linkov]

>     These commands come in handy if you want to create new
>     `*info*' or `*Help*' buffers, for example.
>
> It looks like we've deleted that already in the development sources on
> savannah.gnu.org.

There are other problems related to using clone-buffer in Info.

The docstring of `Info-mode' says:

M-n	Select a new cloned Info buffer in another window.

But actually `M-n' selects a new cloned Info buffer in the same window.
This behavior was changed as a side effect of moving the string "*info*"
from `same-window-buffer-names' to `same-window-regexps' (and adding
a regexp for the suffix <N>).  I guess there should be two separate
commands to clone an Info buffer in the same window (`M-n') and in another
window (I think a suitable key binding would be `C-x 4 M-n').

-- 
Juri Linkov
http://www.jurta.org/emacs/

Re: Bug in Info pages when using indirect buffer

[Richard M. Stallman]

    But actually `M-n' selects a new cloned Info buffer in the same window.
    This behavior was changed as a side effect of moving the string "*info*"
    from `same-window-buffer-names' to `same-window-regexps' (and adding
    a regexp for the suffix <N>).

Can you explain how that change led to this result?
It sounds like this is due to some other kind of bug.

Re: Bug in Info pages when using indirect buffer

[Juri Linkov]

>     But actually `M-n' selects a new cloned Info buffer in the same window.
>     This behavior was changed as a side effect of moving the string "*info*"
>     from `same-window-buffer-names' to `same-window-regexps' (and adding
>     a regexp for the suffix <N>).
>
> Can you explain how that change led to this result?
> It sounds like this is due to some other kind of bug.

`C-h i' displays an Info buffer in the same window, so `C-u N C-h i'
should display `*info*<N>' buffer in the same window as well.  This was
achieved by removing `*info*' from `same-window-buffer-names' and adding
`*info*<[0-9]+>' to `same-window-regexps'.

A side effect of this is the changed behavior of `M-n' which now
displays a new cloned buffer *info*<N> in the same window.

Actually there is no problem with this, but I thought that some users may
want to display a cloned buffer in another window.  This can be done by
creating a new keybinding `C-x 4 M-n' to `clone-indirect-buffer-other-window'.
Of course, every user who wants this can put this binding to .emacs,
or to remove `*info*<[0-9]+>' from `same-window-regexps'.

-- 
Juri Linkov
http://www.jurta.org/emacs/

Re: Bug in Info pages when using indirect buffer

[Juri Linkov]

With the latest change in `clone-buffer' it is not possible to show the
new cloned buffer in the same window, even if its name matches the
`same-window-regexps' (the only way to specify this behavior I know).

Perhaps there should exists a new separate command
`clone-buffer-other-window' that would force displaying the new
cloned buffer in another window (by analogy with two commands
`clone-indirect-buffer' and `clone-indirect-buffer-other-window').

-- 
Juri Linkov
http://www.jurta.org/emacs/