gnus-auto-select-next sometimes gets set to nil

gnus-auto-select-next sometimes gets set to nil

[Ted Stern]

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

Re: gnus-auto-select-next sometimes gets set to nil

[Lars Magne Ingebrigtsen]

Ted Stern <stern@tera.com> writes:

> 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.

That sounds like an error message from bbdb.  Do you use bbdb?

-- 
(domestic pets only, the antidote for overdose, milk.)
   larsi@gnus.org * Lars Magne Ingebrigtsen