From: Lloyd Zusman <ljz@asfast.com>
Subject: Unable to access nndraft:drafts in recent version of Gnus
Date: 16 Sep 2000 18:30:13 -0400 [thread overview]
Message-ID: <ltg0n0ezre.fsf@asfast.com> (raw)
I've been using a three-or-four-week-old CVS release of Gnus 5.8.8,
and recently I decided to bring myself up to date with the latest CVS
release. But once I installed it, all of the sudden, my
"nndraft:drafts" group ceased to work.
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.
However, if I revert back to my older Gnus 5.8.8, my "nndraft:drafts"
group works again. Also, if I use the latest CVS version to create
drafts, I can then exit Gnus and restart the three-or-four-week-old
version, and I then see my drafts in "nndraft:drafts". But if I don't
exit the newest version, the drafts I create don't appear and the
"nndraft:drafts" group remains inaccessible with the asterisk next to
it.
I didn't change anything at all about my configuration. The only
change I make is to switch between the newest CVS version and my
three-to-four-week-old version.
The only drafts-related variable that I have set within my `gnus.el'
file is ...
(setq nndraft-directory "~/News/drafts/")
... and this variable has been set literally for years and has caused
no problems for me during that time.
Any ideas?
Thanks in advance.
--
Lloyd Zusman
ljz@asfast.com
next reply other threads:[~2000-09-16 22:30 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-09-16 22:30 Lloyd Zusman [this message]
2000-10-01 12:18 ` Matthias Wiehl
2000-10-01 23:37 ` Lloyd Zusman
2000-10-02 10:23 ` Kai Großjohann
2000-10-02 22:23 ` Lloyd Zusman
2000-10-03 13:47 ` Kai Großjohann
2000-10-04 3:32 ` Solved! (Was: Unable to access nndraft:drafts in recent version of Gnus) Lloyd Zusman
2000-10-18 14:46 ` Unable to access nndraft:drafts in recent version of Gnus Jari Aalto+mail.emacs
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=ltg0n0ezre.fsf@asfast.com \
--to=ljz@asfast.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).