unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Michael Heerdegen <michael_heerdegen@web.de>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: Juanma Barranquero <lekktu@gmail.com>, 11017@debbugs.gnu.org
Subject: bug#11017: 24.0.94; emacs-lock--kill-emacs-query-functions should ding
Date: Tue, 22 Mar 2022 00:02:59 +0100	[thread overview]
Message-ID: <87wngmx61o.fsf@web.de> (raw)
In-Reply-To: <87ils7nfku.fsf@gnus.org> (Lars Ingebrigtsen's message of "Mon, 21 Mar 2022 22:47:13 +0100")

Lars Ingebrigtsen <larsi@gnus.org> writes:

> Looking at this again -- this is really `emacs-lock-mode'?
> `lock-buffer' does something completely unrelated.

Indeed.  We were never discussing `lock-buffer', this is all about
`emacs-lock-mode'.

> But this is a minor mode, so the prefix arg is taken.

It is also already taken to set the "locking mode"... ;-)

> We could add a `emacs-lock-set-reason' command, but...  would anybody
> use that?

I would not, this would be too distracting.  Using the prefix arg of
the mode function, or a function in the mode hook that would
prompt automatically would be better.

But I still think the feature is useful in general.  When I'm getting
distracted by some other stuff, I want to know why I had locked that
buffer that prevents me from exiting.

> I've never used `emacs-lock-mode', so I don't know what people er would
> use it for.

I'm testing master for a long time now so I don't rely on locking
currently.  Locks don't survive crashes.

People don't use it because it's not really cool.

Michael.





  reply	other threads:[~2022-03-21 23:02 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
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 [this message]
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=87wngmx61o.fsf@web.de \
    --to=michael_heerdegen@web.de \
    --cc=11017@debbugs.gnu.org \
    --cc=larsi@gnus.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).