mailing-list for TeXmacs Users

[David Allouche <address@hidden>]

On Wed, Nov 06, 2002 at 07:28:20PM +0100, Philipp Hartmann wrote:
> I had the same problems. This is due to a lacking parameter '-latin1' in
> the call of the ispell checker.
> 
> Therefore I wrote  a simple script as a quick'n'dirty workaround:
> 
> #!/bin/bash
> TEXMACSBINARY=/usr/bin/texmacs
> ISPELLBINARY=/usr/bin/ispell
> 
> #Workaround for some languages
> #'adds' the switch '-latin1' to the ispell process invoked by TeXmacs
> alias ispell=$ISPELLBINARY -latin1
> 
> if test -x $TEXMACSBINARY; then
>     echo Launching $TEXMACSBINARY $*...
>     $TEXMACSBINARY $*
> else
>    echo $TEXMACSBINARY not found or not executable.
> fi
> exit $?

That is VERY suprising, since your does nothing but lanch texmacs as usual.

The point is that 'alias' is a shell-level feature and is not passed
to children processes.

Demonstration:

    david@nemesis david$ alias foo="echo"
    david@nemesis david$ foo bar
    bar
    david@nemesis david$ bash
    david@nemesis david$ foo bar
    bash: foo: command not found
    david@nemesis david$ exit
    david@nemesis david$ foo bar
    bar
    david@nemesis david$ 

In your shellscript, replacing

    alias ispell=$ISPELLBINARY -latin1

with

    alias ispell="foobar"

does not prevent ispell from running.

So that explains why your script 'works' here even though -latin1 is
obviously not a supported option of ispell on my system.

Are you sure that spell checking works differently when starting
TeXmacs using your script and when starting it in the normal way?

-- 
David Allouche         | GNU TeXmacs -- Writing is a pleasure
Free software engineer |    http://www.texmacs.org
   http://ddaa.net     |    http://alqua.com/tmresources
   address@hidden  |    address@hidden
TeXmacs is NOT a LaTeX front-end and is unrelated to emacs.