Announcements and discussions for Gnus, the GNU Emacs Usenet newsreader
 help / color / mirror / Atom feed
From: Robert Girault <r@dev.null>
To: info-gnus-english@gnu.org
Subject: Re: on automatic gnus-summary-insert-new-articles after posting
Date: Sat, 28 Jul 2018 21:19:12 -0300	[thread overview]
Message-ID: <8636w2hp1b.fsf@dev.null> (raw)
In-Reply-To: <mailman.4365.1532811610.1292.info-gnus-english@gnu.org>

Eric Abrahamsen <eric@ericabrahamsen.net> writes:

> Winston <wbe@UBEBLOCK.psr.com.invalid> writes:
>
>> Robert Girault <r@dev.null> writes:
>>> How can I 
>>>    
>>>   gnus-summary-insert-new-articles
>>>
>>> automatically after posting?  I'd like to see my articles right away in
>>> the thread without having to ``/ N'' every time I post.
>
> Oh I see, I had indeed misunderstood your question.
>
>> I don't have an answer for the question you asked, but I'll point out
>> that, in theory, articles don't necessarily appear for reading instantly
>> after you post them.  Articles to a moderated group, for example, will
>> go to the moderator for approval.  Articles to unmoderated groups may be
>> subject to input filtering, throttling, indexing for overviews, etc.,
>> such that the faster you re-check for new articles, the less likely you
>> are to find your new one.  You could work around the latter issue a bit
>> if you can do "sleep N sec, check".
>
> Right: it's unknown when the message will actually appear. I can't think
> of any better trick than a timer (or patience), but it might work better
> to do "M-g" (rescan) rather than show old articles.

I didn't think very well about it.  I think I was having the impression
that, in the case of an article I posted myself, Gnus would insert the
article because it had a copy of it (since I wrote it).  (A hack.)  And,
in the case of articles coming from the server, it would add them
because it received them from the network.

This isn't impossible: when eventually my article comes from the
network, if it does, Gnus would replace it.  But this is undesirable
indeed.  If my article doesn't ever come, as well pointed out by
Winston, I should know.

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.

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.

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?

  parent reply	other threads:[~2018-07-29  0:19 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 [this message]
2018-07-29  6:52       ` Eric Abrahamsen
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=8636w2hp1b.fsf@dev.null \
    --to=r@dev.null \
    --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).