Re: Automating remote emacsclient setup

Michael Albinus <[email protected]> writes:

> Joel Reicher <[email protected]> writes:
>
>> I was wondering if much work had been done on this front, and 
>> if not what it would take to do it. There's a lot already in 
>> place.
>>
>> From what I can tell the pieces would be, assuming a TCP 
>> server:
>>
>> 1) add port forwarding to the Tramp method (probably ssh only)
>> 2) generate a server file at the remote
>> 3) set Tramp prefix at the remote

[...]

> I'm a little bit lost. What shall this be good for? Could you 
> sketch the scenario you have in mind?

On (info "(emacs) emacsclient Options") there is a long-ish 
description of how to set tramp prefix that begins "For example, 
assume two hosts..."

It is this I'm wondering about automating. The setup of the 
tunnel, the generation of the server file on the remote, etc.

In terms of the use, this is (quite) nice for any remotely 
executed commands that invoke $EDITOR. The one I was doing 
recently was crontab -e.

Thanks and regards,

       - Joel