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: Fri, 16 Mar 2012 03:26:38 +0100 [thread overview]
Message-ID: <CAAeL0ST0F05X2E0BDmq=+S6meNyZRSWRT-0gGnF5WdHOW2hkwA@mail.gmail.com> (raw)
In-Reply-To: <86obrxuz7p.fsf@web.de>
severity 11017 wishlist
found 11017 24.2
quit
On Fri, Mar 16, 2012 at 02:11, Michael Heerdegen
<michael_heerdegen@web.de> wrote:
> That's why I think it's appropriate here ;-)
Making an obnoxious feature the default wouldn't get much goodwill, I think.
> I would appreciate such an option (what do others think?).
IMO, instead of adding an option to call `ding', it would make more
sense to add a hook and let the user decide what do to with it. That's
post 24.1 anyway.
> - 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)
Well, I suppose it makes sense as an optional feature, because you
will want to unlock it. In my case, I have bs-show customized to
display the (un)?locked state of buffers and can toggle it from there,
so no need to pop the buffer.
> - 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.
Again, it seems useful, post-24.1.
I'm going to turn this into a wishlist, and we can revisit it after the release.
Juanma
next prev parent reply other threads:[~2012-03-16 2:26 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 [this message]
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='CAAeL0ST0F05X2E0BDmq=+S6meNyZRSWRT-0gGnF5WdHOW2hkwA@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).