From: Kai.Grossjohann@CS.Uni-Dortmund.DE (Kai Großjohann)
Subject: Re: message part must be split to 2 parts
Date: Fri, 19 Apr 2002 14:24:15 +0200 [thread overview]
Message-ID: <vafhem77u6o.fsf@lucy.cs.uni-dortmund.de> (raw)
In-Reply-To: <3CBFFB65.3060800@mail.suomi.net>
Juha Siltala <juha.siltala@mail.suomi.net> writes:
> No such functions when I try to get emacs to describe them. Or perhaps
> there's just no help for them? Darn. This is getting me into trouble
> on groups with vigorous netiquette police forces. Doing Mozilla now :(
Hm, err. unify-8859-on-encoding-mode is available in ucs-tables.el
which I think is not in Emacs 21.1 or 21.2. But Dave Love has posted
it to gnu.emacs.sources, or you can go to http://savannah.gnu.org and
use the CVS Web interface to fetch the file in question.
But maybe it is enough to use Oort without ucs-tables?
kai
--
Silence is foo!
next parent reply other threads:[~2002-04-19 12:24 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <m2d6wwn8ik.fsf@marvin.kotonet.net>
[not found] ` <vafzo00rdge.fsf@lucy.cs.uni-dortmund.de>
[not found] ` <3CBFFB65.3060800@mail.suomi.net>
2002-04-19 12:24 ` Kai Großjohann [this message]
2002-04-20 22:59 ` Juha Siltala
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=vafhem77u6o.fsf@lucy.cs.uni-dortmund.de \
--to=kai.grossjohann@cs.uni-dortmund.de \
/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).