From: spamtrap@koldfront.dk (Adam Sjøgren)
Subject: Re: XEmacs support?
Date: Tue, 05 Aug 2003 17:02:27 +0200 [thread overview]
Message-ID: <87adaorvuk.fsf@virgil.koldfront.dk> (raw)
In-Reply-To: <u1xw0ci54.fsf@boost-consulting.com>
On Tue, 05 Aug 2003 10:07:35 -0400, David wrote:
> Does anyone use recent GNUs with XEmacs?
I'm using:
XEmacs 21.4 (patch 13) "Rational FORTRAN" [Lucid] (i386-debian-linux,
Mule) of Sun Jul 20 2003 on eeyore
without problems (from Debian/unstable). If it qualifies as recent, I
don't know.
On another box I'm using:
XEmacs 21.4 (patch 6) "Common Lisp" [Lucid] (i386-debian-linux, Mule)
of Sat Apr 6 2002 on eeyore
which is older (from Debian/stable, I think). Works fine there as
well.
Best regards,
--
"There followed a huge, unfocused debate about the Adam Sjøgren
profitability of the computer hardware industry." asjo@koldfront.dk
next prev parent reply other threads:[~2003-08-05 15:02 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-08-05 14:07 David Abrahams
2003-08-05 15:02 ` Adam Sjøgren [this message]
2003-08-05 15:42 ` Vasily Korytov
2003-08-05 16:02 ` David S Goldberg
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=87adaorvuk.fsf@virgil.koldfront.dk \
--to=spamtrap@koldfront.dk \
/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).