From: Lars Ingebrigtsen <larsi@gnus.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 24050@debbugs.gnu.org, olejorgenb@gmail.com
Subject: bug#24050: 24.5; ispell-change-dictionary suggests non-existent dicts (aspell)
Date: Sun, 28 Jul 2019 17:08:26 +0200 [thread overview]
Message-ID: <m3lfwi42ol.fsf@gnus.org> (raw)
In-Reply-To: <83d0hukya1.fsf@gnu.org> (Eli Zaretskii's message of "Sun, 28 Jul 2019 17:51:34 +0300")
Eli Zaretskii <eliz@gnu.org> writes:
> You assume that a dictionary not in the list doesn't exist; but that
> isn't a given. I've heard enough reports from users who for some
> reason or other bumped into situations where ispell.el couldn't figure
> out correctly what dictionaries are installed. The standard list
> (which is also customizable) leaves a "fire escape" for those cases.
OK, so aspell/hunspell won't output the real list of dictionaries it has
access to, but find more later when you give them a dictionary name?
ispell.el itself doesn't look around for dictionaries -- it just calls
aspell/hunspell and it outputs the dictionaries (see below).
If the backend is something other than aspell/hunspell, ispell will
still output the entire list of built-in dictionary names.
$ aspell dicts
en
en-variant_0
en-variant_1
en-variant_2
en-w_accents
en-wo_accents
en_AU
en_AU-variant_0
en_AU-variant_1
en_AU-w_accents
en_AU-wo_accents
en_CA
[...]
--
(domestic pets only, the antidote for overdose, milk.)
bloggy blog: http://lars.ingebrigtsen.no
next prev parent reply other threads:[~2019-07-28 15:08 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-21 19:49 bug#24050: 24.5; ispell-change-dictionary suggests non-existent dicts (aspell) Ole Jørgen Brønner
2019-07-28 10:25 ` Lars Ingebrigtsen
2019-07-28 14:17 ` Eli Zaretskii
2019-07-28 14:25 ` Lars Ingebrigtsen
2019-07-28 14:51 ` Eli Zaretskii
2019-07-28 15:08 ` Lars Ingebrigtsen [this message]
2019-07-28 16:22 ` Eli Zaretskii
2019-07-29 11:12 ` Lars Ingebrigtsen
2019-07-29 15:06 ` Eli Zaretskii
2019-07-30 11:22 ` Lars Ingebrigtsen
2019-07-30 14:42 ` Eli Zaretskii
2019-07-29 14:32 ` Agustin Martin
2022-02-21 16:01 ` Lars Ingebrigtsen
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=m3lfwi42ol.fsf@gnus.org \
--to=larsi@gnus.org \
--cc=24050@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=olejorgenb@gmail.com \
/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 public inbox
https://git.savannah.gnu.org/cgit/emacs.git
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).