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

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

 WM> You mean, in the mmail.rc?

Yes.

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

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

I understood what you meant.  I wasn't expecting a good result by
changing from the LFN, but decided to try it anyway since the effort
was trivial.  Was pleasantly surprised when it worked.

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

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

That's what I figured.  I looked at the value that OLX had in its
Editor field to make sure I used the same value in MMail.  Turns
out that OLX calls TagLine eXpress (TLX) which in turn executes
OLXed to create the message.  After the message is saved, control
returns to TLX to handle the tagline process.  There are some
parameters passed from OLX to TLX which I presume includes color
info that TLX makes available to OLXed.

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

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

I'm know there are many text editor apps available on the web.
Perhaps if I really want to get away from black and white I
should look for one that provides color options.

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

Do you mean it might be possible for me to write the batch file?
I don't think so.    Thanks for the clarification on this
issue.

    TTYL, Max    

---
 þ OLX-TD þ To be, or not to be, those are the parameters.
 
--- MultiMail/MS-DOS v0.46