From: Lars Ingebrigtsen <larsi@gnus.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 19368@debbugs.gnu.org
Subject: bug#19368: 25.0.50; NSM prompt is not self-explanatory enough
Date: Fri, 05 Feb 2016 14:53:58 +1100 [thread overview]
Message-ID: <87vb63vmll.fsf@gnus.org> (raw)
In-Reply-To: <83lhma43ty.fsf@gnu.org> (Eli Zaretskii's message of "Sun, 14 Dec 2014 18:02:33 +0200")
Eli Zaretskii <eliz@gnu.org> writes:
> Sounds useful, thanks. Bonus points for optionally popping a dialog
> (via x-popup-dialog) when the command was invoked by a mouse.
I cargo culted the code from y-or-n-p to determine whether to use
x-popup-dialog, and it seems to be working...
> Btw, if you do that, userlock.el cries for using this functionality,
> and likewise hack-local-variables-confirm.
I think I'll leave that to somebody else to fix. :-)
--
(domestic pets only, the antidote for overdose, milk.)
bloggy blog: http://lars.ingebrigtsen.no
next prev parent reply other threads:[~2016-02-05 3:53 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <87a8j3llba.fsf@lifelogs.com>
2014-12-13 14:39 ` bug#19368: 25.0.50; NSM prompt is not self-explanatory enough Eli Zaretskii
2014-12-14 4:43 ` Stefan Monnier
2014-12-14 11:37 ` Ted Zlatanov
2016-02-05 3:43 ` Lars Ingebrigtsen
2014-12-14 8:12 ` Lars Magne Ingebrigtsen
2014-12-14 16:02 ` Eli Zaretskii
2014-12-14 22:48 ` Stefan Monnier
2014-12-21 11:50 ` Lars Ingebrigtsen
2016-02-04 7:24 ` Lars Ingebrigtsen
2016-02-04 16:47 ` Eli Zaretskii
2016-02-05 3:53 ` Lars Ingebrigtsen [this message]
2016-02-05 3:35 ` Lars Ingebrigtsen
2016-02-05 7:42 ` Eli Zaretskii
2016-02-05 7:46 ` Lars Ingebrigtsen
2016-02-05 9:34 ` Eli Zaretskii
2016-02-06 3:09 ` Lars Ingebrigtsen
2016-06-02 14:31 ` Archived problem report bug#19368 (bug#19368: 25.0.50; NSM prompt is not self-explanatory enough) GNU bug Tracking System
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=87vb63vmll.fsf@gnus.org \
--to=larsi@gnus.org \
--cc=19368@debbugs.gnu.org \
--cc=eliz@gnu.org \
/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.