Gnus development mailing list
 help / color / mirror / Atom feed
From: Eric Abrahamsen <eric@ericabrahamsen.net>
To: ding@gnus.org
Subject: extra server for nnmairix?
Date: Sun, 31 Oct 2010 16:08:38 +0800	[thread overview]
Message-ID: <87zktuyebd.fsf@ericabrahamsen.net> (raw)

Here's something I've never understood.

I use nnmairix, happily. In the manual it says that you can choose to
create a new backend server, or you can use an existing one. I think I'm
doing something wrong, because it behaves weirdly no matter which option
I choose.

If I use an existing server, the search group doesn't survive the next
gnus restart, and I have to do nnmairix-create-server-and-default-group
all over again each time. I've figured out how to change the
subscription level so it doesn't check my mail every time I
search—that's nice at any rate.

If I create an additional server (with a (nnml "mairix"
(nnml-get-new-mail nil)) entry in gnus-secondary-select-methods), I
actually see two new servers in my server list:

{nnmairix:search}
{nnml:mairix}

The first is empty, the second contains killed versions of all the
groups under my regular nnml server, plus the unkilled search group. Why
are all those killed groups there? Why does gnus-group-jump-to-group
show those killed groups? (I'm using the ido-completing-read interface,
which is otherwise brilliant, but makes this "duplication" of group
names particularly evident and annoying.)

I don't care which of the two methods I use, but I'd like either one
problem or the other to be solved. I suspect there's something wrong
with how I'm creating the server, but I just don't know what…

Thanks!

Eric




             reply	other threads:[~2010-10-31  8:08 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-10-31  8:08 Eric Abrahamsen [this message]
2010-10-31  9:30 ` Eric Abrahamsen
2010-10-31  9:35 ` David Engster
2010-10-31 11:12   ` Eric Abrahamsen
2010-10-31 11:09 ` David Engster
2010-10-31 11:16 ` David Engster

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=87zktuyebd.fsf@ericabrahamsen.net \
    --to=eric@ericabrahamsen.net \
    --cc=ding@gnus.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).