From: Eli Zaretskii <eliz@gnu.org>
To: Ihor Radchenko <yantar92@posteo.net>, Dmitry Gutov <dmitry@gutov.dev>
Cc: 67672@debbugs.gnu.org, schand@cooley.com, rmoore@cooley.com
Subject: bug#67672: EMACS - Slow opening files
Date: Wed, 13 Dec 2023 13:49:45 +0200 [thread overview]
Message-ID: <83v892s4o6.fsf@gnu.org> (raw)
In-Reply-To: <871qbrxexo.fsf@localhost> (message from Ihor Radchenko on Tue, 12 Dec 2023 21:56:51 +0000)
> From: Ihor Radchenko <yantar92@posteo.net>
> Cc: Eli Zaretskii <eliz@gnu.org>, "67672@debbugs.gnu.org"
> <67672@debbugs.gnu.org>, "Chand, Suresh" <schand@cooley.com>
> Date: Tue, 12 Dec 2023 21:56:51 +0000
>
> "Moore, Rider" <rmoore@cooley.com> writes:
>
> > Ah, thank you sooo much!! I think this fixed our issue.
> > Thank you for the instructions as well. Does it matter where we save the test.el file? Once we run M-x load-file we are done with it?
>
> Do note that removing vc-refresh-state may break some things related to
> version control functionality of Emacs, so what I asked you to do is a
> workaround at best; not a proper fix.
>
> Eli or people more familiar with vc-hg.el internals might ask more
> questions to narrow down the more precise cause.
>
> For now, we just determined that `vc-refresh-state' is slow in your setup.
Dmitry, any ideas?
My best idea is to profile vc-refresh-state in those situations, to
see what is slow. But maybe before that, running from the shell
prompt the hg command that is run by vc-refresh-state would be useful?
Because if hg is very slow with that many files on that type of
volume, there's little Emacs can do?
Can you show that command for the OP to try?
next prev parent reply other threads:[~2023-12-13 11:49 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-06 22:43 bug#67672: EMACS - Slow opening files Chand, Suresh
2023-12-07 6:43 ` Eli Zaretskii
2023-12-07 16:39 ` Moore, Rider
2023-12-07 18:01 ` Eli Zaretskii
2023-12-07 18:16 ` Moore, Rider
2023-12-07 18:28 ` Eli Zaretskii
2023-12-08 21:41 ` Moore, Rider
2023-12-09 7:29 ` Eli Zaretskii
2023-12-11 17:16 ` Moore, Rider
2023-12-11 17:53 ` Eli Zaretskii
2023-12-12 15:52 ` Moore, Rider
2023-12-12 17:07 ` Eli Zaretskii
2023-12-12 17:57 ` Moore, Rider
2023-12-12 18:40 ` Eli Zaretskii
2023-12-12 19:06 ` Moore, Rider
2023-12-12 19:15 ` Eli Zaretskii
2023-12-12 19:33 ` Moore, Rider
2023-12-12 19:46 ` Eli Zaretskii
2023-12-12 19:58 ` Moore, Rider
2023-12-12 21:03 ` Ihor Radchenko
2023-12-12 21:18 ` Moore, Rider
2023-12-12 21:25 ` Ihor Radchenko
2023-12-12 21:25 ` Moore, Rider
2023-12-12 21:29 ` Moore, Rider
2023-12-12 21:43 ` Ihor Radchenko
2023-12-12 21:32 ` Ihor Radchenko
2023-12-12 21:38 ` Moore, Rider
2023-12-12 21:56 ` Ihor Radchenko
2023-12-13 11:49 ` Eli Zaretskii [this message]
2023-12-13 11:59 ` Dmitry Gutov
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=83v892s4o6.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=67672@debbugs.gnu.org \
--cc=dmitry@gutov.dev \
--cc=rmoore@cooley.com \
--cc=schand@cooley.com \
--cc=yantar92@posteo.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 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.