From: Nevin Kapur <nevin@jhu.edu>
Subject: Problem with marking articles
Date: Sat, 04 Aug 2001 11:55:26 -0400 [thread overview]
Message-ID: <m3d76bddld.fsf@bombay.dyndns.org> (raw)
Latest Oort:
The first time I try to tick an article using u:
Signaling: (wrong-type-argument listp 9991)
car(9991)
(< (car cache-active) (car active))
(if (< (car cache-active) (car active)) (setcar active (car cache-active)))
(when (< (car cache-active) (car active)) (setcar active (car cache-active)))
(progn (when (< ... ...) (setcar active ...)) (when (> ... ...) (setcdr active ...)))
(if cache-active (progn (when ... ...) (when ... ...)))
(when cache-active (when (< ... ...) (setcar active ...)) (when (> ... ...) (setcdr active ...)))
(let ((cache-active ...)) (when cache-active (when ... ...) (when ... ...)))
(if gnus-cache-active-hashtb (let (...) (when cache-active ... ...)))
(when gnus-cache-active-hashtb (let (...) (when cache-active ... ...)))
gnus-cache-possibly-alter-active("nnml:ding" 9991)
gnus-cache-possibly-enter-article("nnml:ding" 9991 t nil nil)
gnus-summary-mark-article(nil ?! nil)
gnus-summary-mark-forward(1 ?!)
gnus-summary-tick-article-forward(1)
call-interactively(gnus-summary-tick-article-forward)
This seems to be the direct consequence of
2001-08-03 Simon Josefsson <jas@extundo.com>
* gnus-cache.el (gnus-cache-possibly-enter-article): The article
that is entered does not necessarily have the highest article
number in the group, so use `gnus-cache-possibly-alter-active'
instead of `gnus-cache-update-active'.
Also I am not seeing the '*' mark when I use 'u' the second time, even
though I have gnus-use-cache set to t.
--
Nevin
next reply other threads:[~2001-08-04 15:55 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-08-04 15:55 Nevin Kapur [this message]
2001-08-04 19:31 ` Simon Josefsson
2001-08-04 21:06 ` Nevin Kapur
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=m3d76bddld.fsf@bombay.dyndns.org \
--to=nevin@jhu.edu \
/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).