Re: Went to 64bit/Fc11, EXMH no longer spellchecking (fwd)

------- Forwarded Message

X-Mailer: exmh version 2.7.2 01/07/2005 (debian 1:2.7.2-18) with nmh-1.3
To: [email protected]
From: Harry G McGavran Jr <[email protected]>
Reply-to: [email protected]
Subject: Re: Went to 64bit/Fc11, EXMH no longer spellchecking (fwd)
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date: Mon, 11 Apr 2011 09:30:35 -0600
Sender: [email protected]


I should point out a few things about *seditSpell:

"ispell" and "custom" are keywords, not programs or paths.
Anything else, like "ispell -x" or "xterm -e ispell"
or "xterm -e ispell -x" are NOT keywords, but are
<some spell command>, a program or path to a program.

So just looking at what one has in his exmh-defaults,
if he has ispell, it is a keyword and is
not the ispell program.

Some users here having seen "ispell" as the
value for *seditSpell:  have replaced 
ispell with xterm -e ispell,
and the result is that the process described in my previous
e-mail for <some spell command> is followed.

That results in the stdout and stderr of xterm being
put in the error reporting region of the sedit window
(usually an empty space because if ispell has done
its job there is nothing put out on stdout or stderr)
and the changes ispell has made to the temp file passed
to it are IGNORED because no wish script is used
to send the changes to the sedit window for text
processing.  That only happens if the ispell KEYWORD
is used and then the *spellCMD is used which may or
may not be ispell depending upon what the user puts
as the value for *spellCMD AND exmh-async must be
used so there isn't a temp file collision.

In my opinion "ispell" is a really bad choice for
a keyword, particularly becuase it is the name
of the program commonly used for this.
Using uppercase for keywords would have been better.

Anyway, the "ispell" keyword is for getting
the changed tempfile contents merged into the
sedit message content IF exmh-async was used,
and "custom" is for ignoring such changes and
just putting the stdout and stderr in the
error reporting region of the sedit window.

I'm not sure of good names for these, but 
to me "ispell" isn't one of them.

    Harry



- -- 

Harry G. McGavran, Jr.

E-mail: [email protected]




------- End of Forwarded Message


-- 

Harry G. McGavran, Jr.

E-mail: [email protected]