all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Lars Ingebrigtsen <larsi@gnus.org>
To: Dave Abrahams <dabrahams@apple.com>
Cc: 25070@debbugs.gnu.org
Subject: bug#25070: nnir-ignored-newsgroups seems to have no effect for `A T'
Date: Fri, 27 Sep 2019 00:56:24 +0200	[thread overview]
Message-ID: <875zlefyzr.fsf@gnus.org> (raw)
In-Reply-To: <m2shq9vb8x.fsf@apple.com> (Dave Abrahams's message of "Tue, 29 Nov 2016 20:32:14 -0800")

Dave Abrahams <dabrahams@apple.com> writes:

> I have gnus-refer-thread-use-nnir set to t and nnir-ignored-newsgroups
> is "nnimap\\+LocalIMAP:committee\\|nnimap\\+LocalIMAP:\\[Gmail\\]/Spam",
> but when I do `A T' from my Inbox, I see the message
>
>   Searching nnimap+LocalIMAP:committee...
>
> which newsgroup name is definitely matched by the regexp.  I've designed
> the regexp that way because the newsgroup is huge and I don't want to
> wait for it to be searched.  So is there anything I can do about this?

I'm not very familiar with nnir, but I've been trying to follow the
logic of nnir-ignored-newsgroups, and I suspect it's not used in the
code path that `A T' uses.

Could you (setq debug-on-message "committee") to get a backtrace when it
outputs that message so that I can see what the call sequence is?

-- 
(domestic pets only, the antidote for overdose, milk.)
   bloggy blog: http://lars.ingebrigtsen.no





       reply	other threads:[~2019-09-26 22:56 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <m2shq9vb8x.fsf@apple.com>
2019-09-26 22:56 ` Lars Ingebrigtsen [this message]
2019-09-26 23:55   ` bug#25070: nnir-ignored-newsgroups seems to have no effect for `A T' Dave Abrahams via Bug reports for GNU Emacs, the Swiss army knife of text editors
2019-09-27 14:22     ` Lars Ingebrigtsen

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=875zlefyzr.fsf@gnus.org \
    --to=larsi@gnus.org \
    --cc=25070@debbugs.gnu.org \
    --cc=dabrahams@apple.com \
    /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.
Code repositories for project(s) associated with this external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.