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: Tue, 30 Jul 2019 17:42:47 +0300 [thread overview]
Message-ID: <834l33k2hk.fsf@gnu.org> (raw)
In-Reply-To: <m336invkb9.fsf@gnus.org> (message from Lars Ingebrigtsen on Tue, 30 Jul 2019 13:22:18 +0200)
> From: Lars Ingebrigtsen <larsi@gnus.org>
> Cc: olejorgenb@gmail.com, 24050@debbugs.gnu.org
> Date: Tue, 30 Jul 2019 13:22:18 +0200
>
> > So all of this is ... complicated. And since the original complaint
> > is about the completion candidates shown by ispell-change-directory, I
> > think we should solve that problem by tweaking only the completion,
> > not the data structures it uses. If you agree, maybe you or someone
> > else could come up with an alternative patch which only modified how
> > the collection of completion candidates is calculated.
>
> A different option might be to use the current way of doing the
> completion candidates, but mark (for instance in bold) the ones that
> aspell/hunspell has said are available on the system.
Yes. Although that would be different from the way we display
completion candidates in other cases, and might require inline
explanation.
next prev parent reply other threads:[~2019-07-30 14:42 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
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 [this message]
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=834l33k2hk.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).