[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Remote asynchronous processes
From: |
Michael Albinus |
Subject: |
Re: Remote asynchronous processes |
Date: |
Tue, 04 Aug 2020 19:35:39 +0200 |
User-agent: |
Gnus/5.13 (Gnus v5.13) Emacs/28.0.50 (gnu/linux) |
Philipp Stephani <p.stephani2@gmail.com> writes:
Hi Philipp,
>> However, we will loose features of remote asynchronous processes. At
>> least (and not comprehensive), processes started via make-process
>>
>> - are not checked for passwords or other interactive dialogues
>> - do not not support multi-hops anymore
>> - cannot be killed via interrupt-process (??? I'm not sure)
>> - do not tell the remote tty
>> - ...
>
> These are typically irrelevant for the editing use cases I have in
> mind. In particular, starting a Flymake backend couldn't ever prompt
> the user; any prompt should be converted into a silent failure.
There are prompts you aren't aware of. Password requests are handled by
Tramp silently, using auth-sources caches. Don't think only about ssh
where you can use public keys, there's also sudo or whatever.
Best regards, Michael.
- Re: Remote asynchronous processes, (continued)
Re: Remote asynchronous processes, Philipp Stephani, 2020/08/04
Re: Remote asynchronous processes, Philipp Stephani, 2020/08/04
- Re: Remote asynchronous processes,
Michael Albinus <=
Re: Remote asynchronous processes, Philipp Stephani, 2020/08/04
Re: Remote asynchronous processes, Philipp Stephani, 2020/08/04
Re: Remote asynchronous processes, Philipp Stephani, 2020/08/07