From: Wes Hardaker <hardaker@ece.ucdavis.edu>
Cc: ding@ifi.uio.no
Subject: bug fix? in sgnus 0.18 and xemacs 19.13 (possibly others)
Date: Tue, 05 Dec 1995 13:05:03 -0800 [thread overview]
Message-ID: <199512052105.AA162687504@chroma.ece.ucdavis.edu> (raw)
I'm not really sure why no one else has complained about this...
Every time I quiet gnus (starting with version 0.16 or so) I get errors
like:
wrong type argument: number-or-marker-p, (4 . 1)
and it dies in gnus-gnus-to-newsrc-format. Specifically, most groups
have gnus-newsrc-alist entries that look something like:
("alt.sources" 4 ((1 . 5667)) nil nil nil)
But a few of mine have entries like:
("gnu.emacs.sources" (4 . 1) ((1 . 3657))
Which is where the problem lies. Its the (4 . 1) list entry that is
killing it. I'm not sure what the second number in that list is, but
I'm assuming the first is the level (the desired feed to the ">"
statement). So, I hacked a fix, which works: (Though not being a
elisp or gnus expert, I'm sure there is probably another reason for my
problem in the first place...)
***************
*** 14820,14828 ****
;; Don't write foreign groups to .newsrc.
(progn
(insert (gnus-info-group info)
! (if (> (let ((infolevel (nth 1 info)))
! (if (listp infolevel) (car infolevel)
! infolevel)) gnus-level-subscribed)
"!" ":"))
(if (setq ranges (gnus-info-read info))
(progn
--- 14820,14826 ----
;; Don't write foreign groups to .newsrc.
(progn
(insert (gnus-info-group info)
! (if (> (nth 1 info) gnus-level-subscribed)
"!" ":"))
(if (setq ranges (gnus-info-read info))
(progn
As an aside, why do topics take so long to fold/unfold? I'm talking
like 5 seconds or so to do either operation?
_____
Wes Hardaker / ___ \
Department of Electrical and Computer Engineering / / \//\
University of California at Davis __________________ \--/ /--\
Davis CA 95616 / Recycle! \ \//\___/ /
(hardaker@ece.ucdavis.edu) / It's not too late! \ \_____/
reply other threads:[~1995-12-05 21:05 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=199512052105.AA162687504@chroma.ece.ucdavis.edu \
--to=hardaker@ece.ucdavis.edu \
--cc=ding@ifi.uio.no \
/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).