From: Dave Love <d.love@dl.ac.uk>
Subject: Re: tm
Date: 26 Aug 1998 19:19:34 +0100 [thread overview]
Message-ID: <rzqvhnfmwqx.fsf@djlvig.dl.ac.uk> (raw)
In-Reply-To: Steinar Bang's message of "Tue, 25 Aug 1998 09:30:26 GMT"
>>>>> "SB" == Steinar Bang <sb@metis.no> writes:
SB> TM doesn't work with 20.2 MBSK, because it assumes that GNU Emacs
SB> with major version > 19 always has MIME, and I was unable to make
SB> it belive otherwise.
Is there something wrong with the recipe to which I've previously
pointed here?
SB> Your approaches are:
SB> - start using XEmacs 20.4 (what I did for mail and news. I use 20.2
SB> for everything else)
SB> - go back to GNU Emacs 19.34
SB> - upgrade to 20.3 and live with MULE (which I haven't tested)
For TM I think you need something like the MBSK recipe in unibyte
mode.
- use RMIME (probably only unibyte but works fine, especially with
some minor hacking for comfort).
prev parent reply other threads:[~1998-08-26 18:19 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
1998-08-24 3:58 tm Phil Humpherys
1998-08-24 12:25 ` tm Karl Kleinpaste
1998-08-24 19:01 ` tm Phil Humpherys
[not found] ` <vxkr9y6qjr5.fsf@pocari-sweat.jprc.com>
1998-08-24 20:03 ` tm Phil Humpherys
1998-08-25 9:26 ` tm Steinar Bang
1998-08-26 18:19 ` Dave Love [this message]
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=rzqvhnfmwqx.fsf@djlvig.dl.ac.uk \
--to=d.love@dl.ac.uk \
/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).