From: Frank Schmitt <usereplyto@Frank-Schmitt.net>
Subject: Re: coding-system conflicts ?
Date: Fri, 27 Sep 2002 15:50:35 +0200 [thread overview]
Message-ID: <u1kb7d90.fsf@hschmi22.userfqdn.rz-online.de> (raw)
In-Reply-To: <vg4rhmq4.fsf@supelec.fr>
Fabrice Popineau <Fabrice.Popineau@supelec.fr> writes:
> So what's wrong ? Should the reply buffer coding system be set to
> iso-8859-15 or is it xemacs which is wrongly guessing both -9 and -1
> (where I suspect -1 only would be ok) ?
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?
--
One Ring to rule them all, One Ring to find them,
One Ring to bring them all and in the darkness bind them
In the Land of Mordor where the Shadows lie.
next prev parent reply other threads:[~2002-09-27 13:50 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 [this message]
2002-09-27 14:45 ` Fabrice Popineau
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=u1kb7d90.fsf@hschmi22.userfqdn.rz-online.de \
--to=usereplyto@frank-schmitt.net \
--cc=replies@Frank-Schmitt.net \
/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).