From: Michael Albinus via "Bug reports for GNU Emacs, the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
To: Dmitry Gutov <dgutov@yandex.ru>
Cc: Ergus <spacibba@aol.com>,
73718@debbugs.gnu.org, Juri Linkov <juri@linkov.net>
Subject: bug#73718: 31.0.50; Severe performance issue with Tramp and project-mode-line-format
Date: Thu, 10 Oct 2024 11:57:51 +0200 [thread overview]
Message-ID: <87wmigp9eo.fsf@gmx.de> (raw)
In-Reply-To: <29ebe27b-89d6-4861-8c5e-3db50a1660f3@yandex.ru> (Dmitry Gutov's message of "Wed, 9 Oct 2024 16:38:04 +0300")
Dmitry Gutov <dgutov@yandex.ru> writes:
> Hi!
Hi Dmitry,
> I wonder if we'll need to disable project-mode-line in remote files
> altogether, or if this is a problem that could be solved in Tramp
> (with extra caching?)
What do you think should be cached in Tramp?
Best regards, Michael.
next prev parent reply other threads:[~2024-10-10 9:57 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <874j5lzhdn.fsf.ref@aol.com>
2024-10-09 10:43 ` bug#73718: 31.0.50; Severe performance issue with Tramp and project-mode-line-format Ergus via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-10-09 13:12 ` Michael Albinus via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-10-10 11:12 ` Michael Albinus via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-10-09 13:38 ` Dmitry Gutov
2024-10-09 13:45 ` Ship Mints
2024-10-09 14:01 ` Ship Mints
2024-10-09 16:10 ` Juri Linkov
2024-10-11 0:38 ` Dmitry Gutov
2024-10-11 14:35 ` Ship Mints
2024-10-13 13:31 ` Ship Mints
2024-10-10 9:57 ` Michael Albinus via Bug reports for GNU Emacs, the Swiss army knife of text editors [this message]
2024-10-11 0:33 ` Dmitry Gutov
2024-10-11 11:45 ` Michael Albinus via Bug reports for GNU Emacs, the Swiss army knife of text editors
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=87wmigp9eo.fsf@gmx.de \
--to=bug-gnu-emacs@gnu.org \
--cc=73718@debbugs.gnu.org \
--cc=dgutov@yandex.ru \
--cc=juri@linkov.net \
--cc=michael.albinus@gmx.de \
--cc=spacibba@aol.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).