From: Ted Stern <stern@tera.com>
Subject: gnus-auto-select-next sometimes gets set to nil
Date: 05 Jan 2000 15:00:43 -0800 [thread overview]
Message-ID: <ycciu18qg2s.fsf@orff.sea.tera.com> (raw)
Occasionally while reading a group, I 'n' onto a message that has no contents.
Since I have debug-on-error set to true, I get debug output that the message
unexists. Sometimes, but not repeatably, this has the side effect of setting
gnus-auto-select-next to nil, which renders 'n' incapable of getting me to the
next newsgroup when I've finished reading the current one.
To my untrained (in elisp) eye, the likely culprit is in gnus-sum.el, in the
definition of gnus-summary-next-article:
(cond
((or (not gnus-auto-select-next)
(not cmd))
(gnus-message 7 "No more%s articles" (if unread " unread" "")))
((or (eq gnus-auto-select-next 'quietly)
(and (eq gnus-auto-select-next 'slightly-quietly)
push)
(and (eq gnus-auto-select-next 'almost-quietly)
(gnus-summary-last-article-p)))
The thing that bugs me is "push". Could that be the problem? Or is it a bug
in Emacs-20.3? I've tried getting my sysadmins to update to 20.5 but it is
delayed for the moment ...
--
Ted Stern Porting/Tuning/Analysis, Applications & Libraries
Tera Computer Company http://www.tera.com
411 First Avenue South, Suite 600 Direct 206/701-2182, Main 701-2000
Seattle, WA 98104-2860 Fax1 206/701-2205, Fax2 701-2500
next reply other threads:[~2000-01-05 23:00 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-01-05 23:00 Ted Stern [this message]
2000-04-21 14:15 ` Lars Magne Ingebrigtsen
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=ycciu18qg2s.fsf@orff.sea.tera.com \
--to=stern@tera.com \
/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).