[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Introducing thread-safe Tramp
From: |
Robert Pluim |
Subject: |
Re: Introducing thread-safe Tramp |
Date: |
Wed, 01 Aug 2018 18:27:40 +0200 |
Robert Pluim <address@hidden> writes:
> Michael Albinus <address@hidden> writes:
>
>> Robert Pluim <address@hidden> writes:
>>
>> Hi Robert,
>>
>>> Given that this is all highly experimental, I wouldn't mind a 'be 100%
>>> asynchronous' variable in order to ensure maximal coverage (plus I
>>> donʼt want the cognitive load of having to think "do I want this
>>> operation to be asynchronous"). Once we have more experience with that
>>> we can decide which if any operations should default to asynchronous.
>>
>> For the time being, I have added
>>
>> find-file-asynchronously is a variable defined in ‘files.el’.
>> Its value is nil
>>
>> Documentation:
>> Non-nil means visit file asynchronously when called interactively.
>> This behavior is toggled by a prefix argument to the interactive call.
>>
>> If there are better proposals to the option's name, and to the key
>> binding for the toggle behavior, I'm all open.
So Iʼve been running with find-file-asynchronously t for the past 5
days, and I can't say Iʼve noticed anything going wrong. Having said
that Iʼm not a particularly heavy user of tramp, but so far itʼs all
looking good.
Robert
- Re: Introducing thread-safe Tramp,
Robert Pluim <=
- Re: Introducing thread-safe Tramp, Michael Albinus, 2018/08/04
- Re: Introducing thread-safe Tramp, Michael Albinus, 2018/08/04
- Re: Introducing thread-safe Tramp, Eli Zaretskii, 2018/08/04
- Re: Introducing thread-safe Tramp, Michael Albinus, 2018/08/04
- Re: Introducing thread-safe Tramp, Eli Zaretskii, 2018/08/04
- Re: Introducing thread-safe Tramp, Michael Albinus, 2018/08/04
- Re: Introducing thread-safe Tramp, Eli Zaretskii, 2018/08/04
- Re: Introducing thread-safe Tramp, Michael Albinus, 2018/08/04
- Re: Introducing thread-safe Tramp, Eli Zaretskii, 2018/08/04