16 Mar 19:34
Re: no mime support?
From: Bill Wohler <wohler <at> newt.com>
Subject: Re: no mime support?
Newsgroups: gmane.mail.mh-e.user
Date: 2008-03-16 18:34:20 GMT
Subject: Re: no mime support?
Newsgroups: gmane.mail.mh-e.user
Date: 2008-03-16 18:34:20 GMT
Greg Minshall <minshall <at> acm.org> wrote: > thanks for the reply. You're welcome. We're delighted to have you aboard. > i'm running emacs built from source to use X > rather than whatever Quartz-macos thing: OK... > ---- > MH-E 8.0 > > MH-E compilation details: > Byte compiled: yes > Gnus (compile-time): Gnus v5.9.0 > Gnus (run-time): Gnus v5.13 Looks like you're compiling MH-E with the default (old) version of Emacs on your system. Probably emacs21. Strange things can happen when there's a mismatch between your Gnus runtime and compile-times (which is why we ended up putting this info in mh-version. From the README: ** Compile. ... If you run Emacs by any name other than `emacs', use the following instead: cd mh-e-8.0.3 make EMACS=myemacs For example, Mac users might have to use something like: make EMACS=/Applications/DarwinPorts/Emacs.app/Contents/MacOS/Emacs However, since you're compiling you're own, it sounds like you might want to try "make EMACS=emacs23" or something... On the other hand, both emacs22 and emacs23 contain the latest version of MH-E, so it might be easiest to just take your local version of MH-E out of your load path (until I have a chance to put out version 8.1). > it isn't ';'!
thanks for pointing that out. (i'm moving from > Brent Welch's exmh, and getting used to mh-e -- which i really like -- i > akin to 10 years ago switching from 15 years of vi to emacs; i.e., > difficult!) Then the manual is just for you
. While we put a lot of work into the online help (?, C-h m, etc.), there's a lot of stuff in MH that is harder to stumble across. Do skim the manual at http://mh-e.sf.net/manual/ > the example i gave (from spam) had the weird windows font. but, other > examples don't. actually, below is a spam that should display > either ascii or html (again, spam). This example was truncated--it ended with: > ---- instead of a MIME boundary. Cut and paste error, or a bug in your .procmailrc script? I replaced it with ------=_NextPart_000_0007_01C886FD.7C28DDC0-- and the message showed up fine for me using both emacs22 -Q and emacs23 -Q. For fun, I truncated that line again, and MH-E still did the right thing
. Trying getting your compile- and run-time Gnus versions to match and I think you'll be in better shape. -- -- Bill Wohler <wohler <at> newt.com> http://www.newt.com/wohler/ GnuPG ID:610BD9AD ------------------------------------------------------------------------- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
. From the README:
** Compile.
...
If you run Emacs by any name other than `emacs', use the following
instead:
cd mh-e-8.0.3
make EMACS=myemacs
For example, Mac users might have to use something like:
make EMACS=/Applications/DarwinPorts/Emacs.app/Contents/MacOS/Emacs
However, since you're compiling you're own, it sounds like you might
want to try "make EMACS=emacs23" or something...
On the other hand, both emacs22 and emacs23 contain the latest version
of MH-E, so it might be easiest to just take your local version of MH-E
out of your load path (until I have a chance to put out version 8.1).
> it isn't ';'!
thanks for pointing that out. (i'm moving from
> Brent Welch's exmh, and getting used to mh-e -- which i really like -- i
> akin to 10 years ago switching from 15 years of vi to emacs; i.e.,
> difficult!)
Then the manual is just for you
RSS Feed