From: Kyaw <jeckferson@gmail.com>
To: help-gnu-emacs@gnu.org
Subject: According to Emacs manual, "Aspell, Ispell or Hunspell" integrate automatically with Emacs, it doesn't with Hunspell
Date: Mon, 19 Feb 2018 18:50:11 +0630 [thread overview]
Message-ID: <CAL65Fyb3hus-u98hTzF9jMmbZ9Jn2Ht0R9Fmx5CqNrP1MfARtg@mail.gmail.com> (raw)
My Emacs work fine with Aspell but not with Hunspell. I installed Hunspell
and Hunspell-en_US in Arch Linux. Hunspell works fine with LibreOffice and
Firefox. Emacs doesn't detect Hunspell.
How do I make Emacs recognize Hunspell. I'm somewhat new to Emacs. I'm
reading "Learning GNU/Emacs" for now. The book also describes Hunspell will
work fine with Emacs automatically.
I check Emacs Wiki. It say so too.
next reply other threads:[~2018-02-19 12:20 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-19 12:20 Kyaw [this message]
2018-02-19 13:22 ` According to Emacs manual, "Aspell, Ispell or Hunspell" integrate automatically with Emacs, it doesn't with Hunspell Kyaw
2018-02-19 15:41 ` Eli Zaretskii
-- strict thread matches above, loose matches on Subject: below --
2018-02-23 16:23 Kyaw
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAL65Fyb3hus-u98hTzF9jMmbZ9Jn2Ht0R9Fmx5CqNrP1MfARtg@mail.gmail.com \
--to=jeckferson@gmail.com \
--cc=help-gnu-emacs@gnu.org \
/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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).