From: Stefan Monnier <monnier@IRO.UMontreal.CA>
To: Juanma Barranquero <lekktu@gmail.com>
Cc: Michael Heerdegen <michael_heerdegen@web.de>, 11017@debbugs.gnu.org
Subject: bug#11017: 24.0.94; emacs-lock--kill-emacs-query-functions should ding
Date: Sun, 18 Mar 2012 22:20:10 -0400 [thread overview]
Message-ID: <jwvk42hjptv.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: <CAAeL0STZYpB-zVwEnZ3_pDsJqS+kqLMrszk=C0hg0kh_+HqTHw@mail.gmail.com> (Juanma Barranquero's message of "Fri, 16 Mar 2012 03:30:45 +0100")
>> Those who don't like dings can customize it with visible-bell and
>> ring-bell-function, so I wouldn't worry too much about it.
> There's a difference between not wanting a ding *ever*, and not
> wanting it in that specific case.
>> But is the message actually visible or does it get immediately
>> overwritten by some other message?
> No, the message is visible. Try
> emacs -Q etc\NEWS -f emacs-lock-mode -f save-buffers-kill-terminal
Oh, I see. Yes, the message is seen OK. And I don't think emacs-lock
should ding in this case. Maybe the code running
kill-emacs-query-functions should ding, on the other hand,
Stefan
next prev parent reply other threads:[~2012-03-19 2:20 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
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 [this message]
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=jwvk42hjptv.fsf-monnier+emacs@gnu.org \
--to=monnier@iro.umontreal.ca \
--cc=11017@debbugs.gnu.org \
--cc=lekktu@gmail.com \
--cc=michael_heerdegen@web.de \
/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).