From: Michael Welsh Duggan <md5i@cs.cmu.edu>
Subject: Re: MULE primer
Date: Mon, 31 Aug 1998 22:20:54 GMT [thread overview]
Message-ID: <v1taf4kyern.fsf@peoria.mt.cs.cmu.edu> (raw)
In-Reply-To: <m3btp0euuf.fsf@sparky.gnus.org>
Lars Magne Ingebrigtsen <larsi@gnus.org> writes:
> What is *the* way to learn about all this MULE stuff? I have a
> distinct feeling I must be misunderstanding something basic here. I
> mean, here's (日本語) some Japanese text, so I must be doing something
> right, but I still don't understand it.
Well, you must be doing something right, because I too can receive and
read the Japanese txt.
> And the XEmacs and Emacs MULEs are subtly and not-so-subtly
> different, in that the XEmacs stuff works and the Emacs stuff
> doesn't. (Well.)
Can you be more specific on what doesn't "work"?
> The Emacs 20.3 manual seems kinda slight on this subject... Is there
> a new Emacs Lisp manual out? Should I read the XEmacs Lisp manual?
Hmm... The prereaders version that Alan Shutko mentioned is still at:
etlport.etl.go.jp:/pub/mule/.notready/elisp.xtar.gz
--
Michael Duggan
(md5i@cs.cmu.edu)
.
next prev parent reply other threads:[~1998-08-31 22:20 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 [this message]
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
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=v1taf4kyern.fsf@peoria.mt.cs.cmu.edu \
--to=md5i@cs.cmu.edu \
/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).