--- Begin Message ---
Subject: |
Tramp connection property can interact weirdly with cache |
Date: |
Wed, 15 May 2024 17:51:00 +0300 |
User-agent: |
Mozilla Thunderbird |
I've used the recipe for "direct-async-processes" as suggested:
(add-to-list 'tramp-connection-properties
(list (regexp-quote "/ssh:user@host:")
"direct-async-process" t))
and at first (the connection was already open) it didn't take effect. I
think I had to kill the connection buffer for the new property to be
used. Would be nice if this was instant.
But also, after that I tried altering tramp-connection-properties back
to disable direct-async-process for that host (for the purposes of
testing and measuring things more precisely), and found that changing
the variable doesn't bring the new behavior back. Restarting Emacs
didn't bring the old (non-direct) behavior back either - I had to edit
the ~/.emacs.d/tramp file by hand to remove that property.
I think that's something that might confuse other users.
--- End Message ---
--- Begin Message ---
Subject: |
Re: bug#70959: Tramp connection property can interact weirdly with cache |
Date: |
Sun, 19 May 2024 14:18:20 +0200 |
User-agent: |
Gnus/5.13 (Gnus v5.13) |
Version: 30.1
Dmitry Gutov <dmitry@gutov.dev> writes:
Hi Dmitry,
>> Try the following patch and the config as shown above.
>
> Seems to be working well, thank you.
Thanks for the feedback, I've pushed an extended version to master.
> Except in my case tramp.el was inside directory lisp/net.
Well, my major development happens in the Tramp git repo. It has a
different subdirectory structure, compared to the Emacs repo.
> And I guess the code will need some backward compatibility path since
> the connection property was there since Emacs 28? ;-(
Sure. I have marked the connection property "direct-async-process" as
deprecated, the user will see a warning.
Closing the bug.
Best regards, Michael.
--- End Message ---