tmux only uses the socket to pass the client environment and file
descriptors up to the server and for some other odds and sods like
telling the client to detach and suspend. Everything else is done
directly by the server. So it isn't really useful for a full terminal
display.
The idea is that we'
You didn't quite describe it this way, but it sort of sounds like you
are describing something like VNC for text terminals, with tmux as the
server and tmux/iTerm2 as clients. I like that overall idea. In fact
it would be pretty awesome. :) I already script up tmux so I can get
the most basic fu
I didn't mean iTerm2 should talk to tmux's socket directly, more that
there is already a protocol used over the socket. Why not have iTerm2
reuse it?
-Kekoa
On Thu, Mar 24, 2011 at 12:01 PM, George Nachman wrote:
>> In a sense tmux is already client/server via a socket in /tmp but I
>> don't kn
This idea had been considered before but perhaps rejected too early. I'm
curious to hear what Nicholas thinks about it when he gets back. Would it be
too painful to maintain two clients?
On Thu, Mar 24, 2011 at 1:00 PM, Kekoa Proudfoot
wrote:
> I didn't mean iTerm2 should talk to tmux's socket di
>
> In a sense tmux is already client/server via a socket in /tmp but I
> don't know if the protocol was done in a way that would allow new
> clients to be written easily.
The advantage of making the tmux client talk to iTerm2 over having iTerm2
communicate directly with tmux's socket is that you
