Gnus development mailing list
 help / color / mirror / Atom feed
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 12:32:35 +1100	[thread overview]
Message-ID: <94896bca-29ad-425b-83c5-3e767f0a928b@well-done.deisui.org> (raw)
In-Reply-To: <b4mr6vlu7xp.fsf@jpl.org>

>>>>> In <b4mr6vlu7xp.fsf@jpl.org> 
>>>>>	Katsumi Yamaoka <yamaoka@jpl.org> wrote:
> I found things that might cause an error in XEmacs with no Mule
> by performing

> egrep '\((de|en)code-coding-' *.el

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.

> in the Gnus source directory.  So, I fixed only nneething.el so
> as to use mm-decode-coding-string instead of decode-coding-string
> in both the trunk and the v5-10 branch.  But I didn't modify
> mml2015.el and the PGG modules since I don't know whether PGG
> and EasyPG support non-Mule XEmacs.

I think that it's ok to apply the same fix to mml2015.el but please
don't propagate such a change to pgg-*.el.
-- 
Daiki Ueno




  reply	other threads:[~2006-11-30  1:32 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 ` Daiki Ueno [this message]
2006-11-30  1:40   ` (\(de\|en\)code-coding- Katsumi Yamaoka
2006-11-30  4:33     ` (\(de\|en\)code-coding- Daiki Ueno
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=94896bca-29ad-425b-83c5-3e767f0a928b@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).