[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: file-remote-p being called too often?
From: |
Michael Albinus |
Subject: |
Re: file-remote-p being called too often? |
Date: |
Thu, 18 Jan 2024 08:30:30 +0100 |
User-agent: |
Gnus/5.13 (Gnus v5.13) |
Eli Zaretskii <eliz@gnu.org> writes:
Hi,
>> global-auto-revert-mode also appears to trigger file-remote-p -- that
>> would be one example where the call could be usefully memoized.
>
> Michael will tell, but I don't think this can be memoized, since file
> handlers can change dynamically behind autorevert's back.
Indeed. And even if it would be only Tramp's file name handler, this
cannot be memoized, because remote file name syntax can change on the
fly. See command `tramp-change-syntax'.
And I also ask the same question as Eli: How expensive is a single
`file-remote-p' call? In the Tramp case it is designed to avoid going
remote unless a remote connection is already established. And if the
file name in question does not match the remote file name syntax, it
returns nil almost immediately.
Best regards, Michael.
- Re: file-remote-p being called too often?, (continued)
- Re: file-remote-p being called too often?, Eli Zaretskii, 2024/01/17
- Re: file-remote-p being called too often?, David Ponce, 2024/01/17
- Re: file-remote-p being called too often?, T.V Raman, 2024/01/17
- Re: file-remote-p being called too often?, Eli Zaretskii, 2024/01/18
- Re: file-remote-p being called too often?,
Michael Albinus <=
- Re: file-remote-p being called too often?, T.V Raman, 2024/01/18
- Re: file-remote-p being called too often?, Eli Zaretskii, 2024/01/18
- Re: file-remote-p being called too often?, T.V Raman, 2024/01/18
- Re: file-remote-p being called too often?, Eli Zaretskii, 2024/01/18