unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Lars Ingebrigtsen <larsi@gnus.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 19:22:27 +0300	[thread overview]
Message-ID: <83a7cyku2k.fsf@gnu.org> (raw)
In-Reply-To: <m3lfwi42ol.fsf@gnus.org> (message from Lars Ingebrigtsen on Sun,  28 Jul 2019 17:08:26 +0200)

> From: Lars Ingebrigtsen <larsi@gnus.org>
> Cc: olejorgenb@gmail.com,  24050@debbugs.gnu.org
> Date: Sun, 28 Jul 2019 17:08:26 +0200
> 
> 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?

If aspell/hunspell is misconfigured, or has some bug, it might not
output the correct list of installed dictionaries, or not at all.

> ispell.el itself doesn't look around for dictionaries -- it just calls
> aspell/hunspell and it outputs the dictionaries (see below).

Yes.

> If the backend is something other than aspell/hunspell, ispell will
> still output the entire list of built-in dictionary names.

Right.





  reply	other threads:[~2019-07-28 16:22 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
2019-07-28 16:22           ` Eli Zaretskii [this message]
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=83a7cyku2k.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=24050@debbugs.gnu.org \
    --cc=larsi@gnus.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).