From: Florian Weimer <fw@deneb.enyo.de>
Subject: Corrupted score files with ... symbols
Date: Mon, 23 Aug 2004 11:16:12 +0200 [thread overview]
Message-ID: <87657agqoz.fsf@deneb.enyo.de> (raw)
The patch below prevents Gnus from corrupting score files if
`print-level' is ever set to a non-nil value. This kind of score file
corruption results in the following error message:
gnus-score-load-score-alist: Wrong type argument: listp, \.\.\.
(The fix is to remove the `...' symbol from the score file. Some data
is lost.)
Okay to commit?
2004-08-23 Florian Weimer <fw@deneb.enyo.de>
* gnus-score.el (gnus-score-save): Bind `print-length' to nil, to
prevent truncation of scoring rules.
* score-mode.el (gnus-score-pretty-print): Likewise.
Index: gnus-score.el
===================================================================
RCS file: /usr/local/cvsroot/gnus/lisp/gnus-score.el,v
retrieving revision 7.12
diff -u -r7.12 gnus-score.el
--- gnus-score.el 20 May 2004 08:02:39 -0000 7.12
+++ gnus-score.el 23 Aug 2004 09:11:47 -0000
@@ -1387,6 +1387,7 @@
(defun gnus-score-save ()
;; Save all score information.
(let ((cache gnus-score-cache)
+ (print-length nil)
entry score file)
(save-excursion
(setq gnus-score-alist nil)
Index: score-mode.el
===================================================================
RCS file: /usr/local/cvsroot/gnus/lisp/score-mode.el,v
retrieving revision 7.2
diff -u -r7.2 score-mode.el
--- score-mode.el 20 May 2004 08:02:41 -0000 7.2
+++ score-mode.el 23 Aug 2004 09:11:55 -0000
@@ -93,7 +93,8 @@
(goto-char (point-min))
(let ((form (read (current-buffer))))
(erase-buffer)
- (let ((emacs-lisp-mode-syntax-table score-mode-syntax-table))
+ (let ((emacs-lisp-mode-syntax-table score-mode-syntax-table)
+ (print-length nil))
(pp form (current-buffer))))
(goto-char (point-min)))
next reply other threads:[~2004-08-23 9:16 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-23 9:16 Florian Weimer [this message]
2004-08-23 9:46 ` Katsumi Yamaoka
2004-08-23 11:08 ` Florian Weimer
2004-08-23 12:34 ` Katsumi Yamaoka
2004-08-24 6:55 ` Katsumi Yamaoka
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=87657agqoz.fsf@deneb.enyo.de \
--to=fw@deneb.enyo.de \
/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).