From: Raymond Scholz <ray-2001@zonix.de>
Subject: Limiting, catching up and undo behaviour
Date: Sun, 28 Oct 2001 15:52:44 +0100 [thread overview]
Message-ID: <lgd.87pu77u88z.fsf@mde1.zonix.de> (raw)
Hi!
Catching up articles after limiting the summary (`/ t') used to catch
up _all_ unread articles of that group regardless of visible or not.
I've now upgraded to Emacs 21 and now only visible articles are
catched up. The doc string says:
,----
| c runs the command gnus-summary-catchup-and-exit
| which is an interactive compiled Lisp function in `gnus-sum'.
| (gnus-summary-catchup-and-exit &optional ALL QUIETLY)
|
| Mark all unread articles in this group as read, then exit.
| If prefix argument ALL is non-nil, all articles are marked as read.
| If QUIETLY is non-nil, no questions will be asked.
`----
Why did that behaviour change?
Maybe this is related:
After catching up I say `C-_' in the group buffer and for every second
try Gnus produces the following backtrace:
,----
| Debugger entered--Lisp error: (void-variable group)
| (gnus-request-set-mark group (list (list ... ... ...)))
| (progn (gnus-info-set-marks (quote ...) (quote ...) t) (gnus-info-set-read (quote ...) (quote ...)) (gnus-get-unread-articles-in-group (quote ...) (gnus-active "de.comm.infosystems.www.authoring.misc")) (gnus-request-set-mark group (list ...)) (gnus-group-update-group "de.comm.infosystems.www.authoring.misc" t))
| (lambda nil (progn (gnus-info-set-marks ... ... t) (gnus-info-set-read ... ...) (gnus-get-unread-articles-in-group ... ...) (gnus-request-set-mark group ...) (gnus-group-update-group "de.comm.infosystems.www.authoring.misc" t)))()
| gnus-undo(1)
| call-interactively(gnus-undo)
`----
Cheers, Ray
--
WYSIWYG is a step backwards. Human labor is used to do that which the
computer can do better. (Andrew S. Tanenbaum)
next reply other threads:[~2001-10-28 14:52 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-10-28 14:52 Raymond Scholz [this message]
2001-10-29 20:22 ` Simon Josefsson
2001-10-29 21:47 ` Raymond Scholz
2001-11-01 21:20 ` Raymond Scholz
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=lgd.87pu77u88z.fsf@mde1.zonix.de \
--to=ray-2001@zonix.de \
--cc=rscholz@zonix.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).