From: Daiki Ueno <ueno@unixuser.org>
Cc: ding@gnus.org, Uwe Brauer <oub@mat.ucm.es>
Subject: Re: (\(de\|en\)code-coding-
Date: Thu, 30 Nov 2006 15:33:23 +1100 [thread overview]
Message-ID: <9a4033ba-9fa5-487f-9608-fd730bd95c49@well-done.deisui.org> (raw)
In-Reply-To: <b4m64cxiuev.fsf@jpl.org> (Katsumi Yamaoka's message of "Thu, 30 Nov 2006 10:40:24 +0900")
>>>>> In <b4m64cxiuev.fsf@jpl.org>
>>>>> Katsumi Yamaoka <yamaoka@jpl.org> wrote:
> > Is there any particular reason to compile non-Mule XEmacs without
> > file-coding? IIRC, at least Debian's xemacs21-nomule is compiled with
> > --without-mule --with-file-coding and there is encode-coding-region.
> I don't know, but Uwe Brauer seems to use the one that has
> neither mule nor file-coding. (I have three XEmacs 21.4.19 for
> testing.)
I mean, is there any distros which distribute non-Mule XEmacs without
file-coding? If so, I agree with that it's worth supporting it.
Otherwise I would recommend such a user to recompile with
--with-file-coding.
--
Daiki Ueno
next prev parent reply other threads:[~2006-11-30 4:33 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-29 23:52 (\(de\|en\)code-coding- Katsumi Yamaoka
2006-11-30 1:32 ` (\(de\|en\)code-coding- Daiki Ueno
2006-11-30 1:40 ` (\(de\|en\)code-coding- Katsumi Yamaoka
2006-11-30 4:33 ` Daiki Ueno [this message]
2006-11-30 4:56 ` (\(de\|en\)code-coding- Katsumi Yamaoka
2006-11-30 10:10 ` (\(de\|en\)code-coding- Uwe Brauer
2006-11-30 12:17 ` (\(de\|en\)code-coding- Daiki Ueno
2006-12-11 6:21 ` (\(de\|en\)code-coding- Daiki Ueno
2006-11-30 10:11 ` (\(de\|en\)code-coding- Uwe Brauer
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=9a4033ba-9fa5-487f-9608-fd730bd95c49@well-done.deisui.org \
--to=ueno@unixuser.org \
--cc=ding@gnus.org \
--cc=oub@mat.ucm.es \
/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).