[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Introducing thread-safe Tramp
From: |
Michael Albinus |
Subject: |
Re: Introducing thread-safe Tramp |
Date: |
Tue, 07 Aug 2018 17:58:32 +0200 |
User-agent: |
Gnus/5.13 (Gnus v5.13) Emacs/27.0.50 (gnu/linux) |
Robert Pluim <address@hidden> writes:
>> How about this:
>> "Non-nil means the next interactively called command runs asynchronously."
>> Or since commands are really interactively called functions, just this:
>> "Non-nil means the next command runs asynchronously."
>
> "Non-nil means the next command is requested to run asynchronously."
No for the same reason as said already.
> The command in question might not have async support.
Indeed. And that's why I believe "requested" is the wrong word. I've
tried it with "... is indicated ..."
Best regards, Michael.
- Re: C-x &, (continued)
- Re: Introducing thread-safe Tramp, Filipp Gunbin, 2018/08/06
- Re: Introducing thread-safe Tramp, Michael Albinus, 2018/08/07
- Re: Introducing thread-safe Tramp, Stephen Berman, 2018/08/07
- Re: Introducing thread-safe Tramp, Robert Pluim, 2018/08/07
- Re: Introducing thread-safe Tramp, Stephen Berman, 2018/08/07
- Re: Introducing thread-safe Tramp, Michael Albinus, 2018/08/07
- Re: Introducing thread-safe Tramp,
Michael Albinus <=
- RE: Introducing thread-safe Tramp, Drew Adams, 2018/08/07
- Re: Introducing thread-safe Tramp, Michael Albinus, 2018/08/07
- RE: Introducing thread-safe Tramp, Drew Adams, 2018/08/07
- Re: Introducing thread-safe Tramp, Michael Albinus, 2018/08/07
- Re: Introducing thread-safe Tramp, Michael Albinus, 2018/08/07
- Re: Introducing thread-safe Tramp, Eli Zaretskii, 2018/08/07
- Re: Introducing thread-safe Tramp, Michael Albinus, 2018/08/07
- Re: Introducing thread-safe Tramp, Eli Zaretskii, 2018/08/07
- Re: Introducing thread-safe Tramp, Michael Albinus, 2018/08/07
- RE: Introducing thread-safe Tramp, Drew Adams, 2018/08/07