From: Lars Magne Ingebrigtsen <larsi@gnus.org>
Subject: Re: gnus-auto-select-next sometimes gets set to nil
Date: 21 Apr 2000 16:15:27 +0200 [thread overview]
Message-ID: <m3purjee0w.fsf@quimbies.gnus.org> (raw)
In-Reply-To: <ycciu18qg2s.fsf@orff.sea.tera.com>
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
prev parent reply other threads:[~2000-04-21 14:15 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-01-05 23:00 Ted Stern
2000-04-21 14:15 ` Lars Magne Ingebrigtsen [this message]
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=m3purjee0w.fsf@quimbies.gnus.org \
--to=larsi@gnus.org \
/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).