emacs-diffs
[Top][All Lists]
Advanced

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

[Emacs-diffs] emacs-26 3aaa2d2: Fix Hunspell invocation for discovering


From: Eli Zaretskii
Subject: [Emacs-diffs] emacs-26 3aaa2d2: Fix Hunspell invocation for discovering its dictionaries
Date: Mon, 11 Feb 2019 11:08:56 -0500 (EST)

branch: emacs-26
commit 3aaa2d2058125a755bd6226cb4009811089812f8
Author: Eli Zaretskii <address@hidden>
Commit: Eli Zaretskii <address@hidden>

    Fix Hunspell invocation for discovering its dictionaries
    
    * lisp/textmodes/ispell.el
    (ispell-find-hunspell-dictionaries): Invoke Hunspell with the
    -a switch, to prevent it from initializing its curses UI.
    (Bug#34272)
---
 lisp/textmodes/ispell.el | 9 ++++++++-
 1 file changed, 8 insertions(+), 1 deletion(-)

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 @@ dictionary from that list was found."
                                 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]