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

Harry G McGavran Jr <[email protected]>
Newsgroups gmane.mail.exmh.user
Message-ID <[email protected]>
------- 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: Sun, 10 Apr 2011 21:01:59 -0600
Sender: [email protected]


I spent a long time trying to figure out why
sedit->more->spell behaved wierdly and never got
any results to sedit for me.  Maybe I just missed
this somewhere in the documentation, but I spent
a long time searching on the web and reading exmh documentation.

I found nothing really helpful about what *seditSpell:
and *spellCmd: really did, what they required in order
to work and how they interacted.  And then there is
the send problem with values in xhost when tcl is comiled 
without -DTK_NO_SECURITY which IS documented on the web
at least and in the exmh documentation to some extent.
That only aggravates trying to solve this problem,
especially if one is a C programmer who knows little
about tcl/tk.  So, I hope what I've gleaned is REASONABLY
CLOSE to what the truth is about the problem, at least
in the April 2011 time frame...

When I upgraded my Ubuntu from Hardy to Lucid, the
sedit->more->spell behavior was so wierd it was
noticeable that something was wrong.

The only thing I could find about the problem was something
in the exmh e-mail list archives from Reg posted in 
November of 2009.  So I sent him what I found and I've
forwarded it to this list. 

Hopefully it will save someone from spending a long searching
for an answer.

- ------- 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
Mime-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: quoted-printable
Date: Sun, 10 Apr 2011 20:21:56 -0600
Sender: [email protected]


Hi Reg --

I found your request (below) for information on the web
and after days of searching in exmh documentation
and on the web, I found nothing else about this problem.
I finally looked at seditExtras.tcl and seditSel.tcl
and while I'm no tcl/tk wiz, was finally able to
determine why sedit->more->spell is so wierd.

In exmh-defaults:

    *seditSpell:
         must be one of:
                 ispell
                 custom
                 <some spell command>

         if ispell is chosen, sedit will run
         whatever is specified in *spellCmd:
         and that must be prefixed by
         exmh-async as two temp files are created
         in /tmp/$USER with a name whose only difference
         is the pid of the process, so there must be
         TWO such processes for it to work.  One
         temp file is a wish script that will be passed
         to wish after executing *spellCmd: whose output
         will go into the other temp file. That wish script
         will take the output temp file and pass it
         via the script to wish for the sedit window.
         That script can't run asynchronously as noted
         in a comment in the tcl file as a requirement.
         The user has no way of controlling the commands
         in that script.

         If custom is chosen, sedit will run
         whatever is specified in *spellCmd: and
         pass the standard output and standard error
         of that program to the error reporting region
         of the sedit window.  If you have specified
         something like ispell for *spellCmd:, then
         you will end up making spelling corrections,
         and nothing will happen in the sedit window
         except the error reproting region of the sedit
         window will have whatever ispell put out in
         standard error.  The temp file ispell used
         and where it made the corrections is just
         thrown away.  It's clear that what was
         expected here was a listing on standard output
         of spelling errors, they would then appear
         in the error reporting region of the sedit window.

         If <some spell command> is specified, it is run
         and whatever is in *spellCmd: is ignored.  The
         standard output and standard error of <some spell
         command> will appear in the error reporting region
         of the sedit window.

And then there is the issue that exmh-async and wish require
that xhosts have no entries UNLESS wish (tcl) is compiled with
- - -DTK_NO_SECURITY.  So, those with Ubuntu lucid and later
must build their own tcl/tk and have the Ubuntu wish and tcl
point to that instead of the packages that Ubuntu supplies,
because the Ubuntu packages:

	1) Are not build the -DTK_NO_SECURITY

	2) Must have SI:localuser:$USER, SI:localauser:gdm,
	   and SI:localuser:root as xhost values in order
           to run.  They seem not to use .Xauthority.

Therefore if one chooses "custom" or "ispell" above, his exmh
under Ubuntu simply will not do spellchecks under sedit's more menu.

I couldn't find any exmh documentation on this, or web searches
didn't reveal anything either.  Doesn't anyone use sedit->more->spell????

=======================================================================


On Sun, 29 Nov 2009 09:39:29 +0100 Emile CARCAMO<ecarcamo.free.fr> wrote:

>> Well, the Subject line says it all, I have gone from 32bit/Fedora6
>> to a 64bit/Fedora11, and I have most things working.
>>
>> One of the things that ISNT working, and one that I dont understand,
>> os that SPELL CHECKING in EXMH has stopped working.  As far as I can
>> tell, all of EXMH was out on /usr/local, which means the new OS is
>> mounting exactly what I saw under Fc6, and I see spell, ispell and
>> aspell all in /usr/bin, so that hasnt changed.  And spell checking
>> is turned on in the EXMH Preferences.
>>
>> Is there some way to get EXMH to tell me what its doing, and why
>> its not doing spell checking,-  I really need spell checking...
>> --
>>                                         Reg.Clemens
>>                                         reg dwf com
>>
>
>Hi Reg,
>
>	I'm running exmh 2.7.2 01/07/2005 on Fedora12 install. All the
>	specific exmh stuff goes under /usr/local/exmh/{lib,bin}. BTW,
>	french spellchecking is working fine for me !! Here's my setup
>	and which RPMs that are required IMHO :
>
><satp20832.wifi>[Bemile=]<112>uname -a
>Linux satp20832.wifi 2.6.31.5-127.fc12.i686 #1 SMP Sat Nov 7 21:41:45 
EST 2009 i686 i686 i386 GNU/Linux
><satp20832.wifi>[emile=]<113>grep -i spell .exmh/exmh-defaults
>*seditSpell:	spell
>*spellCmd:	exmh-async xterm -e ispell
>*ispellOnOff:	1
>*ispellRecheckAfterAdd:	1
>*ispellTextOnly:	1
>*ispellCommand:	ispell -a -d french
>*ispellOthers:	Spanish  { ispell -a -d spanish }  French { ispell -a -d francais } English { ispell -a -d english }
>*ispellPopupBinding:	ButtonPress-3
>*ispellStyle:	other
>*ispellStyleColor:	red
>*ispellStyleOther:	-underline t -foreground red
>*spellCmd:	exmh-async xterm -e ispell
><satp20832.wifi>[emile]<114>rpm -qa | grep -i spell | sort
>aspell-0.60.6-7.fc12.i686
>aspell-fr-0.50-14.fc12.i686
>gtkspell-2.0.15-2.fc12.i686
>hunspell-1.2.8-12.fc12.i686
>hunspell-devel-1.2.8-12.fc12.i686
>hunspell-en-0.20090216-7.fc12.noarch
>hunspell-fr-3.4-1.fc12.noarch
><satp20832.wifi>[emile]<115>which ispell
>/usr/bin/ispell
><satp20832.wifi>[emile]<116>
>
>	Hope that will help you for sure. With best regards,
>
>-Emile
>

- - --

Harry G. McGavran, Jr.

E-mail: [email protected]




- ------- End of Forwarded Message


- -- 

Harry G. McGavran, Jr.

E-mail: [email protected]




------- End of Forwarded Message


-- 

Harry G. McGavran, Jr.

E-mail: [email protected]
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.