unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Felix <felix.dick@web.de>
Cc: joaotavora@gmail.com, 60107@debbugs.gnu.org
Subject: bug#60107: 30.0.50; Open new files very slow if eglot and which-function-mode are enabled.
Date: Fri, 16 Dec 2022 09:23:02 +0200	[thread overview]
Message-ID: <83mt7nke21.fsf@gnu.org> (raw)
In-Reply-To: <87pmcki50f.fsf@web.de> (message from Felix on Fri, 16 Dec 2022 00:59:28 +0100)

> Cc: 60107@debbugs.gnu.org
> From: Felix <felix.dick@web.de>
> Date: Fri, 16 Dec 2022 00:59:28 +0100
> 
> Now it makes sense that glsl-mode managed with eglot and glslls takes
> forever to open glsl files, and imenu is not working at all.
> Seems to depend on the server.
> I will try your suggestions, in the end which-function-mode
> is not that important to me, so if everything fails it's not that bad
> either.

Does it help to customize which-func-non-auto-modes to add the major
mode you are using there?  Or maybe customize which-func-maxout to a
small value to get the same effect in any mode?  I'm asking whether
this helps because it's unclear to me whether doing so will avoid
blocking redisplay, if and when which-func finally becomes active.

> If this is not a bug of emacs,
> feel free to close this bug report.

If the above doesn't help, I guess some changes to which-func could be
in order, to avoid blocking the first display of a buffer for such a
long time.  So in that case we shouldn't close this bug report yet.

Thanks.





  reply	other threads:[~2022-12-16  7:23 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-12-15 22:53 bug#60107: 30.0.50; Open new files very slow if eglot and which-function-mode are enabled Felix
2022-12-15 23:44 ` João Távora
2022-12-15 23:59   ` Felix
2022-12-16  7:23     ` Eli Zaretskii [this message]
2022-12-16 11:26       ` Felix
2022-12-16 15:45         ` Eli Zaretskii
2022-12-16 15:53           ` João Távora

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=83mt7nke21.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=60107@debbugs.gnu.org \
    --cc=felix.dick@web.de \
    --cc=joaotavora@gmail.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 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).