From: Russ Allbery <rra@stanford.edu>
Subject: Additional info on XEmacs 21.4.6 crashes
Date: Thu, 27 Dec 2001 14:51:18 -0800 [thread overview]
Message-ID: <yl4rmcnuop.fsf@windlord.stanford.edu> (raw)
Vin Shelton queried the xemacs-beta list about the intermittant crashes
that I was reporting with Oort and XEmacs 21.4.6, and Stephen Turnbull
replied with this. I figured I'd forward it back here so that it gets
into the mailing list archives for anyone doing a search.
(I have to admit that the documentation of internals in Gnus has bothered
me in the past as well; the user manual is excellent, but if one has to
dig beneath that it's often pretty hard to figure out what's going on.)
--
Russ Allbery (rra@stanford.edu) <http://www.eyrie.org/~eagle/>
To: Vin Shelton <acs@alumni.princeton.edu>
Cc: xemacs-beta@xemacs.org
Subject: Re: [Russ Allbery <rra@stanford.edu>] Anyone using Oort with XEmacs 21.4.6?
From: "Stephen J. Turnbull" <stephen@xemacs.org>
Date: 27 Dec 2001 11:55:33 +0900
>>>>> "vin" == Vin Shelton <acs@alumni.princeton.edu> writes:
vin> Has anyone here seen problems like this? I'm not running
vin> oort, so I don't see this.
This happens in all recent Gnus, I'm not sure what the real cause is,
it's definitely a bug in XEmacs, and you can work around by telling
Gnus not to byte compile on the fly.
I forget how this is done, though, and as is typical in Gnus the
documentation of `gnus-compile' is, er, minimal.
--
Institute of Policy and Planning Sciences http://turnbull.sk.tsukuba.ac.jp
University of Tsukuba Tennodai 1-1-1 Tsukuba 305-8573 JAPAN
Don't ask how you can "do" free software business;
ask what your business can "do for" free software.
reply other threads:[~2001-12-27 22:51 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=yl4rmcnuop.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).