Re: Trouble with nnir.el ("Invalid function ...")

[Sriram Karra <karra@shakti.homelinux.net.mapson>]

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.