From: Eric S Fraga <e.fraga@ucl.ac.uk>
To: Richard Riley <rileyrg@googlemail.com>
Cc: ding@gnus.org
Subject: Re: send from queue
Date: Wed, 26 Jan 2011 12:26:11 +0000 [thread overview]
Message-ID: <87bp33lul8.fsf@ucl.ac.uk> (raw)
In-Reply-To: <4fwrlsvncg.fsf@news.eternal-september.org> (Richard Riley's message of "Tue, 25 Jan 2011 19:40:15 +0100")
Richard Riley <rileyrg@googlemail.com> writes:
> Eric S Fraga <e.fraga@ucl.ac.uk> writes:
>
>> Richard Riley <rileyrg@googlemail.com> writes:
>>
>>> asjo@koldfront.dk (Adam Sjøgren) writes:
>>>
>>>> On Mon, 24 Jan 2011 14:44:43 +0100, Richard wrote:
>>>>
>>>>> No it isnt : I was asking about sending from the Queue summary. The
>>>>> send queue docs refer the reader to Drafts.
>>>>
>>>> I got confused by your long explanations I think. Couldn't your entire
>>>> article be summed up as "I'd like the D s functionality found in drafts
>>>> to work in queue as well"?
>>>
>>> Because its not the same thing. Queue is not drafts : clearly there is
>>> some common ground but it isnt clear. A Queue is somewhere you store
>>> done messages to be reviewed/sent later.
>>
>> +1
>>
>> I use queueing to write emails offline daily (e.g. while on the train on
>> my long commute where I actually do most of my email reading+writing).
>> I expect to send queued messages out when I connect without checking
>> (although obviously it's nice to be able to check them if I decide to).
>> Drafts are very much for *incomplete* emails that I will not send
>> without reviewing. I may often have both queued and draft emails after
>> my train journey. Very different use cases.
>
> Phew ;)
>
> Thanks Eric.
>
> Clearly there is overlap.
>
> Out of interest does D s work for you from the queue?
Never tried it. I simply use J S to send the whole queue after plugging
in. I'll try to remember to try this next time...
--
: Eric S Fraga (GnuPG: 0xC89193D8FFFCF67D) in Emacs 24.0.50.1 + No Gnus v0.11
next prev parent reply other threads:[~2011-01-26 12:26 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
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:10 ` Yes/no -> because [Was: send from queue] Adam Sjøgren
2011-01-25 20:11 ` Sending from queue/drafts " Adam Sjøgren
2011-01-25 20:11 ` send from queue 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 [this message]
2011-01-26 13:29 ` Richard Riley
-- strict thread matches above, loose matches on Subject: below --
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
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
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=87bp33lul8.fsf@ucl.ac.uk \
--to=e.fraga@ucl.ac.uk \
--cc=ding@gnus.org \
--cc=rileyrg@googlemail.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).