From: Michael Heerdegen <michael_heerdegen@web.de>
To: Juanma Barranquero <lekktu@gmail.com>
Cc: 11017@debbugs.gnu.org
Subject: bug#11017: 24.0.94; emacs-lock--kill-emacs-query-functions should ding
Date: Fri, 16 Mar 2012 02:11:22 +0100 [thread overview]
Message-ID: <86obrxuz7p.fsf@web.de> (raw)
In-Reply-To: <CAAeL0SR7t0m1soRU-4+wWkkEGJGh7iRcmYL9NCNex_hborYfyQ@mail.gmail.com> (Juanma Barranquero's message of "Thu, 15 Mar 2012 13:54:12 +0100")
Juanma Barranquero <lekktu@gmail.com> writes:
> > "Buffer %S is locked and cannot be killed"
>
> Really? I get "Emacs cannot exit because buffer %S is locked".
Sorry - I copied the wrong string.
>> [...] So, there should be a (ding) to attract the user's attention.
>
> A ding is obnoxious to many people.
That's why I think it's appropriate here ;-)
> It could be added as an option, but it is not really necessary IMHO.
I would appreciate such an option (what do others think?).
> Getting into the habit of typing without reading what Emac is saying
> is dangerous because you can end typing Y to a question you would've
> rather said N...
Right, no doubt. Nevertheless, it may happen if you lack in
concentration at the end of your work... I don't want to argue, we
obviously disagree. I wrote this report because I thought others could
have the same wish. Dunno if that's the case.
BTW: I wrote this some time ago:
http://www.emacswiki.org/emacs/emacs-lock+.el
(Didn't adopt it for Emacs 24 yet.)
I wrote it mainly because of these two features:
- when exiting Emacs, and there is a locked buffer, pop it up (because
it's very likely that the user will want to see it next)
- Optionally, let the user enter a short note of why he has locked the
buffer. Print this when the user tries to kill the buffer/ Emacs.
Helpful as reminder for people who run Emacs for several days.
Maybe you find these useful, dunno - I don't mind if not.
Regards,
Michael.
next prev parent reply other threads:[~2012-03-16 1:11 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-15 4:48 bug#11017: 24.0.94; emacs-lock--kill-emacs-query-functions should ding Michael Heerdegen
2012-03-15 12:54 ` Juanma Barranquero
2012-03-16 1:11 ` Michael Heerdegen [this message]
2012-03-16 2:26 ` Juanma Barranquero
2012-03-16 2:26 ` Stefan Monnier
2012-03-16 2:30 ` Juanma Barranquero
2012-03-19 2:20 ` Stefan Monnier
2012-03-19 9:04 ` Juanma Barranquero
2012-04-10 14:33 ` Juanma Barranquero
2012-04-14 0:36 ` Michael Heerdegen
2012-04-14 1:48 ` Juanma Barranquero
2020-09-19 15:00 ` Lars Ingebrigtsen
2020-09-19 22:36 ` Michael Heerdegen
2020-09-20 9:38 ` Lars Ingebrigtsen
2022-03-21 21:47 ` Lars Ingebrigtsen
2022-03-21 23:02 ` Michael Heerdegen
2022-03-22 14:07 ` Lars Ingebrigtsen
2022-03-22 23:37 ` Michael Heerdegen
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=86obrxuz7p.fsf@web.de \
--to=michael_heerdegen@web.de \
--cc=11017@debbugs.gnu.org \
--cc=lekktu@gmail.com \
/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).