From: Russ Allbery <rra@stanford.edu>
Subject: Re: Nearly impossible to start up recent Oort.
Date: Fri, 08 Feb 2002 17:40:42 -0800 [thread overview]
Message-ID: <yln0yj8mat.fsf@windlord.stanford.edu> (raw)
In-Reply-To: <2npu3gimzy.fsf@zsh.cs.rochester.edu> (ShengHuo ZHU's message of "Fri, 08 Feb 2002 00:03:13 -0500")
ShengHuo ZHU <zsh@cs.rochester.edu> writes:
> You can get around the problem with (setq gnus-use-byte-compile nil).
> If it works, probably there is a bug in the XEmacs byte-compile code.
A much better workaround that appears to be equally effective is to add:
;; Work around a bug in XEmacs 21.4 with the latest version of Gnus. Loading
;; of byte-optimize when mail splitting starts can cause XEmacs to segfault.
(require 'byte-optimize)
to your .gnus or equivalent thereof.
--
Russ Allbery (rra@stanford.edu) <http://www.eyrie.org/~eagle/>
next prev parent reply other threads:[~2002-02-09 1:40 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-02-08 4:37 Lloyd Zusman
2002-02-08 5:03 ` ShengHuo ZHU
2002-02-08 13:10 ` Lloyd Zusman
2002-02-08 19:12 ` ShengHuo ZHU
2002-02-08 20:03 ` Karl Kleinpaste
2002-02-09 1:41 ` Russ Allbery
2002-02-09 2:58 ` Len Blanks
2002-02-09 10:27 ` Vincent Bernat
2002-02-09 1:40 ` Russ Allbery [this message]
2002-02-09 5:16 ` Lloyd Zusman
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=yln0yj8mat.fsf@windlord.stanford.edu \
--to=rra@stanford.edu \
/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).