From: Ted Zlatanov <tzz@lifelogs.com>
To: info-gnus-english@gnu.org
Subject: Re: always need to run gnus twice
Date: Wed, 24 Mar 2010 15:22:54 -0500 [thread overview]
Message-ID: <87sk7p8o69.fsf@lifelogs.com> (raw)
In-Reply-To: <uepr2u3a3r.fsf@dsm.dsm.fordham.edu>
On Tue, 23 Mar 2010 19:13:28 -0400 Art Werschulz <agw@dsm.fordham.edu> wrote:
AW> Hi all.
AW> Using the following:
AW> (*) version 23.1.1 of emacs on two Linuxes (Fedora and Ubuntu) and on
AW> Mac OS X
AW> (*) eternal-september.org as my newsfeed
AW> gnus runs perfectly under Ubuntu and Mac OS X.
AW> However under Fedora 12, I need to run gnus twice. In other words, I
AW> fire up gnus, which tells me that there is no unread news. I then fire
AW> up gnus a second time, and then gnus finds the unread news articles.
AW> This problem only started happening when I moved from another news
AW> server to eternal-september.
AW> Any idea why this is happening? If so, how to fix.
I haven't seen this. It may be a byte compilation issue since you say
the Gnus code and Emacs are the same. Can you check the versions?
Ted
next prev parent reply other threads:[~2010-03-24 20:22 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-23 23:13 Art Werschulz
2010-03-24 20:22 ` Ted Zlatanov [this message]
2010-03-25 17:20 ` Art Werschulz
2010-03-30 13:31 ` Ted Zlatanov
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=87sk7p8o69.fsf@lifelogs.com \
--to=tzz@lifelogs.com \
--cc=info-gnus-english@gnu.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).