From: Eli Zaretskii <eliz@gnu.org>
To: Tak Kunihiro <tkk@misasa.okayama-u.ac.jp>
Cc: homeros.misasa@gmail.com, 34272@debbugs.gnu.org
Subject: bug#34272: 26.1.91 M-x flyspell-mode
Date: Sat, 09 Feb 2019 12:24:07 +0200 [thread overview]
Message-ID: <83imxtnttk.fsf@gnu.org> (raw)
In-Reply-To: <20190209.184831.1254873787557625236.tkk@misasa.okayama-u.ac.jp> (message from Tak Kunihiro on Sat, 09 Feb 2019 18:48:31 +0900 (JST))
> Date: Sat, 09 Feb 2019 18:48:31 +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>
>
> I think that I found issue. In my environment, `ispell-call-process'
> returns empty string with `null-device'.
That's strange. What is the value of null-device on your system?
> * With `null-device'
>
> (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)) ; => ""
Did you make sure ispell-program-name is set to "hunspell" when you
evaluated the above form? Its default value is something else.
next prev parent reply other threads:[~2019-02-09 10:24 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-01 13:54 bug#34272: 26.1.91 M-x flyspell-mode Tak Kunihiro
2019-02-01 15:04 ` Eli Zaretskii
2019-02-01 23:03 ` Tak Kunihiro
2019-02-02 7:07 ` Eli Zaretskii
2019-02-08 7:27 ` Eli Zaretskii
2019-02-08 11:30 ` Tak Kunihiro
2019-02-09 9:18 ` Eli Zaretskii
2019-02-09 9:48 ` Tak Kunihiro
2019-02-09 10:24 ` Eli Zaretskii [this message]
2019-02-09 10:39 ` Tak Kunihiro
2019-02-10 15:35 ` Eli Zaretskii
2019-02-11 0:49 ` Tak Kunihiro
2019-02-11 16:29 ` Eli Zaretskii
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=83imxtnttk.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=34272@debbugs.gnu.org \
--cc=homeros.misasa@gmail.com \
--cc=tkk@misasa.okayama-u.ac.jp \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.