From: Eric Abrahamsen <eric@ericabrahamsen.net>
To: info-gnus-english@gnu.org
Subject: Re: on automatic gnus-summary-insert-new-articles after posting
Date: Sat, 28 Jul 2018 23:52:55 -0700 [thread overview]
Message-ID: <87zhya5y9k.fsf@ericabrahamsen.net> (raw)
In-Reply-To: <8636w2hp1b.fsf@dev.null>
Robert Girault <r@dev.null> writes:
[...]
> This brings me to a point I've been trying to set up Gnus for. I'd like
> to keep, for a while, a history of everything I wrote. Saving messages
> locally isn't good enough because the context is gone. The context is
> the thread.
>
> When I enter a group, I feel lost. I think it's slrn that I've used in
> the past. When I'd enter a news group, I'd have a clear idea of what's
> happening---which threads are growing and which are not.
I looked up slrn, and interestingly the author seemed to have written it
because he found Gnus too slow!
I don't know how slrn does it, so I don't know exactly what effect
you're after. Are you using threading? I've got `gnus-show-threads' set
to t and `gnus-fetch-old-headers' set to 'some, and that shows me just
as much context as I want.
> Also, my way of working is to write articles, but only post them after
> I've reviewed them. I haven't yet acquired skills enough to do that
> with Gnus.
>
> I know it's possible to save them as drafts and send them later, but I'd
> like to distinguish between partially written messages from messages
> queued for delivery.
You can use the agent for this. When you're finished with a message, hit
"C-c C-j" (gnus-delay-article), and you can choose a future date at
which the message will send. It won't actually send at that date unless
you run the `gnus-delay-send-queue' command in the *Group* buffer. That
might do what you want, though I don't know how easy it is to edit
messages once you've added them to the queue.
> I've read An Introduction to Emacs Lisp and I really liked it. I wish
> there was a book on Gnus. I'm very grateful for the Gnus manual, but I
> confess that, whenever I stop to read it, I try to make the things it
> advertises happen, but I fail to do so a good number of the times. So
> I'm always thinking that I need some sort of education that I don't have
> in order to read the manual properly. Has anyone ever written a book on
> Gnus?
Pretty sure not!
Eric
next prev parent reply other threads:[~2018-07-29 6:52 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-28 15:35 Robert Girault
2018-07-28 16:13 ` Eric Abrahamsen
[not found] ` <mailman.4364.1532794430.1292.info-gnus-english@gnu.org>
2018-07-28 19:54 ` Robert Girault
2018-07-28 20:42 ` Winston
2018-07-28 20:59 ` Eric Abrahamsen
[not found] ` <mailman.4365.1532811610.1292.info-gnus-english@gnu.org>
2018-07-29 0:19 ` Robert Girault
2018-07-29 6:52 ` Eric Abrahamsen [this message]
2018-07-29 8:07 ` Adam Sjøgren
2018-07-29 16:42 ` Eric Abrahamsen
2018-07-29 18:04 ` Adam Sjøgren
2018-07-29 8:03 ` Adam Sjøgren
2018-07-29 14:37 ` Winston
[not found] ` <mailman.4370.1532847194.1292.info-gnus-english@gnu.org>
2018-07-29 16:00 ` Robert Girault
2018-07-29 16:15 ` on continuing from where left off (Was: Re: on automatic gnus-summary-insert-new-articles after posting) Robert Girault
2018-07-29 17:17 ` on automatic gnus-summary-insert-new-articles after posting Eric Abrahamsen
2018-07-30 1:26 ` Robert Girault
[not found] ` <mailman.4372.1532851440.1292.info-gnus-english@gnu.org>
2018-07-29 16:04 ` Robert Girault
2018-07-29 18:03 ` Adam Sjøgren
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=87zhya5y9k.fsf@ericabrahamsen.net \
--to=eric@ericabrahamsen.net \
--cc=info-gnus-english@gnu.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).