From: Lars Ingebrigtsen <larsi@gnus.org>
To: ding@gnus.org
Subject: Re: gnus-agent-prompt-send-queue
Date: Tue, 25 Jan 2011 13:24:57 -0800 [thread overview]
Message-ID: <87hbcwad7a.fsf@gnus.org> (raw)
In-Reply-To: <tqmxmpulu5.fsf@news.eternal-september.org>
Richard Riley <rileyrg@googlemail.com> writes:
> Fair enough, and easily done, but Whats the use case for the existing
> variable?
Some people use the Agent offline thing as a real "offline" thing. That
is, when they don't have a connection. However, most people use the
Agent just as a dynamic cache, and the sending queue as a "eek, I didn't
mean to send that email, let me delete it" thing. In the latter case
being "strict" about the unpluggedness when sending was just too annoying.
--
(domestic pets only, the antidote for overdose, milk.)
larsi@gnus.org * Lars Magne Ingebrigtsen
next prev parent reply other threads:[~2011-01-25 21:24 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-24 13:50 gnus-agent-prompt-send-queue Richard Riley
2011-01-24 21:54 ` gnus-agent-prompt-send-queue Lars Ingebrigtsen
2011-01-25 13:58 ` gnus-agent-prompt-send-queue Richard Riley
2011-01-25 21:24 ` Lars Ingebrigtsen [this message]
2011-01-25 21:51 ` gnus-agent-prompt-send-queue Richard Riley
2011-01-26 23:28 ` gnus-agent-prompt-send-queue Eric S Fraga
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=87hbcwad7a.fsf@gnus.org \
--to=larsi@gnus.org \
--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).