Gnus development mailing list
 help / color / mirror / Atom feed
From: Gaute B Strokkenes <gs234@cam.ac.uk>
Subject: Re: Gnus Agent and mail
Date: Mon, 12 May 2003 06:52:21 +0100	[thread overview]
Message-ID: <87fznkg19m.fsf@cam.ac.uk> (raw)
In-Reply-To: <ur875vznp.fsf@xpediantsolutions.com>

On 12 mai 2003, kgreiner@xpediantsolutions.com wrote:
>Gaute B Strokkenes <gs234@cam.ac.uk> writes:
>>	* 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)?

The sole purpose of that function is to send queued mail (it is the
one that `J S' in the group buffer is bound to.)  So if you're not
using the agent, you're not using this function.

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

Mail is sent by this function pretty much like any other mail.
Therefore, before my patch it would be rewritten back to the queue
folder if gnus were unplugged.  (Some people might like to be
protected from hitting `J S' by mistake while unplugged, by I think
it's a misfeature.  But I digress.)  With my patch, if
gnus-agent-queue-mail is set to always, mail would always be rewritten
to the queue folder if this hunk were not present.  Then there would
be no way to send mail without temporarily setting
gnus-agent-queue-mail to t or nil.

Hmm.  Actually, is is possible to enter the queue group and send
messages with `D s' and `D S'.  I need to take care of those cases as
well.

>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.

Well, life is not supposed to be easy ;-)

-- 
Gaute Strokkenes                        http://www.srcf.ucam.org/~gs234/
Let's all show human CONCERN for REVEREND MOON's legal difficulties!!



  reply	other threads:[~2003-05-12  5:52 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
2003-05-12  5:52                   ` Gaute B Strokkenes [this message]
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=87fznkg19m.fsf@cam.ac.uk \
    --to=gs234@cam.ac.uk \
    /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).