From: Richard Riley <rileyrg@googlemail.com>
To: ding@gnus.org
Subject: Re: send from queue
Date: Mon, 24 Jan 2011 18:57:20 +0100 [thread overview]
Message-ID: <ibr5c2i3r3.fsf@news.eternal-september.org> (raw)
In-Reply-To: <pkn1v42nwn0.fsf@this.is.really.invalid> (Robert Pluim's message of "Mon, 24 Jan 2011 16:34:27 +0100")
Robert Pluim <rpluim@gmail.com> writes:
> Richard Riley <rileyrg@googlemail.com> writes:
>
>> Robert Pluim <rpluim@gmail.com> writes:
>>> I suppose Richard could just save stuff and have it end up in the draft
>>> group, and then send from there, but that kind of defeats the object of
>>> having a separate queue group. (although given how little you can do
>>> with it, perhaps it should be gotten rid of?)
>>
>> The queue is definitely a valuable edition. I think it needs some more
>> use cases to be made truly usable though. e.g It needs a single message
>> send, a queue level prompt to send when plugged as well as
>> unplugged. Possibly they are there. I find it very hard to pinpoint the
>> relevant keys from the docs though or even C-h m.
>
> I can't find them either, I suspect it was intended as a 'queue when
> offline, then batch send when online' solution.
>
>> Certainly it's a bit of a misnomer/confusing to add the queue to
>> nndrafts though.
>
> Definitely.
>
> Robert
Lars, my use case would I think be more generally useable too. Any
chance of a "send single message from queue" functionality if its not
already there?
Also, If I set the "prompt to send" option then I have to accept for it go into
the queue and then accept again when I send from queue : if I send from
the queue I dont think there should be any prompt, Opinion.
But certainly the ability to send a single message without prompt from
the queue would be valuable if its not already there (I cant find it).
regards
r.
next prev parent reply other threads:[~2011-01-24 17:57 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-24 13:01 Richard Riley
2011-01-24 13:36 ` Adam Sjøgren
2011-01-24 13:44 ` Richard Riley
2011-01-24 19:55 ` Adam Sjøgren
2011-01-24 13:50 ` Robert Pluim
2011-01-24 13:56 ` Richard Riley
2011-01-24 15:34 ` Robert Pluim
2011-01-24 17:57 ` Richard Riley [this message]
2011-01-24 21:52 ` Lars Ingebrigtsen
2011-01-25 13:47 ` Richard Riley
2011-01-25 21:19 ` Lars Ingebrigtsen
2011-01-25 21:54 ` Richard Riley
2011-01-25 22:00 ` Lars Ingebrigtsen
2011-01-25 22:42 ` Richard Riley
2011-01-27 1:18 ` Lars Ingebrigtsen
2011-01-27 17:56 ` Richard Riley
2011-01-27 23:56 ` Lars Ingebrigtsen
2011-01-28 0:52 ` Richard Riley
2011-01-25 13:44 Richard Riley
2011-01-25 16:07 ` Adam Sjøgren
2011-01-25 18:38 ` Richard Riley
2011-01-25 18:48 ` Adam Sjøgren
2011-01-25 18:59 ` Richard Riley
2011-01-25 19:56 ` Yann Hodique
2011-01-25 21:22 ` Richard Riley
2011-01-25 20:11 ` Adam Sjøgren
2011-01-25 16:39 ` Eric S Fraga
2011-01-25 18:40 ` Richard Riley
2011-01-25 18:49 ` Adam Sjøgren
2011-01-25 19:00 ` Richard Riley
2011-01-25 20:12 ` Adam Sjøgren
2011-01-26 12:26 ` Eric S Fraga
2011-01-26 13:29 ` Richard Riley
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=ibr5c2i3r3.fsf@news.eternal-september.org \
--to=rileyrg@googlemail.com \
--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).