Subj : Re: Editor problem with M
To   : MAX CHAMBERLAIN
From : William McBrine
Date : Sat Feb 14 2004 11:57 pm

-=> MAX CHAMBERLAIN wrote to WILLIAM MCBRINE <=-

 MC> It was probably overkill, but I changed every instance of the LFN to 
 MC> 'progra~1'

You mean, in the mmail.rc?

 MC> and now the editor in the DOS version 0.46 performs like 0.37.

Hmm. That shouldn't have helped, actually. :-) I was trying to say that if
you did that, it would just be expanded back to "Program Files" internally;
and _that's_ the path that would then be passed to the editor. (That's what
I meant about "what it _resolves_ to".) But maybe I was confusing the
behavior of the DOS and Win32 versions... I'll check on that later.

 MC> There is one other thing I would like to change.  Right now when I'm in
 MC> OLXed (either v0.37 or 0.46) the background is black and the lines of
 MC> text are white.

That's strictly an OLXed matter. MultiMail has nothing to do with it.

I've seen this before, with SLME (essentially the same program as OLXed).  
Although it can work as a standalone editor, it's really designed to work
in tandem with its reader. So, when OLX calls OLXed (or SLMR calls SLME),
it passes some extra info to the editor -- header info, as well as colors.  
Alas, the colors for OLXed/SLME can't be set independently -- they can only
be set in the OLX/SLMR config; and the editor doesn't seem to read the
config on its own.

MultiMail only passes the filename to the editor it calls. Unlike OLX/SLMR,
it's NOT designed specifically to work with OLXed/SLME, so it has no
conception of how to pass the extra info. I don't either. :-) I could look
it up... but this isn't something that's going into MultiMail as a feature.

It might be possible to write a wrapper batch file to pass the appropriate
parameters.

.... Time flies like an arrow, but fruit flies like a banana.
--- MultiMail/Linux v0.46
 * Origin: COMM Port OS/2 juge.com 204.89.247.1 (281) 980-9671 (1:106/2000)

.