Announcements and discussions for Gnus, the GNU Emacs Usenet newsreader
 help / color / mirror / Atom feed
From: Emanuel Berg <embe8573@student.uu.se>
To: info-gnus-english@gnu.org
Subject: Re: Standard way to use Gnus?
Date: Fri, 20 Mar 2015 00:22:15 +0100	[thread overview]
Message-ID: <87h9tg7eu0.fsf@debian.uxu> (raw)
In-Reply-To: <mailman.2344.1426803317.31049.info-gnus-english@gnu.org>

asjo@koldfront.dk (Adam Sjøgren) writes:

> Gnus has scoring, which can be as simple as a
> killfile, and very complex, even adaptive, if that
> is what you want.

If you mean the KILL file that has a syntax like this

    (gnus-kill "From" "L. Amer" '(gnus-summary-mark-as-read nil "X") t)
    (gnus-kill ... )
    ...
    (gnus-expunge "X")

- then that functionality is indeed useful but I don't
like the mixture of data and code in this case. It is
too simple, and too basic, and comes in to big a
quantity to be done in Elisp.

Just killing posts based on header qualities should
only involve a list of what is to be killed.

But the Elisp way might be useful for more elaborate
uses, so I'm not saying it should be removed, only
simplified alongside.

Compare the KILL syntax (which is Elisp) to that of
the ~/.mailrc file which provides aliases for
message-mode:

    alias john    "John DiFool <difool@incal.com>"
    alias kate    "Katherine Moss <mossy@km.com>"
    alias friends john kate

That file can also be put into conf-space-mode to make
it look good.

Other than that, I miss a fast way to insert to the
KILL file from an article buffer. Like
"gnus-article-kill-author" that would forever expunge
that e-mail from your system. Just extract header
data, make a line, and append it to a file.

It shouldn't be difficult to solve (either problem),
so I'll read the scoring section in the manual right
now to see if anyone did. To be concluded...

> I only use two levels: articles I want to be
> automatically marked as read (but still show up in
> lists) and articles I don't even want to know
> existed.

Yes, the system seems super powerful. Too powerful,
perhaps. Well, perhaps it was written in the heydays
of Usenet when there were zillion of posts everywhere.
Nowadays what I can see most groups are pretty serious
with at most one or two oddballs who you can easily
kill manually if they get on your nerves.

-- 
underground experts united
_______________________________________________
info-gnus-english mailing list
info-gnus-english@gnu.org
https://lists.gnu.org/mailman/listinfo/info-gnus-english

  parent reply	other threads:[~2015-03-19 23:22 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-17 21:59 David Masterson
2015-03-18 19:59 ` Emanuel Berg
     [not found] ` <zfudnUkDnvD5lZbInZ2dnUU7-LudnZ2d@supernews.com>
2015-03-19 18:40   ` Non Gnuser
2015-03-19 22:13     ` Adam Sjøgren
     [not found]     ` <mailman.2344.1426803317.31049.info-gnus-english@gnu.org>
2015-03-19 23:22       ` Emanuel Berg [this message]
2015-03-20  6:23         ` Adam Sjøgren
2015-03-20 21:12         ` interface to KILL file (was: Re: Standard way to use Gnus?) Emanuel Berg
2015-03-23 16:28       ` Standard way to use Gnus? Non Gnuser
2015-03-19 23:14 ` Jeffrey DeLeo
2015-03-20  7:05 ` Glyn Millington
     [not found] ` <mailman.2362.1426837049.31049.info-gnus-english@gnu.org>
2015-03-20 23:18   ` David Masterson
2015-03-21  7:33     ` Glyn Millington
     [not found]     ` <mailman.2465.1426963087.31049.info-gnus-english@gnu.org>
2015-03-22 23:12       ` David Masterson

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=87h9tg7eu0.fsf@debian.uxu \
    --to=embe8573@student.uu.se \
    --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).