unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: "Jay Bingham" <b.jc-emacs@netzero.com>
Subject: Bug in clone-indirect-buffer and clone-indirect-buffer-other-window
Date: Tue, 17 Jan 2006 20:52:02 GMT	[thread overview]
Message-ID: <20060117.125238.27535.43697@webmail05.nyc.untd.com> (raw)

I am running Emacs 21.1 on Win2K.

I believe that there are two discrepancies between what is stated on the indirect buffers node in info and the way the two functions clone-indirect-buffer and clone-indirect-buffer-other-window actually work.

In the info page on indirect buffers it states:

-----------------------------------------------------------------------
   A quick and handy way to make an indirect buffer is with the command
`M-x clone-indirect-buffer'.  It creates and selects an indirect buffer
whose base buffer is the current buffer.  With a numeric argument, it
prompts for the name of the indirect buffer; otherwise it defaults to
the name of the current buffer, modifying it by adding a `<N>' prefix
if required.  `C-x 4 c' (`clone-indirect-buffer-other-window') works
like `M-x clone-indirect-buffer', but it selects the cloned buffer in
another window.  These commands come in handy if you want to create new
`*info*' or `*Help*' buffers, for example.
-----------------------------------------------------------------------

The first discrepancy is that when these commands are executed the `<N>' is not prefixed to the buffer name it is suffixed to the buffer name, that is it comes after the name of the buffer not before it.  Either the info page is incorrect or the code is incorrect.

Personally, I would prefer to have some way to differentiate between buffers which contain different files with the same name and buffers that actually point to the same file without having to enter a name for the clone.  I also prefer the numeric indicator to follow the existing buffer name.  Realizing the the same function is likely used to generate the file names I am still willing to suggest that perhaps the `[N]' or `{N}' designators could be used to indicate a cloned buffer as opposed to an automatically generated file name.


The second discrepancy is: although the info page indicates that the only difference between clone-indirect-buffer and clone-indirect-buffer-other-window is that the latter selects the buffer in another window, I do not believe that this is the case.  The clone-indirect-buffer function accepts an argument and prompts for a name while the clone-indirect-buffer-other-window function ignores any numeric argument.
I would like to see the clone-indirect-buffer-other-window function accept an argument as well.

__
J_)
C_)ingham


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

             reply	other threads:[~2006-01-17 20:52 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-01-17 20:52 Jay Bingham [this message]
2006-01-18 16:41 ` Bug in clone-indirect-buffer and clone-indirect-buffer-other-window Kevin Rodgers
2006-01-18 18:56 ` Eli Zaretskii
2006-01-19 17:43 ` Richard M. Stallman
2006-01-22  0:45   ` Juri Linkov
2006-01-22 17:44     ` Richard M. Stallman
2006-01-23  1:57       ` Juri Linkov
2006-01-24 16:46         ` Richard M. Stallman
2006-01-22 17:44     ` Richard M. Stallman

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20060117.125238.27535.43697@webmail05.nyc.untd.com \
    --to=b.jc-emacs@netzero.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).