If ^a prints in cat inside tmux then tmux must be receiving it from the
terminal and passing it to the application inside.
What are you expecting ^A to do? Should tmux do something or your shell inside
tmux?
Original message
From: Kartik Agaram
Date: 24/06/2014 23:37 (GM
There are two problems here. One (the big problem), I made the mistake
of changing from flock() to lockf() which is badly designed and next to
useless. Two, there is a small window where two clients could race and
both create a server.
So please try this which changes back to flock, fixes the race
Ok. Posted here
http://lists.mindrot.org/pipermail/openssh-unix-dev/2014-June/032668.html
Thanks for the feedback.
On Sun, Jun 22, 2014 at 8:00 AM, Nicholas Marriott <
nicholas.marri...@gmail.com> wrote:
> Go and persuade OpenSSH to add --help and I will reconsider the question
> for tmux.
>
>
Nicholas Marriott writes:
> Also please run all the tmux with - without the
> sleeps and see what is in the tmux-client-* logs that
> should end up in your home directories.
Oops, I forgot this line in ~/.xinitrc -
xterm -fullscreen -e tmux new-session\; split-window -v\; select-pane -U
-
Nicholas Marriott writes:
> Hmm. One of the clients should win and start the
> server, you shouldn't end up with three tmux servers.
>
> Are you moving tmux sockets away from /tmp?
No, not that I know of. How would I do that? (Then I
could tell you instantly if I did it.)
> If not, what filesys
Nicholas Marriott writes:
> Also please run all the tmux with - without the
> sleeps and see what is in the tmux-client-* logs that
> should end up in your home directories.
I run it twice as first time it worked without the
sleeps. Then it didn't. Here are the logs for both
cases:
http://u
Hi
I'm partway through rewriting mouse support to allow mouse events to be
bound as keys, which should allow us to get rid of a bunch of special
cases.
Currently I haven't included double clicks, but they will have to work
differently anyway.
Probably best to leave this until I'm finished, which
