From: Richard Riley <rileyrg@googlemail.com>
To: ding@gnus.org
Subject: Re: Unplugged or Offline mode
Date: Tue, 03 May 2011 17:39:39 +0200 [thread overview]
Message-ID: <89y62nx078.fsf@news.eternal-september.org> (raw)
In-Reply-To: <87vcxrajox.fsf@pinto.chemeng.ucl.ac.uk>
Eric S Fraga <e.fraga@ucl.ac.uk> writes:
> Deepak Tripathi <deepak@gnumonk.com> writes:
>
>> Robert Pluim <rpluim@gmail.com> writes:
>>
>>> Eric S Fraga <e.fraga@ucl.ac.uk> writes:
>> D t and D s works from nndraft:drafts folders, How to use it from
>> nndraft:queue ?
>
> No idea. When I have drafts, I typically edit them (e) and then send
> (C-c C-c), save for later further processing (C-c C-d) or discard (C-c
> C-k), as appropriate.
>
> If I have queued messages, I send them from the group buffer (J S).
>
> For me, draft and queued messages are very distinct. Anything in the
> queue *will* be sent: they are complete messages that I do not need to
> look at again before sending (except in extreme cases). Draft messages
> are those which should *not* be sent without further editing. Very
> different use cases and gnus handles the distinction very nicely, IMO.
just some notes, comments which might make the OP a little more
comfortable with Gnus...
I'm not sure I would describe it handling it nicely per se - its
confusing I think and takes a while to get your head around. Also both
draft and queue have the same key sequences since they are "kind of" one
of the same.
I work pretty much the same as you but I dont bother with offline
anymore since the registry doesnt work with multiple gmail accounts
(posted a few times) for me. A shame as I struggled for ages to get this
working. I activate based on topic levels and have the option set to
always queue outgoing email regardless of online or offline.
Drafts I can send from the draft queue with D s which sends it to the
queue. This is correct. And from the queue I can D s from within the
queue or do a J S at the group buffer levels.
Except for Gnus not correctly updating the draft/queue counts it works
very nicely.
next prev parent reply other threads:[~2011-05-03 15:39 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-02 14:33 Deepak Tripathi
2011-05-03 8:01 ` Eric S Fraga
2011-05-03 9:28 ` Robert Pluim
2011-05-03 10:34 ` Deepak Tripathi
2011-05-03 12:15 ` Richard Riley
2011-05-03 15:24 ` Eric S Fraga
2011-05-03 12:13 ` Richard Riley
2011-05-03 12:36 ` Deepak Tripathi
2011-05-03 13:14 ` Richard Riley
2011-05-04 9:56 ` Deepak Tripathi
2011-05-03 12:14 ` Deepak Tripathi
2011-05-03 15:27 ` Eric S Fraga
2011-05-03 15:39 ` Richard Riley [this message]
2011-05-03 23:21 ` Adam Sjøgren
2011-05-04 9:59 ` Deepak Tripathi
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=89y62nx078.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).