Gnus development mailing list
 help / color / mirror / Atom feed
From: Eric Abrahamsen <eric@ericabrahamsen.net>
To: ding@gnus.org
Subject: Re: keeping killed groups out of gnus-group-jump-to-group
Date: Wed, 25 May 2011 00:43:25 -0400	[thread overview]
Message-ID: <87boyrcrv6.fsf@ericabrahamsen.net> (raw)
In-Reply-To: <87mxibd088.fsf@ericabrahamsen.net>

Eric Abrahamsen <eric@ericabrahamsen.net> writes:

> David Engster <deng@randomsample.de> writes:
>
>> Eric Abrahamsen writes:
>>> Very simply: I'm using a mairix server, and ido for all autocompletion.
>>> The mairix server includes a complete list of all my nnmail groups,
>>> killed, and they all show up when I hit 'j' to jump to a group, usually
>>> *before* the real nnmail group, which makes it hard to use. I don't know
>>> where the list of groups is created -- is there a way I can have it
>>> filter out killed groups?
>>
>> I don't know either. You could use an advice to at least filter the
>> nnmairix groups:
>>
>> (defadvice gnus-group-completing-read (before remove-nnmairix-groups activate)
>>   (unless collection
>>     (mapatoms
>>      (lambda (g)
>>        (unless (string-match nnmairix-group-prefix (symbol-name g))
>> 	 (push g collection)))
>>      gnus-active-hashtb)))
>>
>
> Thanks! I was definitely expecting to have to advise something…
>
> However, just putting this in my .gnus.el and evaluating it doesn't seem
> to do anything, do have to put it somewhere special?

Found the problem: =nnmairix-group-prefix= is the prefix of the
directory where mairix keeps its results, "zz_mairix" in my case, not
the prefix of the bogus mairix server groups, which is "nnml+mairix:".
Using a literal string instead of =nnmairix-group-prefix= made this
work.

Thanks again,
Eric




      reply	other threads:[~2011-05-25  4:43 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-05-23 20:11 Eric Abrahamsen
2011-05-24 13:51 ` David Engster
2011-05-25  1:42   ` Eric Abrahamsen
2011-05-25  4:43     ` Eric Abrahamsen [this message]

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=87boyrcrv6.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).