From: "Drew Adams" <drew.adams@oracle.com>
To: "'Juri Linkov'" <juri@jurta.org>
Cc: rogers-emacs@rgrjr.dyndns.org, rms@gnu.org, emacs-devel@gnu.org
Subject: RE: C-x C-v considered harmful
Date: Thu, 9 Jul 2009 09:09:56 -0700 [thread overview]
Message-ID: <331B2F5CF78F4411A0F1471D4B70B3AC@us.oracle.com> (raw)
In-Reply-To: <87ws6ipxy7.fsf@mail.jurta.org>
> The variable `kill-buffer-query-functions' is nil by default,
> so maybe it's better to implement this confirmation in Fkill_buffer
> instead of the hook `kill-buffer-query-functions'?
That's pretty much the original question (modulo a few trips we made around
Robinson's barn).
I don't think things should be hard-coded in `kill-buffer'. It's especially not
great to hard-code such stuff in C code.
This is the kind of thing for which it's good to both (a) provide reasonable
default behavior and (b) make it easy for users to change/override that
behavior. IOW, it's fine to do something smart here, but that should not be
hard-coded.
I suggested a separate option for identifying buffers for `kill-buffer'
confirmation query. That's one possibility. That is similar to
`kill-buffer-query-functions', but it is more specifically a list of buffer
names or name patterns. The confirmation behavior itself is already defined; all
we need additionally is to identify the buffers that require it. IOW,
`kill-buffer-query-functions' could be overkill here.
We could also make `kill-buffer-query-functions' a user option (i.e.,
customizable), and give it a default value that provides the behavior you
suggested.
next prev parent reply other threads:[~2009-07-09 16:09 UTC|newest]
Thread overview: 46+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-02 1:18 C-x C-v considered harmful Bob Rogers
2009-07-02 2:39 ` Miles Bader
2009-07-02 3:10 ` Bob Rogers
2009-07-02 6:48 ` Kevin Rodgers
2009-07-02 15:17 ` Drew Adams
2009-07-03 1:09 ` Bob Rogers
2009-07-03 3:19 ` Drew Adams
2009-07-03 20:33 ` Bob Rogers
2009-07-03 22:23 ` Drew Adams
2009-07-04 23:16 ` Bob Rogers
2009-07-05 7:13 ` Drew Adams
2009-07-06 0:39 ` Bob Rogers
2009-07-06 1:40 ` Drew Adams
2009-07-07 10:39 ` Johan Bockgård
2009-07-05 10:18 ` Richard Stallman
2009-07-05 14:56 ` Drew Adams
2009-07-05 0:05 ` Richard Stallman
2009-07-05 7:10 ` Drew Adams
2009-07-06 15:05 ` Richard Stallman
2009-07-06 15:59 ` Drew Adams
2009-07-07 10:05 ` Richard Stallman
2009-07-06 12:04 ` Robert J. Chassell
2009-07-06 23:49 ` Juri Linkov
2009-07-07 1:07 ` Drew Adams
2009-07-08 0:32 ` Juri Linkov
2009-07-08 23:28 ` Juri Linkov
2009-07-09 16:09 ` Drew Adams [this message]
2009-07-09 22:10 ` Juri Linkov
2009-07-09 22:26 ` Drew Adams
2009-07-09 22:46 ` Juri Linkov
2009-07-09 23:21 ` Drew Adams
2009-07-10 4:05 ` Bob Rogers
2009-07-13 20:05 ` Juri Linkov
2009-07-16 21:57 ` Juri Linkov
2009-07-03 2:40 ` M Jared Finder
2009-07-03 2:57 ` Miles Bader
2009-07-03 19:23 ` Richard Stallman
2009-07-03 20:07 ` Andreas Schwab
2009-07-03 20:56 ` Miles Bader
2009-07-03 13:55 ` Markus Triska
2009-07-05 22:15 ` Stefan Monnier
2009-07-05 22:42 ` Bob Rogers
2009-07-11 10:06 ` Stefan Monnier
2009-07-14 2:45 ` Bob Rogers
2009-07-14 18:34 ` Stefan Monnier
2009-07-02 21:03 ` 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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=331B2F5CF78F4411A0F1471D4B70B3AC@us.oracle.com \
--to=drew.adams@oracle.com \
--cc=emacs-devel@gnu.org \
--cc=juri@jurta.org \
--cc=rms@gnu.org \
--cc=rogers-emacs@rgrjr.dyndns.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.