From: "Robert D. Crawford" <rdc1x@comcast.net>
To: info-gnus-english@gnu.org
Subject: Note: read-only score file; entry discarded
Date: Sat, 25 Aug 2007 05:56:23 -0500 [thread overview]
Message-ID: <87lkbzopbc.fsf@comcast.net> (raw)
Using Gnus v5.11 on GNU Emacs 22.1.50.1 (i686-pc-linux-gnu) of
2007-08-02 on t40.
I am getting the above message and can't understand why. I am not
really sure when the message began but I realized it when I tried to
manually lower the score for a particular sender. I have checked the
permissions on each of the SCORE and ADAPT files and they are all
currently 666. I have within the last few months done a reinstall of
Debian so, thinking this might be an issue with users and groups I have
done a chown rdc.rdc on the SCORE and ADAPT files. All the score files
have the following lines:
(mark-and-expunge -1)
(read-only nil)
(adapt t)
and I have made sure that it is valid elisp as far as parens go.
I am not really sure where else to look. Any help would be
appreciated.
Thanks,
rdc
--
Robert D. Crawford rdc1x@comcast.net
So this is it. We're going to die.
reply other threads:[~2007-08-25 10:56 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=87lkbzopbc.fsf@comcast.net \
--to=rdc1x@comcast.net \
--cc=info-gnus-english@gnu.org \
/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).