From: Didier Verna <verna@inf.enst.fr>
Cc: Gnus Beta Testers <ding@gnus.org>
Subject: Re: enable-multibyte-characters
Date: 28 Jun 1999 15:26:16 +0200 [thread overview]
Message-ID: <qyjlnd4zcav.fsf@metheny.enst.fr> (raw)
In-Reply-To: wmperry@aventail.com's message of "28 Jun 1999 07:47:39 -0500"
wmperry@aventail.com (William M. Perry) writes:
> > Footnotes:
> > [1] Steve, this is a good example of why it's really bad to have this
> > meaningless variable in XEmacs.
>
> Agreed. :)
So, I guess the best workaround would be for mule-sysdp.el NOT to
touch this variable at all when running XEmacs. OK ? ;-)
--
/ / _ _ Didier Verna http://www.inf.enst.fr/~verna/
- / / - / / /_/ / ENST, INFRES C201.1 mailto:verna@inf.enst.fr
/_/ / /_/ / /__ / 46 rue Barrault Tel. +33 (1) 45 81 73 46
75013 Paris, France Fax. +33 (1) 45 81 31 19
next prev parent reply other threads:[~1999-06-28 13:26 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-06-28 8:46 enable-multibyte-characters Didier Verna
1999-06-28 12:47 ` enable-multibyte-characters William M. Perry
1999-06-28 13:26 ` Didier Verna [this message]
1999-06-29 21:39 ` enable-multibyte-characters William M. Perry
1999-07-01 7:56 ` enable-multibyte-characters Didier Verna
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=qyjlnd4zcav.fsf@metheny.enst.fr \
--to=verna@inf.enst.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).