Re: [h-e-w] cygwin ispell and emacs 21.1

[Underwood, Jonathan]

Hi

Having done a bit more tracing it seems the problem lies in the fact that i
was purposefully not putting the directory containing the cygwin dll in my
PATH system variable (according to cygwin wisdom, it;s not a good idea to do
this generally), but relying upon ispell.el to run ispell via a
non-interactive shell command eg. bash -c ispell <file> and having an
initialization file set up the path for bash correctly. However ispell.el
just lunges at the ispell executeable (found via my exec-path emacs
variable). This seems somewhat inconsistent to me since, eg. compile
commands are all launched via a non-intereactive shell. Unless i'm missing
something, for consistency, ispell.el should launch ispell via a
non-interactive shell also.

Any thoughts?

jonathan.

> -----Original Message-----
> From: Underwood, Jonathan [mailto:address@hidden
> Sent: December 4, 2001 11:47 PM
> To: 'address@hidden'
> Subject: [h-e-w] cygwin ispell and emacs 21.1
> 
> 
> Hi
> 
> I'm currently running emacs 21.1 under windows 2000 and am 
> having trouble
> running ispell from within emacs. I am using ispell compiled 
> and running
> under cygwin. When run thru' emacs, i get the error message 
> "ispell exited
> with code 128". I have checked that ispell works correctly 
> under a terminal
> window (bash -c ispell), and all is well. There's nothing 
> unusual about my
> cygwin setup within .emacs:
> 
>   (if (boundp 'w32-quote-process-args)
>       (setq w32-quote-process-args ?\"))
>   (setq shell-file-name "bash")
>   (setenv "SHELL" shell-file-name) 
>   (setq explicit-shell-file-name shell-file-name) 
>   (setq shell-command-switch "-c")
>   (setq explicit-bash-args '("--login" "-i"))
> 
> setting the environment variable DICTIONARY to something 
> sensible didn't
> help matters at all. Any suggestions anyone? Is error code 
> 128 significant?
> 
> Thanks,
> 
> jonathan.
>