Announcements and discussions for Gnus, the GNU Emacs Usenet newsreader
 help / color / mirror / Atom feed
From: Winston <wbe@UBEBLOCK.psr.com.invalid>
To: info-gnus-english@gnu.org
Subject: Re: on automatic gnus-summary-insert-new-articles after posting
Date: Sun, 29 Jul 2018 10:37:22 -0400	[thread overview]
Message-ID: <ydk1pexg4d.fsf@UBEblock.psr.com> (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.  ...

> 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.

Some adjustments you could try to see if they help:

(setq gnus-use-cross-reference t)
(setq gnus-thread-indent-level 2)
(setq gnus-thread-sort-functions '(gnus-thread-sort-by-subject))

I find that sorting threads by subject does a decent job of putting
related articles together, even when their original context is no longer
in the article summary.

Next, use Gnus article scoring to highlight articles you've posted and
replies to them:

* Increase score in all newsgroups on articles "From" you (<r@dev.null>)

and

* Increase score in all newsgroups on articles with "References" that
  include "fsf@dev.null>"

The easiest way to do that is usually to start by going to an article
you posted.

The scoring rules should end up in News/all.SCORE and (depending on what
you left in the string to match on) might look something like:

(("from"
  ("r@dev\\.null" 1000 nil r))
 ("references"
  ("\\.fsf@dev\\.null>" 1000 nil r))

[I'm not certain about the "\\." instead of just plain "." above, but I
think it's a regular expression and thus needs \. to prevent "." from
being the 1-char wild card.]

If you follow groups that are very active, setting a number-of-articles
limit such as

(setq gnus-large-newsgroup 400)

might also be helpful.  If there are more articles than the limit, you
get the choice of which (oldest or newest), and how many to view.

HTH,
 -WBE

  parent reply	other threads:[~2018-07-29 14:37 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
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 [this message]
     [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=ydk1pexg4d.fsf@UBEblock.psr.com \
    --to=wbe@ubeblock.psr.com.invalid \
    --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).