Gnus development mailing list
 help / color / mirror / Atom feed
From: Uwe Brauer <oub@mat.ucm.es>
To: ding@gnus.org
Subject: Re: message-dont-send in queue folder not in draft folder
Date: Wed, 13 Dec 2023 16:46:43 +0100	[thread overview]
Message-ID: <87zfye9kbg.fsf@mat.ucm.es> (raw)
In-Reply-To: <87v892b66c.fsf@mat.ucm.es>

[-- Attachment #1: Type: text/plain, Size: 1146 bytes --]

>>> "UB" == Uwe Brauer <oub@mat.ucm.es> writes:

> Hi
> If I have gnus plugged in and I am connected to the Internet, 
> message-dont-send saves the message in my  nndraft:drafts

> If, however, gnus is not plugged in (agent on) then 
> message-dont-send again saves in that folder but 
> message-send-and-exit saves the buffer to the queue folder.

> Is there any possibility tell message-send-and-exit (with an argument)
> not to save it in the draft folder but in the queue folder?

>   (nndraft-request-associate-buffer "queue")

> Might be a possibility but are there other ones?


It seems one solution would be
to change the setting of gnus-agent-queue-mail

(defun my-gnus-queue-mail-on ()
    (interactive) 
  (setq gnus-agent-queue-mail 'always)
  (message "Now messages will always be queued"))

A bit cumbersome but doable.

Uwe Brauer 

-- 
I strongly condemn Hamas heinous atrocities on Israel, especially the despicable pogroms.
I strongly condemn Putin's war of aggression against Ukraine.
I support to deliver weapons to Ukraine's military. 
I support the EU and NATO membership of Ukraine. 


[-- Attachment #2: smime.p7s --]
[-- Type: application/pkcs7-signature, Size: 5673 bytes --]

  reply	other threads:[~2023-12-13 15:47 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-12-13 13:09 Uwe Brauer
2023-12-13 15:46 ` Uwe Brauer [this message]
2023-12-13 16:25   ` Eric Abrahamsen
2023-12-14 13:08     ` Uwe Brauer
2023-12-15  1:45       ` Eric Abrahamsen
2023-12-15  6:42         ` Uwe Brauer
2023-12-13 16:31   ` Eric S Fraga
2023-12-14 13:06     ` Uwe Brauer
2023-12-14 13:21       ` Eric S Fraga
2023-12-14 17:17         ` Uwe Brauer
2023-12-14 14:44       ` Tim Landscheidt

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=87zfye9kbg.fsf@mat.ucm.es \
    --to=oub@mat.ucm.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).