From: Miles Bader <miles@lsi.nec.co.jp>
Subject: problem with uniquify.el and kill-buffer-hook
Date: 13 Dec 2002 11:10:15 +0900 [thread overview]
Message-ID: <buod6o6r7nc.fsf@mcspd15.ucom.lsi.nec.co.jp> (raw)
Recently I've noticed that the `uniquify' package has stopped working
correctly, in particular, the feature controlled by the
`uniquify-after-kill-buffer-p' variable doesn't work; here's the doc:
uniquify-after-kill-buffer-p's value is t
If non-nil, rerationalize buffer names after a buffer has been killed.
This can be dangerous if Emacs Lisp code is keeping track of buffers
by their names (rather than keeping pointers to the buffers
themselves).
I looked at the code a bit, and I think I found the problem:
This feature works by adding an appropriate local hook to
`kill-buffer-hook' in all the affected buffers.
However, this is done _before_ the buffer's mode is set (in the new
buffer that caused uniqify to be triggered); since most mode functions
call `kill-all-local-variables', this trashes the `kill-buffer-hook'.
I've found that I can fix the problem by doing:
(put 'kill-buffer-hook 'permanent-local t)
But doing this by default may cause problems for other code (e.g., if a
particular mode adds a `kill-buffer-hook', you probably want that hook
to be deleted if the mode changes).
Since `kill-all-local-variables' first calls `change-major-mode-hook' I
guess another solution would be to make uniquify add some hair to
`change-major-mode-hook' that tries to preserve its entry in
`kill-buffer-hook' across the kill-all-local-variables', but I'm not
sure how this can be done without another hook that runs _after_
kill-all-local-variables has done its job.
Does anyone have any ideas for a solution? The real problem here seems
to be that kill-buffer-hook can contain both mode-specific and
non-mode-specific entries; I'm not sure if any modes actually use
kill-buffer-hook though...
Also, any ideas why this just stopped working recently? I didn't see
any _obvious_ things in the ChangeLogs, but maybe I just missed it.
Another thing (whew!), is that uniquify.el uses `defadvice' (on
`rename-buffer', and `create-file-buffer') and I wonder if it should be
changed to just have those functions invoke it directly.
Anyway sorry for the long rambling message!
Thanks,
-Miles
--
Ich bin ein Virus. Mach' mit und kopiere mich in Deine .signature.
next reply other threads:[~2002-12-13 2:10 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-12-13 2:10 Miles Bader [this message]
2002-12-13 15:48 ` problem with uniquify.el and kill-buffer-hook Stefan Monnier
2002-12-14 18:31 ` Richard Stallman
2002-12-14 21:36 ` Miles Bader
2002-12-16 16:43 ` Richard Stallman
2002-12-16 17:01 ` Stefan Monnier
2002-12-17 18:44 ` Richard 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=buod6o6r7nc.fsf@mcspd15.ucom.lsi.nec.co.jp \
--to=miles@lsi.nec.co.jp \
--cc=miles@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).