Gnus development mailing list
 help / color / mirror / Atom feed
From: Fabrice Popineau <Fabrice.Popineau@supelec.fr>
Cc: ding@gnus.org
Subject: Re: coding-system conflicts ?
Date: Fri, 27 Sep 2002 16:45:43 +0200	[thread overview]
Message-ID: <1y7fqync.fsf@supelec.fr> (raw)
In-Reply-To: <u1kb7d90.fsf@hschmi22.userfqdn.rz-online.de> (Frank Schmitt's message of "Fri, 27 Sep 2002 15:50:35 +0200")

* Frank Schmitt <usereplyto@Frank-Schmitt.net> writes:

> XEmacs is broken in this aspect at the moment. (See my mail to the
> xemacs-beta list). Perhaps you want to drop a note there too?

Well, I'll do it. For the moment, it seems that (latin-unity-install)
is ok. Thanks for the hint. 

I need to investigate a bit deeper and ensure that nothing else
is wrong. I had problems with my XEmacs+Mule compiled with
optimization : many of the basic Mule functions were just broken. It
took me bit of time to sort this out

-- 
Fabrice





      reply	other threads:[~2002-09-27 14:45 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-09-27  8:15 Fabrice Popineau
2002-09-27 10:32 ` Kai Großjohann
2002-09-27 11:18   ` Daniel Pittman
2002-09-27 13:50 ` Frank Schmitt
2002-09-27 14:45   ` Fabrice Popineau [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=1y7fqync.fsf@supelec.fr \
    --to=fabrice.popineau@supelec.fr \
    --cc=ding@gnus.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).