From: Katsumi Yamaoka <yamaoka@jpl.org>
Subject: Re: Non-MULE XEmacsen
Date: Tue, 06 Jan 2004 12:20:57 +0900 [thread overview]
Message-ID: <b9y8yklhiee.fsf@jpl.org> (raw)
In-Reply-To: <m3y8sl3iey.fsf@defun.localdomain>
>>>>> In <m3y8sl3iey.fsf@defun.localdomain>
>>>>> Jesper Harder <harder@myrealbox.com> wrote:
> "Katsumi Yamaoka" <yamaoka@jpl.org> writes:
>> (gnus-xmas-define): Defun char-width for non-MULE XEmacsen.
> Thanks. By the way, is there an easy way [1] to discover which stuff
> isn't available in non-MULE XEmacs?
> I've always found it really annoying that you never know which
> function or variable might be unbound if XEmacs is compiled with some
> weird option (non-MULE especially).
> [1] Easier than compiling one.
Gnus developers should use 3GHz machine. ;-p
--
Katsumi Yamaoka <yamaoka@jpl.org>
prev parent reply other threads:[~2004-01-06 3:20 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <E1AdgPi-0001An-00@quimby.gnus.org>
2004-01-06 2:44 ` Non-MULE XEmacsen (was: CVS update of gnus/lisp (ChangeLog gnus-xmas.el)) Jesper Harder
2004-01-06 3:20 ` Katsumi Yamaoka [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=b9y8yklhiee.fsf@jpl.org \
--to=yamaoka@jpl.org \
/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).