all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: "Tomasz Hołubowicz via Bug reports for GNU Emacs, the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
To: Eshel Yaron <me@eshelyaron.com>, Eli Zaretskii <eliz@gnu.org>
Cc: 74437@debbugs.gnu.org
Subject: bug#74437: 30.0.92; completion-preview-idle-delay is delayed by flyspell
Date: Sat, 23 Nov 2024 22:41:00 +0100	[thread overview]
Message-ID: <871pz14oib.fsf@alternateved.com> (raw)
In-Reply-To: <m1jzcvbqc8.fsf@macbookpro.home>

[-- Attachment #1: Type: text/plain, Size: 588 bytes --]

On Fri, Nov 22 2024, Eshel Yaron wrote:

> Done, in 097b685aa1c.
>
> Tomasz, setting this new option flyspell-delay-use-timer to non-nil
> (after building Emacs from the master branch, or applying these changes
> to your copy of flyspell.el) should hopefully resolve the extended delay
> you've been seeing.

Thank you Eshel and Eli for quick resolution of this issue!

Setting flyspell-delay-use-timer to non-nil indeed helps. The delay set with completion-preview-idle-delay option is not extended when flyspell-mode is active as well.

Kind wishes,
Tomasz Hołubowicz


[-- Attachment #2.1: Type: text/plain, Size: 1228 bytes --]


On Fri, Nov 22 2024, Eshel Yaron wrote:

> Eli Zaretskii <eliz@gnu.org> writes:
>
>>> From: Eshel Yaron <me@eshelyaron.com>
>>> Cc: 74437@debbugs.gnu.org,  mail@alternateved.com
>>> Date: Fri, 22 Nov 2024 08:26:42 +0100
>>> 
>>> >> > The question is: what do users expect to happen in those cases?
>>> >> 
>>> >> I don't know
>>> >
>>> > Neither do I.  I didn't say something was wrong with either of these
>>> > implementations, I'm just saying they should be well tested by users
>>> > before we have enough basis to make the decisions whether the idea is
>>> > generally good and whether it should probably become the default in
>>> > some future version.
>>> 
>>> Sounds good.  So here's a full patch that keeps the current
>>> implementation as the default:
>>
>> Thanks.  Please install on master, but please add a NEWS entry which
>> calls out this change and invites feedback on using this new behavior.
>
> Done, in 097b685aa1c.
>
> Tomasz, setting this new option flyspell-delay-use-timer to non-nil
> (after building Emacs from the master branch, or applying these changes
> to your copy of flyspell.el) should hopefully resolve the extended delay
> you've been seeing.
>
>
> Eshel

[-- Attachment #2.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 259 bytes --]

      reply	other threads:[~2024-11-23 21:41 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-11-19 11:55 bug#74437: 30.0.92; completion-preview-idle-delay is delayed by flyspell Tomasz Hołubowicz via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-11-19 16:13 ` Eshel Yaron via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-11-19 16:56   ` Tomasz Hołubowicz via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-11-19 17:19   ` Eli Zaretskii
2024-11-19 18:40     ` Eshel Yaron via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-11-19 19:10       ` Eli Zaretskii
2024-11-19 20:16         ` Eshel Yaron via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-11-20 13:04           ` Eli Zaretskii
2024-11-20 15:52             ` Eshel Yaron via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-11-20 16:29               ` Eli Zaretskii
2024-11-22  7:26                 ` Eshel Yaron via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-11-22  7:41                   ` Eli Zaretskii
2024-11-22  8:55                     ` Eshel Yaron via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-11-23 21:41                       ` Tomasz Hołubowicz via Bug reports for GNU Emacs, the Swiss army knife of text editors [this message]

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=871pz14oib.fsf@alternateved.com \
    --to=bug-gnu-emacs@gnu.org \
    --cc=74437@debbugs.gnu.org \
    --cc=eliz@gnu.org \
    --cc=mail@alternateved.com \
    --cc=me@eshelyaron.com \
    /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 external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.