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: Sun, 10 Mar 2024 10:06:50 +0200 [thread overview]
Message-ID: <86bk7mwlwl.fsf@gnu.org> (raw)
In-Reply-To: <86y1aqh70o.fsf@mail.linkov.net> (message from Juri Linkov on Sun, 10 Mar 2024 09:37:20 +0200)
> From: Juri Linkov <juri@linkov.net>
> Date: Sun, 10 Mar 2024 09:37:20 +0200
>
> When different projects have different personal dictionaries
> and flyspell mode is used, then ispell process is killed and restarted
> almost on every key press. This creates hundreds of hunspell processes
> that soon fill all available memory.
If the speller process is killed each time before starting a new one,
how come there's more than just one running at any given time? IOW,
how come you have "hundreds of hunspell processes" in memory? Does
killing a hunspell process fail for some reason?
And why are you saying "almost on every key press"? are different
personal dictionaries defined for different portions of text in some
way? Otherwise, I'd expect hunspell to be restarted when you change
buffers, whuch is hardly "on every key press". Or what am I missing?
> Is it possible to fix this?
Not easily, AFAIR. But I don't think I understand the nature of the
problem you are experiencing, see above.
next prev parent reply other threads:[~2024-03-10 8:06 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 [this message]
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
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=86bk7mwlwl.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).