all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Simon Katz <sk@nomistech.com>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: 50042@debbugs.gnu.org
Subject: bug#50042: 26.3; Post-command hooks slow with M-x commands
Date: Fri, 13 Aug 2021 13:40:51 +0100	[thread overview]
Message-ID: <CAPXG948zsPq6KZHHPcw=W9G1h7rHG6tf0vdhLgNjT=BpmCQSKA@mail.gmail.com> (raw)
In-Reply-To: <87lf55edhd.fsf@gnus.org>

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

It's probably worth me giving a bit more context…

I'm using `lsp-ui`, and that's using post-command hooks to update the UI.

If I use `M-x flycheck-next-error` (for example), it takes time for the UI
to update.

See https://github.com/emacs-lsp/lsp-ui/issues/647

[-- Attachment #2: Type: text/html, Size: 468 bytes --]

  reply	other threads:[~2021-08-13 12:40 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <878s13os3a.fsf@gnus.org>
2021-08-13 11:52 ` bug#50042: 26.3; Post-command hooks slow with M-x commands Simon Katz
2021-08-13 12:27   ` Lars Ingebrigtsen
2021-08-13 12:40     ` Simon Katz [this message]
2021-08-14 16:36     ` Lars Ingebrigtsen
2021-08-14 20:52       ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-08-15 11:38         ` Lars Ingebrigtsen
2021-08-17  0:41           ` Dmitry Gutov
     [not found]   ` <handler.50042.C.162902754922550.notifdonectrl.0@debbugs.gnu.org>
2021-08-18 15:27     ` bug#50042: acknowledged by developer (control message for bug #50042) Simon Katz
2021-08-18 15:33       ` Simon Katz
2021-08-18 15:37       ` Simon Katz
2021-08-19 13:07         ` Lars Ingebrigtsen
2021-08-19 14:55           ` Simon Katz
2021-08-20 13:09             ` Lars Ingebrigtsen
2021-08-20 16:14               ` Simon Katz
2021-08-21 12:55                 ` Lars Ingebrigtsen

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='CAPXG948zsPq6KZHHPcw=W9G1h7rHG6tf0vdhLgNjT=BpmCQSKA@mail.gmail.com' \
    --to=sk@nomistech.com \
    --cc=50042@debbugs.gnu.org \
    --cc=larsi@gnus.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 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.