Gnus development mailing list
 help / color / mirror / Atom feed
From: Bastien <bzg@altern.org>
To: ding@gnus.org
Subject: Re: message-confirm-send
Date: Sat, 17 Nov 2007 10:23:37 +0000	[thread overview]
Message-ID: <877ikhgogm.fsf@bzg.ath.cx> (raw)
In-Reply-To: <874pfl1tsu.fsf@catnip.gol.com> (Miles Bader's message of "Sat, 17 Nov 2007 11:37:21 +0900")

Miles Bader <miles@gnu.org> writes:

> Russ Allbery <rra@stanford.edu> writes:
>>> I suppose it's all a bit too much effort (needs MTA cooperation etc) for
>>> the gain though.  [and would probably cause tons of complaints about
>>> your "slow" mail system...]
>>
>> Gnus could probably implement something like this internally, though,
>> using a concept similar to the drafts group.
>
> The problem would seem to be reliability -- once they've hit send,
> people really, _really_, don't want email to be lost or even delayed for
> longer than expected (e.g. a "undoable delay" of 5 minutes might be
> acceptable, but 2 days almost certainly isn't).

I think some internal Gnus way of undoing mails would be a mistake.  If
someone finds C-c C-c to be too dangerous, he might also use a different
key (provided he's aware that he will get used to this new key soon.)

> MTAs in general have put huge amounts of effort into making mail queuing
> fairly reliable, but I think any Gnus specific solution is bound to be
> less so (and it's probably a lot of work to make it reliable).

I tend to use C-c C-d more and more myself.  Not only when I'm offline,
but also when I plan to quickly review the mail I send.

-- 
Bastien



  reply	other threads:[~2007-11-17 10:23 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                   ` Bastien [this message]
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       ` message-confirm-send Richard Riley
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=877ikhgogm.fsf@bzg.ath.cx \
    --to=bzg@altern.org \
    --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).