From: Richard Riley <rileyrg@googlemail.com>
To: Alberto Luaces <aluaces@udc.es>
Cc: ding@gnus.org
Subject: Re: message-confirm-send
Date: Sat, 23 Oct 2010 12:18:28 +0200 [thread overview]
Message-ID: <1ppqv1mcuj.fsf@news.eternal-september.org> (raw)
In-Reply-To: <87y69p9skh.fsf@eps142.cdf.udc.es> (Alberto Luaces's message of "Sat, 23 Oct 2010 11:17:18 +0200")
Alberto Luaces <aluaces@udc.es> writes:
> jidanni@jidanni.orgwrites:
>
>>>>>>> "LMI" == Lars Magne Ingebrigtsen <larsi@gnus.org> writes:
>> LMI> jidanni@jidanni.org writes:
>>
>>>> OK, you forced me to do
>>>> (defun jidanni-message-confirm ()
>>>> "Confirm that we really want to send the message."
>>>> (interactive)(or (y-or-n-p "Send?")(keyboard-quit)))
>>>> (add-hook 'message-send-hook 'jidanni-message-confirm)
>>>> At least add an example to the manual.
>>>>
>>>> Imagine sending a mail to people you respect, cut off in mid-
>>
>> LMI> Heh heh heh.
>>
>> LMI> Well, I've sent more than my share of messages prematurely by leaning on
>> LMI> `C-c C-c', so I'm sympathetic, but on the other hand, all equivalent
>> LMI> Emacs things (like checking in stuff into VCs) work with `C-c C-c'
>> LMI> without any "warning". So I think it should remain that way.
>>
>> Yeah with VCs you could just check it back out. But with email you have
>> to send apologies, unless you already sent the corporate secrets due to
>> cut and paste errors.
>>
>> Do provide the function but leave the variable to activate it off. That way
>> users could just toggle a variable instead of having to muck around
>> writing their own hack.
>
> What about just mapping also `C-c C-c' to `message-dont-send' if you
> want to reread before sending?
C-c C-c is ingrained as "process".
I would agree that the confirm could and should be built in
however. Possibly based on a group parameter "Prompt to confirm
post". Defaulted to nil so default stays the same.
next prev parent reply other threads:[~2010-10-23 10:18 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-14 18:58 message-confirm-send jidanni
2007-11-14 21:05 ` message-confirm-send Adam Sjøgren
2007-11-14 21:09 ` message-confirm-send Leo
2007-11-15 20:13 ` message-confirm-send jidanni
2007-11-15 20:29 ` message-confirm-send Bastien
2007-11-15 22:47 ` message-confirm-send jidanni
2007-11-15 22:55 ` message-confirm-send Karl Kleinpaste
2007-11-15 23:08 ` message-confirm-send Russ Allbery
2007-11-15 23:38 ` message-confirm-send jidanni
2007-11-15 23:58 ` message-confirm-send Miles Bader
2007-11-16 0:20 ` message-confirm-send Russ Allbery
2007-11-17 2:37 ` message-confirm-send Miles Bader
2007-11-17 10:23 ` message-confirm-send Bastien
2007-12-06 12:48 ` message-confirm-send jidanni
2007-12-06 18:31 ` message-confirm-send Reiner Steib
2007-12-12 17:50 ` message-confirm-send jidanni
2007-11-25 3:26 ` message-confirm-send Giorgos Keramidas
2007-12-18 5:24 ` shell-mode flakey [was Re: message-confirm-send] jidanni
[not found] ` <mailman.5147.1197955487.18990.bug-gnu-emacs@gnu.org>
2007-12-18 16:19 ` shell-mode flakey Roland Winkler
2007-12-19 0:31 ` Miles Bader
2007-12-19 2:22 ` Russ Allbery
[not found] ` <mailman.5185.1198024311.18990.bug-gnu-emacs@gnu.org>
2007-12-19 16:25 ` Sven Joachim
2007-11-17 9:23 ` message-confirm-send Reiner Steib
2007-11-25 3:20 ` message-confirm-send Giorgos Keramidas
2007-11-26 12:51 ` message-confirm-send jidanni
2007-11-21 16:31 ` message-confirm-send Ted Zlatanov
2007-11-14 21:18 ` message-confirm-send Bastien
2010-10-01 20:03 ` message-confirm-send Lars Magne Ingebrigtsen
2010-10-23 4:22 ` message-confirm-send jidanni
2010-10-23 9:17 ` message-confirm-send Alberto Luaces
2010-10-23 10:18 ` Richard Riley [this message]
2010-10-23 13:55 ` message-confirm-send Bruno Tavernier
2010-10-24 14:46 ` message-confirm-send jidanni
2010-10-25 18:32 ` message-confirm-send Ted Zlatanov
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=1ppqv1mcuj.fsf@news.eternal-september.org \
--to=rileyrg@googlemail.com \
--cc=aluaces@udc.es \
--cc=ding@gnus.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.
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 NNTP newsgroup(s).