From: Juri Linkov <juri@linkov.net>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 50775@debbugs.gnu.org, "積丹尼 Dan Jacobson" <jidanni@jidanni.org>
Subject: bug#50775: ispell help message times out before most people can read it
Date: Fri, 24 Sep 2021 18:39:03 +0300 [thread overview]
Message-ID: <87fstukoca.fsf@mail.linkov.net> (raw)
In-Reply-To: <83tuiarrv9.fsf@gnu.org> (Eli Zaretskii's message of "Fri, 24 Sep 2021 17:05:30 +0300")
>> EZ> For me, it times out in 5 sec, not one.
>>
>> In fact you're right!
>>
>> But it is way to short for many of us.
>
> It's a simple matter of increasing the timeout, since when the user
> touches any key, the help goes away.
I have another problem with ispell timeouts: oftentimes text contains
characters that mismatch the charsets used by ispell. Then ispell
waits 5 sec for every such character to display a useless error message.
I used such change to minimize the time spent looking at these messages:
diff --git a/lisp/textmodes/ispell.el b/lisp/textmodes/ispell.el
index b650ab3871..f940dad460 100644
--- a/lisp/textmodes/ispell.el
+++ b/lisp/textmodes/ispell.el
@@ -2723,7 +2723,7 @@ ispell-parse-output
((equal 0 (string-match "[\ra-zA-Z]" output))
(ding) ; error message from ispell!
(message "Ispell error: %s" output)
- (sit-for 5)
+ (sit-for 1)
nil)
(t ; need to process &, ?, and #'s
(let ((type (aref output 0)) ; &, ?, or #
--
next prev parent reply other threads:[~2021-09-24 15:39 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-24 13:13 bug#50775: ispell help message times out before most people can read it 積丹尼 Dan Jacobson
2021-09-24 13:40 ` Eli Zaretskii
2021-09-24 13:52 ` 積丹尼 Dan Jacobson
2021-09-24 14:05 ` Eli Zaretskii
2021-09-24 14:34 ` 積丹尼 Dan Jacobson
2021-09-24 15:39 ` Juri Linkov [this message]
2021-09-24 16:10 ` Eli Zaretskii
2021-09-25 18:57 ` Juri Linkov
2021-09-25 19:45 ` Eli Zaretskii
2021-09-25 2:26 ` Lars Ingebrigtsen
2021-09-25 18:17 ` Stefan Kangas
2021-09-25 18:52 ` Eli Zaretskii
2021-09-25 19:38 ` Stefan Kangas
2021-09-25 19:44 ` Juri Linkov
2021-09-25 19:48 ` Eli Zaretskii
2021-09-26 6:30 ` 積丹尼 Dan Jacobson
2021-09-26 6:59 ` Eli Zaretskii
2021-09-29 11:32 ` Stefan Kangas
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=87fstukoca.fsf@mail.linkov.net \
--to=juri@linkov.net \
--cc=50775@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=jidanni@jidanni.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.
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).