From: Lars Ingebrigtsen <larsi@gnus.org>
To: Michael Heerdegen <michael_heerdegen@web.de>
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: Mon, 21 Mar 2022 22:47:13 +0100 [thread overview]
Message-ID: <87ils7nfku.fsf@gnus.org> (raw)
In-Reply-To: <87imc8ss7u.fsf@gnus.org> (Lars Ingebrigtsen's message of "Sun, 20 Sep 2020 11:38:45 +0200")
Lars Ingebrigtsen <larsi@gnus.org> writes:
>>> > - 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.
>>>
>>> It doesn't look like this was implemented? But it does sound kinda
>>> useful... would `M-x lock-buffer' just prompt for a reason?
>>
>> I would say it would do that when called interactively with a prefix
>> arg.
>
> Sure; makes sense.
Looking at this again -- this is really `emacs-lock-mode'?
`lock-buffer' does something completely unrelated.
But this is a minor mode, so the prefix arg is taken. We could add a
`emacs-lock-set-reason' command, but... would anybody use that?
I've never used `emacs-lock-mode', so I don't know what people er would
use it for.
Any opinions?
--
(domestic pets only, the antidote for overdose, milk.)
bloggy blog: http://lars.ingebrigtsen.no
next prev parent reply other threads:[~2022-03-21 21:47 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 [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87ils7nfku.fsf@gnus.org \
--to=larsi@gnus.org \
--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 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.