bug#41333: 27.0.91; Spurious errors using TRAMP and auto-save-visited-mode

[Michael Albinus]

Lars Ingebrigtsen <larsi@gnus.org> writes:

Hi,

> Philipp Stephani <p.stephani2@gmail.com> writes:
>
>> I've stopped auto-save-visited-mode for remote files due to this bug,
>> and recently I've stopped using TRAMP altogether, so personally I
>> can't reproduce the problem any more. That doesn't mean the root cause
>> is fixed, though; maybe Michael can make some sense of the logs I
>> posted?
>
> Perhaps; I've now added Michael to the CCs.

I've played for a while with auto-save-visited-mode and remote files. I
couldn't reproduce the problem.

As said in the original message, it could depend on user customisation,
so there is no guarantee that the problem is gone.

auto-save-visited-mode works with an idle timer. This could always be a
source of problems, when timers do remote file operations while another
remote file operation is in progress. The observation in the original
report, that Tramp doesn't handle sent commands and the returned output
in order, is an indication of such a problem.

With Emacs 28, Tramp has tried better to detect interference of remote
file operations, and at least to report them if it isn't possible to
solve them. Perhaps this has improved the situation.

I'm sorry but w/o any more information I don't know what I could do
else. Perhaps we should close the bug, although it is not satisfying w/o
knowing what is/was up.

However, one possible counter measure is to disable
auto-save-visited-mode for remote files, as Philipp did in his
setup. Don't know whether this is acceptable, but given that we're
unsure whether Tramp works correctly here it might be the better option.

Best regards, Michael.