0.56 major nnfolder bug?

0.56 major nnfolder bug?

[d. hall]

-----BEGIN PGP SIGNED MESSAGE-----

Okay at first I thought it was my setup, and now I'm beginning to wonder.
I've sent email to Lars, but I want to know if this bug can be
reconstructed.  It's potentially very dangerous since it clears (catchups)
all nnfolders as you select them.  I did a relatively clean gnus startup
with a min.el file.

Most of the changes had to do with file variables and the split methods.
What happens is when I select a nnfolder newsgroup, it basically does a
catchup.  Only once did I get it to select the nnfolder group correctly
(i.e. I selected a normal newsgroups and then went to select an nnfolder
one) but after that each consectutive call to open an nnfolder group did a
catchup.  Can anyone reproduce this?

Emacs-version:
GNU Emacs 19.30.1 (i486-slackware-linux, X toolkit) of Wed Nov 29 1995 on fuzzy

Gnus-version:
September Gnus v0.56; nnfolder 1.0

d.
- --[[application/octet-stream; type=emacs-lisp
Content-Disposition: attachment; filename="min.el"][7bit]]
(setq nnfolder-active-file		"~/.mailbox/.active"
      nnfolder-directory		"~/.mailbox/")
      
(setq nnmail-crash-box			"~/.mailbox/.crash"
      nnmail-message-id-cache-file	"~/.mailbox/.cache"
      nnmail-message-id-cache-length	 100
      nnmail-expiry-wait		'immediate
      nnmail-delete-incoming		 t
      nnmail-split-methods
      '(("folder.circle" "^X-Folder: circle")
	("folder.source" "^X-Folder: source")
	("folder.system" "^X-Folder: system")
	("folder.emacs"  "^X-Folder: emacs")
	("folder.inbox"	 "")))


-----BEGIN PGP SIGNATURE-----
Version: 2.6.2
Comment: Processed by Mailcrypt 3.4, an Emacs/PGP interface

iQCVAwUBMVNrzIX26urqpgG1AQFFwQQA2rAYJ1jTpohnxwSCHCbS2/3paCkXW6En
iVYfQSf43VplNNRrQ08klUTmJ4x0xb+Mmot8+bRArrVWVx1hQifoF38JmysaZXFl
l7CXtOU12L/pZbrEvPzuWudhFx7qvzrtne28bS6l64hJuvHK0LFE9eZYcEwPxcHM
s7VOzzlg3Vs=
=uoks
-----END PGP SIGNATURE-----
--
			``Our love is like water
			  Pinned down and abused
			     For being strange''

				~ live, all over you

Re: 0.56 major nnfolder bug?

[Hans de Graaff]

dhall@illusion.apk.net (d. hall) writes:

> What happens is when I select a nnfolder newsgroup, it basically
> does a catchup.  Only once did I get it to select the nnfolder group
> correctly (i.e. I selected a normal newsgroups and then went to
> select an nnfolder one) but after that each consectutive call to
> open an nnfolder group did a catchup.  Can anyone reproduce this?

Unfortunatly, yes. However, so far I've only seen this on one
folder. All the others work fine.

I've also noted lines in my active file like:

nil 0 1 y

I've checked, and in my case the articles are still in the folder, but
so far I haven't been able to get them back into Gnus.

Hans
-- 
Hans de Graaff                              J.J.deGraaff@TWI.TUDelft.NL
Delft University of Technology        Department of Information Systems
---- <a href="http://is.twi.tudelft.nl/~graaff/">Hans de Graaff</a> ---

Re: 0.56 major nnfolder bug?

[Jason Schroeder]

I have observed this catchup behaviour as well with my nnfolder groups.

Jason

   From: dhall@illusion.apk.net (d. hall)
   Date: 22 Mar 1996 22:11:27 -0500

   Okay at first I thought it was my setup, and now I'm beginning to wonder.
   I've sent email to Lars, but I want to know if this bug can be
   reconstructed.  It's potentially very dangerous since it clears (catchups)
   all nnfolders as you select them.  I did a relatively clean gnus startup
   with a min.el file.

   Most of the changes had to do with file variables and the split methods.
   What happens is when I select a nnfolder newsgroup, it basically does a
   catchup.  Only once did I get it to select the nnfolder group correctly
   (i.e. I selected a normal newsgroups and then went to select an nnfolder
   one) but after that each consectutive call to open an nnfolder group did a
   catchup.  Can anyone reproduce this?