From: Juri Linkov <juri@jurta.org>
To: Glenn Morris <rgm@gnu.org>
Cc: 10770@debbugs.gnu.org
Subject: bug#10770: info-display-manual replaces existing *info* buffer
Date: Fri, 10 Feb 2012 12:14:56 +0200 [thread overview]
Message-ID: <87ty2zvx7r.fsf@mail.jurta.org> (raw)
In-Reply-To: <qrty2z95gf.fsf@fencepost.gnu.org> (Glenn Morris's message of "Thu, 09 Feb 2012 14:23:12 -0500")
>> PS maybe there should be an `info-rename' command that renames an info
>> buffer to include the name of the displayed manual.
>
> Or maybe `rename-uniquely' should get some (optional) smart behaviour to
> use more meaningful names. Names of manuals in info, names of recipient
> of current mail message, etc.
Then functions like `occur-rename-buffer' could be replaced with a simple
buffer-local naming function (named e.g. `rename-buffer-name-function')
with the behaviour similar to `compilation-buffer-name-function'.
This will help to replace such customizations as:
(add-hook 'occur-hook (lambda () (occur-rename-buffer t)))
(setq compilation-buffer-name-function
(lambda (mode-name)
(generate-new-buffer-name
(concat "*" (downcase mode-name) "*"))))
with just:
(add-hook 'occur-hook 'rename-uniquely)
(add-hook 'compilation-mode-hook 'rename-uniquely)
next prev parent reply other threads:[~2012-02-10 10:14 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-09 6:33 bug#10770: info-display-manual replaces existing *info* buffer Glenn Morris
2012-02-09 9:28 ` Juri Linkov
2012-02-09 18:43 ` Eli Zaretskii
2012-02-09 18:36 ` Eli Zaretskii
2012-02-09 18:46 ` Glenn Morris
2012-02-09 18:53 ` Glenn Morris
2012-02-09 19:05 ` Eli Zaretskii
2012-02-09 19:16 ` Drew Adams
2012-02-09 19:19 ` Glenn Morris
2012-02-09 22:04 ` Eli Zaretskii
2012-02-09 19:23 ` Glenn Morris
2012-02-10 10:14 ` Juri Linkov [this message]
2012-02-10 15:13 ` Stefan Monnier
2012-02-09 19:04 ` Eli Zaretskii
2012-12-02 6:24 ` Chong Yidong
2012-02-10 15:15 ` Stefan Monnier
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=87ty2zvx7r.fsf@mail.jurta.org \
--to=juri@jurta.org \
--cc=10770@debbugs.gnu.org \
--cc=rgm@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 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).