I'm not sure. IDK I've had this issue before. However, I had to
restore from an old backup, so that's a known unknown :)
It's the same distro I was using before (Ubuntu) but beside that.
I'm pretty sure I had compiled tmux on the other system as well, but
did I specify library paths and what l
If you aren't trying the latest tmux then do so. If you are then try the
previous version.
Original message
From: shawn wilson
Date: 17/06/2014 08:36 (GMT+00:00)
To: Nicholas Marriott
Cc: tmux-users
Subject: Re: terminal select
I'm not sure. IDK I've had this issue b
ok yeah, I'm on the current head:
% git lg | head -1
gits/tmux (master)
swlap1
* 92af7f5 - (HEAD, origin/master, origin/HEAD, master) Linux: Add
to log.c (5 weeks ago) [N]
So, I'll try recompiling on 1.9a
On Tue, Jun 17, 2014 at 4:33 AM, Nich
Ok, 1.9 and 1.9a both have the same issue. At 1.8, I get:
./tmuxprotocol version mismatch (client 7, server 8)
On Tue, Jun 17, 2014 at 5:31 AM, shawn wilson wrote:
> ok yeah, I'm on the current head:
> % git lg | head -1
> gits/tmux (master)
> sw
You aren't restarting tmux entirely between each version.
On Tue, Jun 17, 2014 at 05:43:02AM -0400, shawn wilson wrote:
> Ok, 1.9 and 1.9a both have the same issue. At 1.8, I get:
> ./tmuxprotocol version mismatch (client 7, server 8)
>
> On Tue, Jun 17, 2014 at 5:31 AM, shawn wilson wrote:
> >
Ugh, is there a way to isolate this without docker or some other
virtualization software?
On Tue, Jun 17, 2014 at 5:47 AM, Nicholas Marriott
wrote:
> You aren't restarting tmux entirely between each version.
>
>
> On Tue, Jun 17, 2014 at 05:43:02AM -0400, shawn wilson wrote:
>> Ok, 1.9 and 1.9a b
Is it possible to access the $TMUX environment variable from the program
specified for the lock-command?
Specifically I am interested in having the tmux socket path inside my locking
script.
Thanks, Jesse
--
HPCC Syst
