From: Eli Zaretskii <eliz@gnu.org>
To: Juri Linkov <juri@linkov.net>
Cc: 69703@debbugs.gnu.org
Subject: bug#69703: Ispell process restarted too often
Date: Tue, 12 Mar 2024 16:44:26 +0200 [thread overview]
Message-ID: <86le6ntsqd.fsf@gnu.org> (raw)
In-Reply-To: <867ci7rj05.fsf@mail.linkov.net> (message from Juri Linkov on Tue, 12 Mar 2024 09:45:14 +0200)
> From: Juri Linkov <juri@linkov.net>
> Cc: 69703@debbugs.gnu.org
> Date: Tue, 12 Mar 2024 09:45:14 +0200
>
> >> The nature of the problem is the inability of ispell.el to maintain
> >> multiple processes with different dictionaries simultaneously
> >> that is required by flyspell-mode.
> >>
> >> What is needed here is a hash of processes where the key is
> >> the ispell program name and its dictionary arguments.
> >
> > Feel free to submit patches for that, and thanks. (But didn't you
> > just complain about one speller process per buffer?)
>
> Since implementing this is not urgent, here is a design outline
> for possible future improvements:
>
> 1. Create a pool of Ispell processes.
>
> 2. Instead of killing Ispell processes
> just get the process from the pool
> by the ispell program name and its dictionary arguments.
This assumes that the number of different personal dictionaries is
much smaller than the number of buffers under flyspell-mode. Since I
don't quite understand why you need so many personal dictionaries
(presumably for the same language?), I cannot say whether this
assumption is reasonable or scalable. In general, if we want to
support buffer-local speller processes, we could have hundreds of
speller processes running on the system, which is not very nice, I
think.
The current design is generally based on the following assumptions:
. a speller process is mostly needed in a single buffer at a time,
the buffer where the user is typing
. a speller process needs to be restarted only if you change the
dictionary, which is done when you need to spell-check a different
language
. the number of languages for which the user needs spell-checking is
small (or even spell-checked by a single speller, if that is
Hunspell)
next prev parent reply other threads:[~2024-03-12 14:44 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-10 7:37 bug#69703: Ispell process restarted too often Juri Linkov
2024-03-10 8:06 ` Eli Zaretskii
2024-03-10 17:10 ` Juri Linkov
2024-03-10 17:51 ` Eli Zaretskii
2024-03-12 7:45 ` Juri Linkov
2024-03-12 14:44 ` Eli Zaretskii [this message]
2024-03-12 17:30 ` Juri Linkov
2024-03-14 17:50 ` Juri Linkov
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=86le6ntsqd.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=69703@debbugs.gnu.org \
--cc=juri@linkov.net \
/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).