Announcements and discussions for Gnus, the GNU Emacs Usenet newsreader
 help / color / mirror / Atom feed
From: Francis Moreau <francis.moro@gmail.com>
To: info-gnus-english@gnu.org
Subject: Re: What's a killed article ?
Date: Fri, 09 Jan 2009 12:17:06 +0100	[thread overview]
Message-ID: <m2y6xkk9u5.fsf@gmail.com> (raw)
In-Reply-To: <m2vdthnthn.fsf@free.fr>

harven <harven@free.fr> writes:

[...]

> - GNUS-SECONDARY-SELECT-METHODS
>   and gnus-select-method. A single select method but many secondary
>   methods ? Why  differentiate ? Is it correct to put a mail group
>   as the primary method ?

I definitely agree.

And the sad thing is that this part is almost the first thing the user
is going to read when using gnus for the first time and is confusing.

In my understanding (mostly based on experiments) groups which belongs
to the primary server (the one given by gnu-select-method) can be
retrieved from another news server later. You just need to change the
server from gnus-select-method or by starting gnus with 'C-u M-x
gnus' (which is a bad idea actually, see later). IOW these groups
aren't stick to one server.

In contrary groups which belong to secondary servers (given by
gnus-secondary-select-methods) include the server name in their
names. So they can not be opened from different servers later.

This difference seems really useless: it gave me totaly disaster
results when I tried to swithc the primary server with 'C-u M-x gnus'
and get back to my initial server: all articles were marked as
unread. Even worse I set (display . all) on all these groups but gnus
seems to ignore it now...

Whereas the gnus doc, it says:

,----
|    A slightly different approach to foreign groups is to set the
| `gnus-secondary-select-methods' variable.  The select methods listed in
| this variable are in many ways just as native as the
| `gnus-select-method' server.  They will also be queried for active
`----

note the "in may ways just as native as the...", which sounds totaly
useless since we still don't know what the differences are.

Of course all of this is from a gnus dumb user...
-- 
Francis

  parent reply	other threads:[~2009-01-09 11:17 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-12-03 19:41 Francis Moreau
2008-12-03 19:47 ` Reiner Steib
2008-12-04  9:06   ` Francis Moreau
2008-12-04 19:33     ` Reiner Steib
2008-12-04 21:46       ` Francis Moreau
2008-12-05 17:48         ` Ted Zlatanov
2008-12-05 21:21           ` Francis Moreau
2008-12-05 22:19             ` Glyn Millington
     [not found]             ` <mailman.2031.1228517278.26697.info-gnus-english@gnu.org>
2008-12-06 13:49               ` Francis Moreau
2008-12-08 15:46             ` Ted Zlatanov
2008-12-08 18:05               ` Giorgos Keramidas
2008-12-15 19:21                 ` Francis Moreau
2008-12-16  2:30                   ` Giorgos Keramidas
2008-12-18 20:00                     ` harven
2008-12-23  8:17                       ` Giorgos Keramidas
2008-12-23 22:51                       ` Ted Zlatanov
2009-01-09 11:25                         ` Francis Moreau
2009-01-09 11:30                         ` Francis Moreau
2009-01-09 11:17                       ` Francis Moreau [this message]
2009-01-09 11:28                         ` Francis Moreau
2008-12-15 19:21               ` Francis Moreau
2008-12-16 17:17                 ` Ted Zlatanov

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=m2y6xkk9u5.fsf@gmail.com \
    --to=francis.moro@gmail.com \
    --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).