From: Hallvard B Furuseth <h.b.furuseth@usit.uio.no>
Subject: Re: MULE primer
Date: 01 Sep 1998 19:43:38 +0200 [thread overview]
Message-ID: <HBF.980901wev0@bombur2.uio.no> (raw)
In-Reply-To: Lars Magne Ingebrigtsen's message of "Tue, 01 Sep 1998 17:34:03 GMT"
Lars Magne Ingebrigtsen <larsi@gnus.org> writes:
> I don't think these are bugs -- they are just the result of Emacs'
> unibyte/multibyte model. XEmacs doesn't have that problem.
Well, it's at least a documentation problem, since you needed to ask.
--
Hallvard
next prev parent reply other threads:[~1998-09-01 17:43 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
1998-08-31 20:53 Lars Magne Ingebrigtsen
1998-08-31 21:14 ` Alan Shutko
1998-08-31 21:38 ` Hrvoje Niksic
1998-08-31 22:20 ` Michael Welsh Duggan
1998-09-01 1:10 ` Alan Shutko
1998-09-01 8:22 ` Lars Magne Ingebrigtsen
1998-09-01 16:13 ` Alan Shutko
1998-09-01 8:20 ` Lars Magne Ingebrigtsen
1998-09-01 13:13 ` Michael Welsh Duggan
1998-09-01 14:33 ` William M. Perry
1998-09-01 15:57 ` Lars Magne Ingebrigtsen
1998-09-01 17:43 ` Hallvard B Furuseth [this message]
1998-08-31 23:02 ` SL Baur
1998-09-01 8:46 ` Stephen J. Turnbull
1998-09-01 15:52 ` font suggestions for GNU Emacs? (was Re: MULE primer) John H Palmieri
1998-09-01 19:29 ` John H Palmieri
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=HBF.980901wev0@bombur2.uio.no \
--to=h.b.furuseth@usit.uio.no \
/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).