--- Begin Message ---
Subject: |
26.1.91 M-x flyspell-mode |
Date: |
Fri, 01 Feb 2019 22:54:05 +0900 |
I cannot start flyspell-mode on GNU Emacs 26.1.91 (build 1, x86_64-w64-mingw32).
I can start flyspell-mode on GNU Emacs 26.1 (build 1, x86_64-w64-mingw32)
I wonder if this is something to do with 26.1.91.
CMD> c:/msys64/mingw64/bin/hunspell.exe --version
@(#) International Ispell Version 3.2.06 (but really Hunspell 1.6.2)
GNU Emacs 26.1.91 (build 1, x86_64-w64-mingw32)
CMD> runemacs -Q
M-: (with-eval-after-load "ispell"
(ispell-change-dictionary "en_US" t))
M-: (setq ispell-program-name "c:/msys64/mingw64/bin/hunspell.exe"
ispell-local-dictionary "en_US"
ispell-local-dictionary-alist
'(("en_US" "[[:alpha:]]" "[^[:alpha:]]" "[']" nil ("-d" "en_US") nil
utf-8)))
M-x flyspell-mode
Error enabling Flyspell mode:
(stringp nil)
--- End Message ---
--- Begin Message ---
Subject: |
Re: bug#34272: 26.1.91 M-x flyspell-mode |
Date: |
Mon, 11 Feb 2019 18:29:01 +0200 |
> Date: Mon, 11 Feb 2019 09:49:47 +0900 (JST)
> Cc: address@hidden, address@hidden,
> address@hidden
> From: Tak Kunihiro <address@hidden>
>
> > 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))
>
> Yes, the following block works and also `M-x flyspell' works!
Thanks, I installed this on the emacs-26 branch, and I'm marking this
bug done.
--- End Message ---