Re: Unable to access nndraft:drafts in recent version of Gnus

[Lloyd Zusman <ljz@asfast.com>]

Matthias Wiehl <mwiehl@gmx.de> writes:

> Lloyd Zusman <ljz@asfast.com> writes:
> 
> > With the new CVS version, my "nndraft:drafts" group shows up with an
> > asterisk at its left and I cannot access it.  I cannot see any drafts
> > that go into that group.
> 
> You will have to byte-compile Gnus in order to make your drafts group
> work properly again.  Lars Magne Ingebrigtsen writes:
>
> [ ... ]

I found Lars' comments in my gnus mailing list archives before posting
my question to this group.  However, I always byte-compile everything,
and in the case of this problem, my gnus was also byte-compiled
properly.

It turns out that the problem has something to do with changing my
`load-path' to contain an entry that points to a newly downloaded
(from cvs) version of gnus that has indeed been byte-compiled, instead
of using the original `load-path' entry which points to the directory
path for the gnus version I had previously been using.  It appears
that now there is something in my normal `load-path' that gnus needs,
and when the version pointed to by the altered `load-path' is run,
this `nndrafts:drafts' problem occurs.  If I install the latest
version into my normal load path, the problem goes away.

I have been using this same method of switching `load-path' entries to
test downloads of gnus for the better part of a year, and this
`nndrafts:drafts' problem hadn't occurred at all until recently.

Once I stumbled upon this connection to `load-path', however, I
stopped looking for the real cause of the problem, since it only seems
to occur when testing.

Thanks for your suggestion, however.

Any ideas about how a `load-path' change could affect the ability for
gnus to recognize the `nndrafts:drafts' folder? ... especially given
that the only path component I change is the one which points to gnus
directory tree, which contains nothing at all but the byte-compiled
gnus release ... ???

-- 
 Lloyd Zusman
 ljz@asfast.com