Re: flyspell bug

[Magnus Henoch <mange@freemail.hu>]

Stephen Eglen <S.J.Eglen@damtp.cam.ac.uk> writes:

> Having looked at ispell.el, I don't think they are inconsistent; I
> think the logic of ispell.el is that if ispell-program-name is
> "ispell", it just checks the output of ispell -v:
>
> $ ispell -v
> @(#) International Ispell Version 3.1.20 (but really Aspell 0.50.5)
>
> and that parenthetic comment triggers ispell-really-aspell to t.
>
> I suggest we just fix flyspell to always use the -l flag in this case,
> rather than "list".

I disagree.  I was the one who asked for the change from -l to list in
the first place, because it wouldn't work for me.  The situation seems
to be that your version of aspell installs a compatibility "ispell"
command which supports the -l option meaning "list", while my version
of aspell (0.60.2) doesn't install any such alias and only understands
"list" when invoked as aspell.  (-l specifies the language to use)

So it seems that the variable ispell-really-aspell is moderately
useful, as there are three situations: ispell, aspell in ispell
compatibility mode, and "real" aspell.

The following patch eliminates the middle case.  The documentation of
aspell 0.50.5 claims that it supports the "list" command, but I
haven't tested it.

--- orig/lisp/textmodes/ispell.el
+++ mod/lisp/textmodes/ispell.el
@@ -301,7 +301,8 @@
   :type 'integer
   :group 'ispell)
 
-(defcustom ispell-program-name "ispell"
+(defcustom ispell-program-name (or (executable-find "aspell")
+				   "ispell")
   "Program invoked by \\[ispell-word] and \\[ispell-region] commands."
   :type 'string
   :group 'ispell)

Magnus