From: Eli Zaretskii <eliz@gnu.org>
To: Jim Porter <jporterbugs@gmail.com>
Cc: 51622@debbugs.gnu.org
Subject: bug#51622: 29.0.50; [PATCH] Abbreviate remote home directories in `abbreviate-file-name'
Date: Sat, 06 Nov 2021 10:06:23 +0200 [thread overview]
Message-ID: <83v915btds.fsf@gnu.org> (raw)
In-Reply-To: <5ac0b5f3-302c-2f96-771c-8d38088aa573@gmail.com> (message from Jim Porter on Fri, 5 Nov 2021 20:44:44 -0700)
> From: Jim Porter <jporterbugs@gmail.com>
> Date: Fri, 5 Nov 2021 20:44:44 -0700
>
> Second, I removed the caching of the abbreviated home dir. Since adding
> TRAMP support means there are multiple home dirs (one per host), keeping
> the caching would have been fairly complex, and it's already the source
> of potential bugs (e.g. when temporarily setting HOME to something
> else). I did some benchmarking on this (see attached), and while it is
> indeed slower without the caching, I don't think it's worth keeping the
> caching around.
If some user never uses Tramp, this removal will be a net loss for
that user. So I think we should have this customizable. Or maybe
even better: as long as Tramp is not used, keep the cache, and only
stop updating it when Tramp is being used.
next prev parent reply other threads:[~2021-11-06 8:06 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-06 3:44 bug#51622: 29.0.50; [PATCH] Abbreviate remote home directories in `abbreviate-file-name' Jim Porter
2021-11-06 8:06 ` Eli Zaretskii [this message]
2021-11-06 15:34 ` Michael Albinus
2021-11-06 16:38 ` Jim Porter
2021-11-06 17:41 ` Michael Albinus
2021-11-07 3:30 ` bug#51622: 29.0.50; [PATCH v2] " Jim Porter
2021-11-07 18:37 ` Michael Albinus
2021-11-08 4:54 ` Jim Porter
2021-11-08 15:58 ` Michael Albinus
2021-11-08 18:32 ` Jim Porter
2021-11-08 19:18 ` Michael Albinus
2021-11-14 2:10 ` Jim Porter
2021-11-14 14:43 ` Michael Albinus
2021-11-15 6:58 ` bug#51622: 29.0.50; [PATCH v3] " Jim Porter
2021-11-15 16:59 ` Michael Albinus
2021-11-16 1:14 ` Jim Porter
2021-11-16 11:43 ` Michael Albinus
2021-11-16 12:57 ` Michael Albinus
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=83v915btds.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=51622@debbugs.gnu.org \
--cc=jporterbugs@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).