bug#70959: Tramp connection property can interact weirdly with cache

[Dmitry Gutov <dmitry@gutov.dev>]

Hi Michael,

On 18/05/2024 13:57, Michael Albinus wrote:

>>>> IMHO if it were possible (and easy enough to implement) to have the
>>>> property connection-wide without caching it, it would make for a
>>>> better user experience.
>>> What about to make it a connection-local variable?
>> Maybe? How will that look in customization?
>>
>> Will we set some variable with 'setopt', or setq, or just have to do
>> this through Customize?
> You would do something like
> 
> --8<---------------cut here---------------start------------->8---
> (connection-local-set-profile-variables 'remote-direct-async
>     '((tramp-direct-async-process . t)))
> 
> (connection-local-set-profiles
>     '(:application tramp :machine "randomhost") 'remote-direct-async)
> --8<---------------cut here---------------end--------------->8---
> 
> `remote-direct-async' is a profile name you could choose
> yourself. `tramp-direct-async-process' would be the respective Tramp
> variable.

That looks very reasonable. One bonus is that the machine is specified 
by the hostname only.

Which would avoid the difficulty of tweaking the regexp (e.g. I had a 
problem - on a different machine - that my url included a port, and that 
needed to be reflected in the regexp as well).