Re: file properties cache

[Michael Albinus]

Ted Zlatanov <address@hidden> writes:

>> Tramp tries to remove file properties in all cases it detects there is
>> a change. If it misses some cases where it should do so, please
>> report.
>
> Can you explain what you mean by "detects" so I know where to look for
> the bug?  When does Tramp re-run "ls -l" or its equivalent?

Scan tramp.el for "tramp-flush". You'll see there the "detections".

Commands in Tramp are performed on the fly. "ls" is applied wherever
you see a call of "tramp-get-ls-command". It is not only "ls",
information is also retrieved via "stat" or via Perl modules.

But all these places are usually surrounded by the
"with-file-property" macro, which checks first the cache, evaluates
the body in case there is no entry in the cache, and inserts the
result into the cache then.

>> Changing the file properties on a remote host during an Emacs session
>> should be rather rare, shouldn't it? 
>
> Perforce (a VCS) checkout of a file makes it +w; checkin makes it -w.
> Often I'll open a file that's not checked out for a quick look, then
> close it and revisit after it's been checked out on the remote
> system.  The effect is the same as chmod +w or -w FILE.

OK, let me sleep with this. Maybe tomorrow morning I'm convinced to
add this to kill-buffer-hook :-)

> Ted

Best regards, Michael.