From: Norbert Koch <nk@viteno.net>
Subject: Re: Oort 0.17 brings many XEmacs cores
Date: Mon, 31 Mar 2003 22:23:14 +0200 [thread overview]
Message-ID: <vz4r5jl1zh.fsf@viteno.dyns.net> (raw)
In-Reply-To: <86u1dj4j7u.fsf@duchess.twilley.org> (Jack Twilley's message of "Mon, 31 Mar 2003 08:03:01 -0800")
Jack Twilley <jmt+usenet@twilley.org> writes:
Hi!
> That's for XEmacs. I haven't changed XEmacs in months, the only
> recent change I've made has been in gnus. I wanted to notify the
> gnus team about the new behavior -- I'll notify the XEmacs folks as
> per their website.
Sure, but if you encounter a core dump it's certainly an (X)Emacs
problem, since you can't have them on Lisp level. Only Gnus, the most
precious bug tracker ever written, opens the flood-gates to make the
bug show itself :-)
If you rilly wanted to report a Gnus bug, M-x gnus-bug and the
Lisp-backtrace sounds like a good start to me.
norbert.
prev parent reply other threads:[~2003-03-31 20:23 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-31 7:49 Jack Twilley
2003-03-31 8:04 ` Norbert Koch
2003-03-31 16:03 ` Jack Twilley
2003-03-31 20:23 ` Norbert Koch [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=vz4r5jl1zh.fsf@viteno.dyns.net \
--to=nk@viteno.net \
/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).