JD Smith <[email protected]> writes: Hi,
> It would be application specific, not a general TRAMP setting. In my > case, the remote application itself (iPython) would send a message > reporting its own PID, and my package code would read that PID and set > it into the process property. I don't think TRAMP would need to do > anything special (other than not inhibiting this usage for > direct-async connections). Since my package requires an (i)ipython > executable to exist on the remote side, if it fails to find one, well > that's a user error. Sounds like a good plan :-) If it works for you, could you pls send some few lines for the Tramp manual, describing this technique? Other users can profit from this. > Until we find a way for sending signals to the remote direct async > process, we must point to the non-direct case. > > The normal non-direct ControlMaster side-channel commands like "kill - > 2" seem to work just fine for direct-async. TRAMP just needs a > 'remote-pid. Yes. > Thanks again for your tireless work on TRAMP. Hope you feel better > soon! Best regards, Michael.
