torbjok@ifi.uio.no (Torbjørn Køhler) writes:

> I've been unable to create and use a nnkiboze group with gnus 5.6.4.
> I create the group with "G k", groupname "banana.banana", group regexp
> "gnu.emacs.gnus", match on header "subject", match "haha"
> 
> then the group pops up in the group buffer.  I press "g" to update,
> and it contains 0 messages. i quit gnus and start it again, and start
> it again and the last message i see is 
> "Loading ~/News/kiboze/nnkiboze:banana.banana.newsrc...done"
> 
> then nothing happens except emacs is using 99% of the cpu without me
> being able to notice anything happening.  i'm eventually able to break
> gnus with C-g, but i have to manually edit .newsrc.eld and remove
> banana.banana from it to be able to start gnus again.
> 
> If i run nnkiboze-generate-groups after i've created it, it says it
> contains several messages, but i'm unable to select the group to read
> any og them.

I've been floundering around with nnkiboze for days and have yet to get
anything useful from it.  I've concluded, without further coding, it is
basically useless and can do harm.  Some of this is documented in my
postings to this group recently.

Have you noticed how after running a kiboze search, the groups searched
have all ticked articles unticked [and thereby uncached] and show up as
unread, so that the number of unread showing is how ever many are on the
server.

And of course any ticked articles that were older than the servers
expirey are history, if you are running with caching set to 't'.  I lost
quite a few older articles that way.  Nnkiboze should come with a danger
sign on it.


-- 

Harry Putnam  reader@newsguy.com