On Wed, Oct 29, 2014 at 11:08 AM, Balazs Kezes wrote:
> On 2014-10-28 17:42 +0100, meino.cra...@gmx.de wrote:
>> I login on my Beaglebone via ssh using this command:
>> ssh -t root@ screen -R -d
>> ...
>> What is the above ssh-command in case of tmux to acchieve the same as
>> with using screen ?
On 2014-10-28 17:42 +0100, meino.cra...@gmx.de wrote:
> I login on my Beaglebone via ssh using this command:
> ssh -t root@ screen -R -d
> ...
> What is the above ssh-command in case of tmux to acchieve the same as
> with using screen ?
Have you tried "ssh -t root@ tmux attach -d"? Or even
better:
This response comes from tmux querying the device attributes which it
should only do on terminals with the XT flag set. Are you sure you did
export TERM=nsterm
BEFORE starting tmux?
On Tue, Oct 28, 2014 at 08:48:47PM -0400, Justin W. Flory wrote:
> Sadly, no changes for this. I still get t
Hi
Without many big changes to tmux, you can't make a tmux client talk to a
tmux server over a network (you can't pass file descriptors
remotely). Not to mention the huge security issues.
I think the way to do this is to write a new tmux client that uses
control mode. Control mode was designed t
Ola,
One of my age long pet peeves has been the poor integration between my local
tmux environment and tmux sessions running on servers, such as having no shared
clipboard, the annoyance of needing to different prefixes for nested sessions,
etc.
Recently I've been thinking a bit about how to f
