bug-gnu-emacs
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

bug#34272: 26.1.91 M-x flyspell-mode


From: Eli Zaretskii
Subject: bug#34272: 26.1.91 M-x flyspell-mode
Date: Sun, 10 Feb 2019 17:35:50 +0200

> Date: Sat, 09 Feb 2019 19:39:17 +0900 (JST)
> Cc: homeros.misasa@gmail.com, 34272@debbugs.gnu.org,
>  tkk@misasa.okayama-u.ac.jp
> From: Tak Kunihiro <tkk@misasa.okayama-u.ac.jp>
> 
> (setq ispell-program-name "c:/msys64/mingw64/bin/hunspell.exe")
> 
> (with-temp-buffer
>   (ispell-call-process ispell-program-name
>                                      null-device
>                                      t
>                                      nil
>                        ;; Hunspell 1.7.0 (and later?) won't
>                        ;; show LOADED DICTIONARY unless
>                        ;; there's at least one file argument
>                        ;; on the command line.  So we feed
>                        ;; it with the null device.
>                                      "-D" null-device)
>   (buffer-string))                      ; => ""

Does the patch below help?

diff --git a/lisp/textmodes/ispell.el b/lisp/textmodes/ispell.el
index 656c9fa..237997d 100644
--- a/lisp/textmodes/ispell.el
+++ b/lisp/textmodes/ispell.el
@@ -1114,12 +1114,19 @@ ispell-find-hunspell-dictionaries
                                 null-device
                                 t
                                 nil
+                                 "-D"
+                                 ;; Use -a to prevent Hunspell from
+                                 ;; trying to initialize its
+                                 ;; curses/termcap UI, which causes it
+                                 ;; to crash or fail to start in some
+                                 ;; MS-Windows ports.
+                                 "-a"
                                  ;; Hunspell 1.7.0 (and later?) won't
                                  ;; show LOADED DICTIONARY unless
                                  ;; there's at least one file argument
                                  ;; on the command line.  So we feed
                                  ;; it with the null device.
-                                "-D" null-device)
+                                null-device)
            (buffer-string))
          "[\n\r]+"
          t))





reply via email to

[Prev in Thread] Current Thread [Next in Thread]