*growl* nnfolder cont.

*growl* nnfolder cont.

[d. hall]

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

I know I'm not familiar with this, cause backtracing is a pain.  The only
reason I see for the forced catchup is that (buffer-size) is eval'ing to 0,
and when I just went through gnus-summary-prepare, there wasn't anything to
prepare (so the problem is before that).  Lars, the ChangeLog says you
fixed the NOV which might truncate by a few (I think less than 5), but I'm
getting nnfolder groups of 25+ getting truncated to 0.  I'll have to
backtrack even further.

btw: I found an autosaving error (i.e. just now while composing this
message)  Gnus seems to want to place the outgoing mail autosave file into
the current-directory, well if that directory isn't writable, I get this
annoying autosave message.  Can Gnus places this either into either

	1. nnfolder-directory (if we're using that)
	2. nnmail-tmp-directory
	3. gnus-article-save-directory

(This is probably due to that fact that I set gnus-use-draft to nil, and
Gnus is no longer handling my auto-saves).

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

iQCVAwUBMVTbtoX26urqpgG1AQH4lgQAqnVJbc2ErdMCP2Qpapjtk52x97SZt1m6
8EULYqHy2zg13qXD4CLzD+T0iTNjAfDqUEsl0Z9WPZNZKZHrcGModOPCYLjIkufG
SSdueO3lsBmi/Z4uSn5jzwEchCtJheZB9me7zmGQLcT1jTMZOFFiItMOt05LON4V
dgRqIlCVjno=
=nfZZ
-----END PGP SIGNATURE-----