unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Juanma Barranquero <lekktu@gmail.com>
To: Michael Heerdegen <michael_heerdegen@web.de>
Cc: 11017@debbugs.gnu.org
Subject: bug#11017: 24.0.94; emacs-lock--kill-emacs-query-functions should ding
Date: Thu, 15 Mar 2012 13:54:12 +0100	[thread overview]
Message-ID: <CAAeL0SR7t0m1soRU-4+wWkkEGJGh7iRcmYL9NCNex_hborYfyQ@mail.gmail.com> (raw)
In-Reply-To: <86mx7i79lb.fsf@web.de>

On Thu, Mar 15, 2012 at 05:48, Michael Heerdegen
<michael_heerdegen@web.de> wrote:

> if I lock a buffer and try to exit Emacs, I only get a message:
>
>  "Buffer %S is locked and cannot be killed"

Really? I get "Emacs cannot exit because buffer %S is locked".

> This is IMHO not enough.  If the user tries to exit Emacs while there
> are locked buffers, he obviously has forgotten about these locks. So,
> there should be a (ding) to attract the user's attention.

A ding is obnoxious to many people. It could be added as an option,
but it is not really necessary IMHO. You can use

(defadvice emacs-lock--kill-emacs-query-functions (around do-ding activate)
  ad-do-it
  (unless ad-return-value (ding)))

(defadvice emacs-lock--kill-emacs-hook (around do-ding activate)
  (condition-case err
      ad-do-it
    (error
     (ding)
     (signal (car err) (cdr err)))))

> Without this, the user will possibly continue saying "yes" to the
> expected questions Emacs typically asks, and accidentally modify some
> buffer, which is annoying.

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...

    Juanma





  reply	other threads:[~2012-03-15 12:54 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 [this message]
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
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=CAAeL0SR7t0m1soRU-4+wWkkEGJGh7iRcmYL9NCNex_hborYfyQ@mail.gmail.com \
    --to=lekktu@gmail.com \
    --cc=11017@debbugs.gnu.org \
    --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).