Gnus development mailing list
 help / color / mirror / Atom feed
From: Kevin Greiner <kgreiner@xpediantsolutions.com>
Subject: Re: Gnus Agent and mail
Date: Sun, 11 May 2003 18:20:26 -0500	[thread overview]
Message-ID: <ur875vznp.fsf@xpediantsolutions.com> (raw)
In-Reply-To: <87k7cytpco.fsf@cam.ac.uk>

Gaute B Strokkenes <gs234@cam.ac.uk> writes:

> On 10 mai 2003, gs234@cam.ac.uk wrote:
>>On 10 mai 2003, kgreiner@xpediantsolutions.com wrote:
>>>BTW, I'm actually convincing myself that gnus-agent-queue-mail is
>>>the reasonable thing to do.
>>
>>Well, I'm having a stab at implementing it now...
>
> And here it is.
>
> 2003-05-10  Gaute B Strokkenes <gs234@srcf.ucam.org>
>
> 	* gnus-agent.el (gnus-agent-queue-mail): New variable.
> 	(gnus-agent-send-mail): Use it.

This part seems fine.


> 	* gnus-draft.el (gnus-group-send-queue): Bind
> 	message-send-mail-real-function to the value of
> 	gnus-agent-send-mail-function when sending queued mail.

I don't like the idea of messing with
message-send-mail-real-function. What happens to someone who is not
using the agent (i.e. gnus-agent-send-mail-function is nil)?

What issue are you trying to resolve by adding this binding?

> If you find this approach at all acceptable, I will start work on the
> documentation.
>
> AFAICT there is only one change in behaviour when using the default
> configuration: if you hit J S in the Group buffer when unplugged, Gnus
> will actually try to send any queued email rather than just rewriting
> them to the queue folder.  This is arguably an improvement; if not it
> is probably better to have a "are you sure" nag message anyway.

We will have to wait until the code is checked in to see what is
arguable.  I've learned that some people find any behavior changes to
be objectable.


Kevin



  reply	other threads:[~2003-05-11 23:20 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-01-24  8:33 Sean Neakums
2003-01-24 12:52 ` Kai Großjohann
2003-01-24 13:49   ` Sean Neakums
2003-01-24 22:00     ` Lars Magne Ingebrigtsen
2003-04-13 21:10 ` Kevin Greiner
2003-04-13 21:18   ` Sean Neakums
2003-04-13 23:32     ` Kevin Greiner
2003-04-14  6:15   ` Kai Großjohann
2003-04-18  6:31     ` Gaute B Strokkenes
2003-04-29  5:40       ` Kevin Greiner
2003-04-29 15:28         ` Kai Großjohann
2003-04-30  2:12           ` Kevin Greiner
2003-05-01 10:57             ` Kai Großjohann
2003-05-08 23:36         ` Gaute B Strokkenes
2003-05-10 14:43           ` Kevin Greiner
2003-05-10 16:08             ` Gaute B Strokkenes
2003-05-10 22:21               ` Gaute B Strokkenes
2003-05-11 23:20                 ` Kevin Greiner [this message]
2003-05-12  5:52                   ` Gaute B Strokkenes
2003-05-12 13:47                     ` Kevin Greiner
2003-05-12 18:46                       ` Gaute B Strokkenes
2003-05-12 20:37                         ` Gaute B Strokkenes
2003-05-14 11:07                           ` Gaute B Strokkenes
2003-05-14 17:15                             ` Kevin Greiner
2003-05-14 20:15                               ` Gaute B Strokkenes
2003-05-15  8:15                                 ` Gaute B Strokkenes
2003-05-12 15:51                     ` Kai Großjohann
2003-05-12 18:49                       ` Gaute B Strokkenes
2003-05-13 12:31                         ` Kai Großjohann
2003-05-10 17:35             ` Kai Großjohann
2003-05-10 20:54               ` Gaute B Strokkenes
2003-05-12 15:49                 ` Kai Großjohann

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=ur875vznp.fsf@xpediantsolutions.com \
    --to=kgreiner@xpediantsolutions.com \
    /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).