Gnus development mailing list
 help / color / mirror / Atom feed
From: Phil Shapiro <pshapiro@curl.com>
Subject: gnus 5.10.6 and fedora core 3 -> doesn't work?
Date: Thu, 18 Nov 2004 19:34:48 +0000 (UTC)	[thread overview]
Message-ID: <loom.20041118T201908-473@post.gmane.org> (raw)

I've been using gnus 5.10 under Redhat's Fedora Core 2, gnu emacs 21.3.1, and
everything worked fine.  The other day I upgraded to Fedora Core 3 and found
that gnus 5.10 no longer works.  5.9 appears to work OK.  I have the same
version (rpm) of emacs installed on both FC2 and FC3 boxes.

Here's what happens when it fails.

- start emacs, and then start gnus using M-x gnus RET
- read the first email message using RET
- hit 'r' to reply, and then emacs hangs
- hit C-g to un-hang emacs
- in *Messages* it says:
Generating summary...done
while: Quit
Fontifying *reply to xxx@zzz.com*... (regexps...........)
Quit

Any ideas?  The FC3 setup is pretty much a stock installation.

Thanks.

-phil




                 reply	other threads:[~2004-11-18 19:34 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=loom.20041118T201908-473@post.gmane.org \
    --to=pshapiro@curl.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).