From: Emanuel Berg via Users list for the GNU Emacs text editor <help-gnu-emacs@gnu.org>
To: help-gnu-emacs@gnu.org
Subject: Re: Let ispell use use multiple dictionaries stored in different files.
Date: Sat, 07 Aug 2021 17:54:24 +0200 [thread overview]
Message-ID: <874kc1i72n.fsf@zoho.eu> (raw)
In-Reply-To: CAGP6POKF6QcZpaLgyfCx=_vvpKD3fYoi3CHvgL8619LiRnKuvA@mail.gmail.com
Hongyi Zhao wrote:
> On Ubuntu 20.04, I noticed that ispell use the following
> file as its completion dictionary: "/usr/share/dict/words",
> which comes from wamerican package:
>
> $ apt-file search /usr/share/dict/words wamerican:
> /usr/share/dict/words
>
> But I want to know if ispell can use multiple dictionaries
> stored in different files for this purpose.
Install wamerican-insane - that should be the biggest ... then
just start type and spell, insert everything that is correct,
using the interface. It should be more than enough
pretty soon.
As for using multiple files, you can do a little Elisp loop
that iterates the dictionaries.
Another alternative is this, see this discussion of virtual
files on Linux:
https://unix.stackexchange.com/questions/94041/a-virtual-file-containing-the-concatenation-of-other-files
But I think it is overkill for this purpose (could be cool to
try tho), if I wanted to use several files, I'd just have
a simple script or Makefile that merged them into a new,
regular file, and then that's what I would use.
--
underground experts united
https://dataswamp.org/~incal
next prev parent reply other threads:[~2021-08-07 15:54 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-07 12:20 Let ispell use use multiple dictionaries stored in different files Hongyi Zhao
2021-08-07 12:41 ` Eli Zaretskii
2021-08-07 13:46 ` Hongyi Zhao
2021-08-07 14:03 ` Eli Zaretskii
2021-08-07 15:54 ` Emanuel Berg via Users list for the GNU Emacs text editor [this message]
2021-08-08 3:10 ` Hongyi Zhao
2021-08-08 3:35 ` Emanuel Berg via Users list for the GNU Emacs text editor
2021-08-08 4:03 ` Hongyi Zhao
2021-08-08 4:09 ` Emanuel Berg via Users list for the GNU Emacs text editor
2021-08-08 4:22 ` Hongyi Zhao
2021-08-08 3:58 ` Emanuel Berg via Users list for the GNU Emacs text editor
2021-08-08 4:16 ` Hongyi Zhao
2021-08-08 4:40 ` Emanuel Berg via Users list for the GNU Emacs text editor
2021-08-08 4:52 ` Hongyi Zhao
2021-08-08 4:58 ` Emanuel Berg via Users list for the GNU Emacs text editor
2021-08-08 5:08 ` Hongyi Zhao
2021-08-08 5:19 ` Hongyi Zhao
2021-08-08 6:53 ` Emanuel Berg via Users list for the GNU Emacs text editor
2021-08-08 7:14 ` Hongyi Zhao
2021-08-08 7:22 ` Emanuel Berg via Users list for the GNU Emacs text editor
2021-08-08 7:43 ` Hongyi Zhao
2021-08-08 7:51 ` Hongyi Zhao
2021-08-08 8:02 ` Emanuel Berg via Users list for the GNU Emacs text editor
2021-08-08 8:27 ` Hongyi Zhao
2021-08-08 8:37 ` Hongyi Zhao
2021-08-08 10:14 ` Emanuel Berg via Users list for the GNU Emacs text editor
2021-08-08 13:09 ` Hongyi Zhao
2021-08-08 16:27 ` Emanuel Berg via Users list for the GNU Emacs text editor
2021-08-09 0:06 ` Hongyi Zhao
2021-08-09 0:34 ` Emanuel Berg via Users list for the GNU Emacs text editor
2021-08-09 1:31 ` Hongyi Zhao
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=874kc1i72n.fsf@zoho.eu \
--to=help-gnu-emacs@gnu.org \
--cc=moasenwood@zoho.eu \
/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).