<div dir="ltr"><br><div class="gmail_extra"><br><br><div class="gmail_quote">On Tue, Dec 3, 2013 at 2:34 PM, Keith Winstein <span dir="ltr"><<a href="mailto:keithw@mit.edu" target="_blank">keithw@mit.edu</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div>You may be interested in our conversation with the iTerm2 folks earlier this year -- please see <a href="https://www.mail-archive.com/mosh-devel@mit.edu/msg00304.html" target="_blank">https://www.mail-archive.com/mosh-devel@mit.edu/msg00304.html</a></div>
</div></blockquote><div><br></div><div>That is interesting. As I mentioned in my first email, I think tmux command and control over mosh is a non-starter - they're both sync protocols and would get in each other's way.</div>
<div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div>The scrollback is on the agenda for us; unfortunately I doubt the integration to a native terminal emulator is going to happen anytime soon.</div>
</div></blockquote><div><br></div><div>Ahh - perhaps I should have been clearer. Here are some features and where I think they should sit:</div><div><br></div><div>1) scrollback - already planned by mosh team</div><div>2) multiple tab/window support - this is my core feature suggestion for the mosh team. Think of this as extended scrollback - you're storing more state on the server. I'm also assuming that mosh-client would have quite a primitive 'screen'-like interface to these multiple terminals.</div>
<div>3) iTerm integration to support the mosh-client protocol. This would obviously not be done by the mosh team. I assume this would be done by another interested party (possibly myself). (In the same way that the current tmux integration in iTerm was done by the iTerm team, not the tmux team.)</div>
<div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div>You could get somewhere by just running tmux locally (and maybe having it automatically run "mosh server" when you start up a new tab), but I realize that's probably not quite what you wanted.</div>
</div></blockquote><div><br></div><div>Running tmux on the server inside each mosh session would get me scrollback now, but it wouldn't work with the mac UI.</div><div><br></div><div>When mosh gets scrollback support, then one (me?) could still write meaningful iTerm integration. The difference between this and if mosh had multi-window support would be the behaviour on opening a new tab. With multi-window support a new login shell is opened on the server and forwarded over the original mosh connection to a new window opened by iTerm. Without multi-window support, iTerm would have to open a new mosh connection to the server, run a new instance of mosh-server, etc. The UI experience would be quite similar once you were logged in, but would be requires kerberos or pubic keys for a clean login experience (which is quite doable).</div>
<div><br></div><div>Be well,</div><div><br></div><div>Will :-}</div><div><br></div><div> </div></div></div></div>