From: Glenn Morris <rgm@gnu.org>
To: 3806-done@debbugs.gnu.org
Subject: bug#3806: 23.1.50; rename-uniquely doc
Date: Thu, 09 Feb 2012 15:31:27 -0500 [thread overview]
Message-ID: <86liobeokg.fsf@fencepost.gnu.org> (raw)
In-Reply-To: <87bpnsevls.fsf@escher.local.home> (Stephen Berman's message of "Fri, 10 Jul 2009 11:27:27 +0200")
Version: 24.0.94
Stephen Berman wrote:
> The last, parenthetical, sentence in particular is important
> information, and I think it should also be in the doc string,
OK, I added something about this.
> And for this reason, I also think it should be more specific, not just
> listing "some of these features" that require switching out of the
> uniquely renamed buffer, but all such known "features".
I don't think it is possible or desirable to give a comprehensive list
(it may just be compilation-based modes).
> However, the manual appears to be out of date, or just inaccurate:
> invoking Info from within a uniquely renamed Info buffer does not
> overwrite it but opens new Info buffer, as I just confirmed with -Q.
I happened to change this recently.
> If `M-x info' has indeed been "fixed" wrt rename-uniquely, then can't
> `M-x {r,l}grep' and `M-x compile' likewise be fixed? (I haven't tested
> compile for this, but the grep commands do indeed, annoyingly, require
> switching buffers.) Since the requirement is documented, it is not
> strictly a bug, but the behavior is suboptimal and if, as with Info, it
> can be changed, then I think it should be. I can submit a separate bug
> for that.
It's a deliberate feature of compilation-buffer-name. A new wishlist bug
would be appropriate if you would like to see that changed.
prev parent reply other threads:[~2012-02-09 20:31 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-10 9:27 bug#3806: 23.1.50; rename-uniquely doc Stephen Berman
2012-02-09 20:31 ` Glenn Morris [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=86liobeokg.fsf@fencepost.gnu.org \
--to=rgm@gnu.org \
--cc=3806-done@debbugs.gnu.org \
/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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.