help-gnu-emacs
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: GNUS gnus-group-split .. my sorting is bad.


From: Emanuel Berg
Subject: Re: GNUS gnus-group-split .. my sorting is bad.
Date: Thu, 25 Feb 2016 23:00:12 +0100
User-agent: Gnus/5.13 (Gnus v5.13) Emacs/24.5 (gnu/linux)

Nils Gillmann <niasterisk@grrlz.net> writes:

> Here's a question: why? What's the rational choice
> to favor gmane over subscribing to mailman at
> gnu.org for the Guix project and others
> I participate in?

There are many advantages. Three that instantly come
to mind are:

1. You get the lists/newsgroups as a uniform Emacs
   interface and you don't have to Google individual
   sites and wade thru the projects different homepages
   to get to their lists. You only have to bring up
   the 'browse server' buffer to see them all -
   organized, sorted, and you can search the buffer
   like any other (so it is a double "uniform Emacs
   interface"). Have a look:

       http://user.it.uu.se/~embe8573/pics/gnus-server.png

2. You can add, interact, and remove lists/newsgroups
   like any other NNTP newsgroup and you don't have to
   deal with verification and e-mails back and forth
   from different automatic systems which often do not
   work or take time to react to the point you wonder
   if it actually did work...

3. Instead of getting all the traffic all the time,
   you only fetch data when you want it. (At least
   compared to nnml. YMMV. But if it is the same for
   you, it should be a *huge* advantage as you are on
   so many lists!) E.g., I subscribe to the
   gmane.emacs.erc.general as well as
   gmane.emacs.help. On gmane.emacs.help, I'm active
   writing so I want all traffic. But, on
   gmane.emacs.erc.general, I only ask one specific
   question or so once a couple of months. So I always
   want gmane.emacs.help, but very seldom
   gmane.emacs.erc.general (still, I want it to be
   there, ready), and with Gmane this is not only
   possible but super easy to do.

> I also have lists which are not on gmane or some
> other serverbased network with nntp access.
> for example local hackerspaces.

Gmane does not exclude any other source of data to be
used in parallel:

    (setq gnus-select-method '(nntp "news.gmane.org"))

    (require 'gnus-namazu)
    (setq gnus-secondary-select-methods '((nnml "" (nnir-search-engine namazu))
                                          (nntp "nntp.aioe.org")
                                          (nntp "news.gwene.org")
                                          (nntp "news.gnus.org")
                                          ))

> That's the usual behavior on mosts lists (or how
> most people configure their mail agents) I am on,
> To: person you replying to, CC: list.

Isn't it the other way around?

But it doesn't matter. Like I said, you can use
splitting to take those to an out-of-action group.

I do that - add the list to the splitting regexp -
when it happens, i.e. when I get a superfluous mail
which originated from a list/group I know I'm on
so I know I'll see the post anyway.

    (setq nnmail-split-methods
          '(
            ("mail.ml-ooa" 
"\\(To\\|Cc\\):.*\\(emacs-w3m@namazu.org\\|help-gnu-emacs@gnu.org\\|gnuplot-info@lists.sourceforge.net\\)")
            ("mail.misc"   "")) )

> In the whole picture - leaving aside the whole other
> issue with email in general, with an external
> service as gmane, etc - your recommendation looks
> good to me. It can be done for almost all lists
> I have, however I would still need a recommendation
> for the ones I can't apply it to. Take the CC and Cc
> out of the filters for lists?

You can do it with splitting or with scoring.
Splitting would be favorable (more transparent) at
least in its base form as it doesn't require you to
enter the group to execute.

Add the newsgroup from Gmane, wait for the CCs to
come, when they do split or downscore and they
shouldn't return.

-- 
underground experts united
http://user.it.uu.se/~embe8573




reply via email to

[Prev in Thread] Current Thread [Next in Thread]