From: Hongyi Zhao <hongyi.zhao@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: help-gnu-emacs <help-gnu-emacs@gnu.org>
Subject: Re: Let ispell use use multiple dictionaries stored in different files.
Date: Sat, 7 Aug 2021 21:46:20 +0800 [thread overview]
Message-ID: <CAGP6PO+-Ds7S7k3ALtav_z6ABkdiSnxoX58xWZFzs_5h6Exr4g@mail.gmail.com> (raw)
In-Reply-To: <834kc1ifzl.fsf@gnu.org>
On Sat, Aug 7, 2021 at 8:41 PM Eli Zaretskii <eliz@gnu.org> wrote:
>
> > From: Hongyi Zhao <hongyi.zhao@gmail.com>
> > Date: Sat, 7 Aug 2021 20:20:02 +0800
> >
> > 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.
>
> ispell-alternate-dictionary is a defcustom, so you can customized the
> value to point to any other file. But it must to be a single file.
Thank you for letting me know this restriction.
> Why do you need to use more than one file at once?
Say, use different files to store vocabulary of different disciplines.
> This file is not really used as a dictionary, it is used to complete words you type as
> replacements, or when you are looking for a word you cannot remember.
> It isn't a dictionary used by the speller for finding spelling
> mistakes.
Thank you for your explanation.
Regards
--
Assoc. Prof. Hongyi Zhao <hongyi.zhao@gmail.com>
Theory and Simulation of Materials
Hebei Vocational University of Technology and Engineering
No. 473, Quannan West Street, Xindu District, Xingtai, Hebei province
next prev parent reply other threads:[~2021-08-07 13:46 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 [this message]
2021-08-07 14:03 ` Eli Zaretskii
2021-08-07 15:54 ` Emanuel Berg via Users list for the GNU Emacs text editor
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=CAGP6PO+-Ds7S7k3ALtav_z6ABkdiSnxoX58xWZFzs_5h6Exr4g@mail.gmail.com \
--to=hongyi.zhao@gmail.com \
--cc=eliz@gnu.org \
--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).