`clone-indirect-buffer' buffer naming.

`clone-indirect-buffer' buffer naming.

[David Hansen]

Hello,

the doc of `clone-indirect-buffer' states:

Give the indirect buffer name NEWNAME.  Interactively, read NEWNAME
from the minibuffer when invoked with a prefix arg.  If NEWNAME is nil
or if not called with a prefix arg, NEWNAME defaults to the current
buffer's name.  The name is modified by adding a `<N>' suffix to it
or by incrementing the N in an existing suffix.

I don't see this modification.  E.g.

$ emacs -Q tmp/foo.txt

M-x clone-indirect-buffer

M-: (require 'cl)

M-: (loop for b in (buffer-list)
      when (string-match "foo" (buffer-name b))
      collect b)

--> (#<buffer foo.txt> #<buffer foo.txt>)

Bug?  Misleading documentation?

David

Re: `clone-indirect-buffer' buffer naming.

[Lennart Borgman (gmail)]

David Hansen wrote:
> Hello,
> 
> the doc of `clone-indirect-buffer' states:
> 
> Give the indirect buffer name NEWNAME.  Interactively, read NEWNAME
> from the minibuffer when invoked with a prefix arg.  If NEWNAME is nil
> or if not called with a prefix arg, NEWNAME defaults to the current
> buffer's name.  The name is modified by adding a `<N>' suffix to it
> or by incrementing the N in an existing suffix.
> 
> I don't see this modification.  E.g.
> 
> $ emacs -Q tmp/foo.txt
> 
> M-x clone-indirect-buffer
> 
> M-: (require 'cl)
> 
> M-: (loop for b in (buffer-list)
>       when (string-match "foo" (buffer-name b))
>       collect b)
> 
> --> (#<buffer foo.txt> #<buffer foo.txt>)
> 
> Bug?  Misleading documentation?
> 
> David

I noticed this too, since it means trouble for ido-switch-buffer. So I 
would suggest it is a bug.

Re: `clone-indirect-buffer' buffer naming.

[Stefan Monnier]

> M-: (loop for b in (buffer-list)
>       when (string-match "foo" (buffer-name b))
>       collect b)

--> (#<buffer foo.txt> #<buffer foo.txt>)

> Bug?

Bug.  Should be fixed now.  Thank you,


        Stefan