unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Juri Linkov <juri@jurta.org>
Cc: schwab@suse.de, emacs-devel@gnu.org, handa@m17n.org
Subject: Re: confusing info in C-u C-x =
Date: Sat, 10 Dec 2005 01:52:23 +0200	[thread overview]
Message-ID: <87y82thq84.fsf@jurta.org> (raw)
In-Reply-To: <E1EkpaB-0005kF-W2@fencepost.gnu.org> (Richard M. Stallman's message of "Fri, 09 Dec 2005 16:15:11 -0500")

>     I propose using (generate-new-buffer-name "*Help*") in both functions
>     to generate the standard unique names like *Help*<2>.
>
> That would result in always creating a new buffer for this command.
> That is not desirable at all.  Thanks, but we won't make this change.

It already always creates a new buffer *Help-2*.  Do you mean that
`generate-new-buffer-name' can create more buffers like *Help*<3> and
*Help*<4>?  In this case, "*Help-2*" should be replaced with the constant
buffer name "*Help*<2>".

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

  reply	other threads:[~2005-12-09 23:52 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-11-20  9:55 confusing info in C-u C-x = Werner LEMBERG
2005-11-20 15:16 ` Andreas Schwab
2005-11-20 22:07   ` [SPAM?]: " Werner LEMBERG
2005-11-21  7:35   ` Juri Linkov
2005-12-08  1:49   ` Kenichi Handa
2005-12-09  9:57     ` Juri Linkov
2005-12-09 15:07       ` Kim F. Storm
2005-12-09 21:15       ` Richard M. Stallman
2005-12-09 23:52         ` Juri Linkov [this message]
2005-12-10 16:18           ` Richard M. Stallman
2005-12-11  0:46             ` Juri Linkov
2005-12-10 22:50           ` Kim F. Storm
2005-12-11  0:55       ` Juri Linkov
2005-12-11 16:49         ` Richard M. Stallman
2005-11-20 23:21 ` Richard M. Stallman
  -- strict thread matches above, loose matches on Subject: below --
2005-11-20 19:35 martin rudalics
2005-11-21  8:56 martin rudalics

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=87y82thq84.fsf@jurta.org \
    --to=juri@jurta.org \
    --cc=emacs-devel@gnu.org \
    --cc=handa@m17n.org \
    --cc=schwab@suse.de \
    /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).