From mboxrd@z Thu Jan 1 00:00:00 1970 X-Msuck: nntp://news.gmane.io/gmane.emacs.gnus.user/2787 Path: news.gmane.org!not-for-mail From: Sriram Karra Newsgroups: gmane.emacs.gnus.user Subject: Re: Trouble with nnir.el ("Invalid function ...") Date: Wed, 30 Jul 2003 22:58:34 +0530 Organization: The Klingon High Council Message-ID: References: <84znj7q8u0.fsf@lucy.is.informatik.uni-duisburg.de> <87adaxbozu.fsf@phiwumbda.localnet> <84k7a1xvx9.fsf@slowfox.is.informatik.uni-duisburg.de> <87y8yh5hbb.fsf@phiwumbda.localnet> <84zniw59nn.fsf@slowfox.is.informatik.uni-duisburg.de> NNTP-Posting-Host: main.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Trace: sea.gmane.org 1138669092 16355 80.91.229.2 (31 Jan 2006 00:58:12 GMT) X-Complaints-To: usenet@sea.gmane.org NNTP-Posting-Date: Tue, 31 Jan 2006 00:58:12 +0000 (UTC) Original-X-From: nobody Tue Jan 17 17:31:13 2006 Original-Path: quimby.gnus.org!newsfeed1.e.nsc.no!nsc.no!nextra.com!news.tele.dk!news.tele.dk!small.news.tele.dk!news.maxwell.syr.edu!sn-xit-03!sn-xit-01!sn-post-01!supernews.com!corp.supernews.com!not-for-mail Original-Newsgroups: gnu.emacs.gnus Mail-Copies-To: nobody X-Attribution: karra User-Agent: Gnus/5.1002 (Gnus v5.10.2) Emacs/21.2.95 (usg-unix-v) Cancel-Lock: sha1:o8pOQfrHedifNNe5iRs/4Y/DYU0= Cache-Post-Path: sj-nntpcache-5!unknown@desh.cisco.com X-Cache: nntpcache 2.4.0b2 (see http://www.nntpcache.org/) Original-X-Complaints-To: abuse@supernews.com Original-Xref: bridgekeeper.physik.uni-ulm.de gnus-emacs-gnus:2927 Original-Lines: 33 X-Gnus-Article-Number: 2927 Tue Jan 17 17:31:13 2006 Xref: news.gmane.org gmane.emacs.gnus.user:2787 Archived-At: Kai, Thanks for your help so far. kai.grossjohann@gmx.net (Kai Großjohann) writes: > jesseh@cs.kun.nl (Jesse F. Hughes) writes: > >> Anyway, it appears that the final clause of the case statement is >> tripped, and that novitem is never set. Is that helpful? > > So what's the value of foo at that point? I wonder if there is a > new value that has been introduced recently, or whether the symbols > have been renamed, or whether foo is nil... foo is nil. I think the fundamental problem is that nnir-artlist is not populated correctly. The reason the default in the case statement gets triggered is that nnir is looking in the wrong backend. Basically, I use nnfolder for my sent-mail and nnml for everything else. When the search results are in nnml backend, say "ucode" folde, nnir falsely tries to look in nnfolder+archive:ucode. So, looks like this problem will be there for anyone using multiple nnir backends. I do not know enough about nnir to provide a solution. But with your help, Kai, we can fix this problem/ Thanks, -Sriram. -- Well, all's well that ends.