Angus Leeming wrote:
Paul A. Rubin wrote:
Edit | Preferences | Language settings | Spellchecker lists ispell as
the program, but it's grayed out and cannot be changed. I have aspell
(in C:\Aspell). I don't have ispell. On the other hand,
spell-checking somehow works ...
The *nix versions have two ways to invoke the spell checker:
1 Spawn a child process and communicate with it through its STDIN and
STDOUT streams.
2 Link against the Aspell library and communicate with it through the
libraries C-API.
Version 1, the external process, is not available to us on Windows
because the communication with pipes bit hasn't been inplemented. That's
why the Preferences thingie is greyed out: it's the name of the external
process and it's irrelevant.
And yet ... Ruurd's port has an active drop-down list with three choices
(ispell, aspell, hspell). Hence the confusion, at least for us
"old-timers".
... except for the bug, reported long ago for other versions, that
opening multiple documents and then spell-checking more than one of
them causes LyX to crash. Still.
Cool! Detailed HOWTO please.
Seems to be somewhat document-dependent, and may vary by astrological or
meteorological conditions. I'm attaching two files from one of my
classes. I can crash LyX using the following algorithm:
1. Open both docs (order seems immaterial).
2. Spell check one of them (again, does not seem to matter which) and
click "Ignore All" every time a word is flagged. (My spelling is
impeccable, so this is the appropriate response each time.)
3. Switch to the other document, position the cursor at the beginning,
and commence checking. The first time I click "Ignore All", LyX
disappears into bit oblivion.
I read you as saying on the lyx-users list that you're now a proud linux
user. Can you crash LyX 1.3.5 on linux?
I think you have me confused with someone with a similar name (and no
doubt not as good-looking). I do have a Linux server (currently not in
use and possibly no longer fully loaded), but I've never installed LyX
on it. The crash-on-spell-check problem has been discussed on the user
list, but I only recall posts from Windows users.
-- Paul
