When opening/attaching a session in a vnc, tmux complains and fails
issuing:
sessions should be nested with care. unset $TMUX to force.
but will start after: unset TMUX
successive xterms also require the unset.
note: further research reveals that I had started the vnc session from
within a
> There are three approaches I can see:
>
> 1) Protocol changes. This could work, could have a flag to mark this as
> an "extended" client that gets additional update messages in various
> places. I'd be concerned how invasive this would be though.
Now that I understand your architecture better, i
Hi there,
I am the author of tmux-ruby.
George Nachman writes:
>> 2) Call tmux commands through the existing client. There is at least one
>> project I know of that does this already to provide a Ruby API to
>> tmux.
>
> I found the project (tmux-ruby) but not any documentation for it, so
> it'
