[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Tramp mosh method

From: Jason Stelzer
Subject: Re: Tramp mosh method
Date: Mon, 23 Apr 2012 16:41:05 -0400

I don't think it's going to be that simple.

For ssh connections, you have a byte stream that tramp can interpret.

Mosh changes that. They're using  a new protocol called the State
Synchronization Protocol. It operates at the screen level and
synchronizes state.

Someone else can correct me where I'm wrong, but once ssh is used for
initial authentication, mosh uses a completely different protocol to
sych screen state.

2012/4/22 Ted Zlatanov <address@hidden>:
> Hi,
> I'd like to use the very cool mosh client on my laptop.  If you haven't
> tried mosh yet, it's a UDP-based client that establishes the connection
> via SSH and then maintains a login across network timeouts and all kinds
> of outages; indispensable when you are on the road or on a flaky
> connection.
> It only takes address@hidden as parameters.  -p specifies the UDP port so it's
> not the usual -p for SSH; you have use ~/.ssh/config to specify the
> port.  It also doesn't take the SSH -o options, again relying on
> ~/.ssh/config to specify them.  I hope that explains why I modified
> `tramp-login-args' the way I did, starting with the "ssh" method.
> I tried adding this to my setup but the `mosh' method complains any host
> is not remote.  Could you advise?  Is it the removal of the "-p" command
> so there is no %p in the login args?
> Thanks
> Ted
> #+begin_src lisp
> (add-to-list
>  'tramp-methods
>  '("mosh"
>   (tramp-login-program "/usr/local/bin/mosh")
>   (tramp-login-args
>    (("address@hidden")))
>   (tramp-async-args
>    (()))
>   (tramp-remote-shell "/bin/sh")
>   (tramp-remote-shell-args
>    ("-c"))
>   (tramp-gw-args
>    ())
>   (tramp-default-port 22)))
> #+end_src
> _______________________________________________
> Tramp-devel mailing list
> address@hidden


reply via email to

[Prev in Thread] Current Thread [Next in Thread]