Re: Documentation for "Clone Buffers" (corrected version)

[Alan Mackenzie]

On 9 Mar 2004, David Kastrup wrote:

Alan Mackenzie <address@hidden> writes:

>> [Re: My proposed patch to the Emacs manual, documenting the command
>> `clone-buffer'.]

>> On Sat, 28 Feb 2004, Richard Stallman wrote:

>> [Alan Mackenzie:]
>> >    I disagree.  I find clone-buffer exceptionally useful, as it is
>> >    the only way I know of having two *info* buffers displaying
>> >    different info files at the same time.

>> >The recommended method is to create one, do M-x rename-uniquely, then
>> >switch to some other buffer and do M-x info again.  This works for
>> >all sorts of special facilities.

>> Ah, right!  :-)  That's anything but user-friendly, though.  It's also
>> difficult to work out from the documentation.  I couldn't find any
>> hint of this procedure in the Info info pages, which is the first
>> place I looked, a year or three ago.

>Is the prefix argument of the following more user-friendly?

>m runs the command Info-menu
>   which is an interactive compiled Lisp function in `info'.
>It is bound to m.
>(Info-menu MENU-ITEM &optional FORK)

It is friendlier.  Sadly, it's not documented in the Info manual (at
least, it wasn't last time I looked).

[ .... ]

>Actually, it might be even more useful if the "d" command for going
>to a new directory would also have this FORK functionality, since
>_that_ is the point where one usually wants to start a new info
>path.  And while we are at it, "t" could also make use of a FORK
>prefix.

Yes, why don't we just FORK the whole lot of them?  n, p, u, m, d, f, l,
i, t, <CR>, as well as retaining M-n?

>David Kastrup

-- 
Alan Mackenzie (Munich, Germany)