Re: tmux bug (?) and problem (and more)

2014-06-21 Thread Emanuel Berg
Romain Francoise writes: > The mailing list is tmux-us...@lists.sf.net and is > usually pretty active. OK! I send this mail to them as well, as well as the first mail I sent, in quotes. I don't know if I'm added automatically but otherwise you'll have to CC me, I guess. >> In .zprofile, I have

Re: tmux bug (?) and problem (and more)

2014-06-23 Thread Emanuel Berg
Nicholas Marriott writes: > If you do without the sleeps and it goes wrong, how > many tmux servers do you end up with? (run "ps > -eopid,ppid,comm" and look for tmux with a ppid of > 1). Without (any) sleep, instant failure for /dev/tty2 and /dev/tty3: pid ppid comm -- 29821 t

Re: tmux bug (?) and problem (and more)

2014-06-23 Thread Emanuel Berg
Nicholas Marriott writes: > If you do without the sleeps and it goes wrong, how > many tmux servers do you end up with? (run "ps > -eopid,ppid,comm" and look for tmux with a ppid of > 1). Using this insight, this will do unless you guys have better suggestions: tmux-two-panes-50-50 () { tmu

Re: tmux bug (?) and problem (and more)

2014-06-23 Thread Emanuel Berg
Romain Francoise writes: > It's not possible to have per-pane or per-window key > bindings, but you can just start the application in a > dedicated tmux server (using e.g. 'tmux -L rebind -c > rebind.conf') and then attach to that from the main > server. In the inner server you can disable any >

Re: tmux bug (?) and problem (and more)

2014-06-23 Thread Emanuel Berg
Romain Francoise writes: > It's not possible to have per-pane or per-window key > bindings, but you can just start the application in a > dedicated tmux server (using e.g. 'tmux -L rebind -c > rebind.conf') and then attach to that from the main > server. In the inner server you can disable any >

Re: tmux bug (?) and problem (and more)

2014-06-23 Thread Emanuel Berg
Romain Francoise writes: > Anyway, I have no idea about this but my advice would > be to take the reverse approach and use tmux as your > shell, a new session will automatically be started > for each tty. I just tried that, but I rather not do that. First, I want Emacs in tty1 without tmux becau

Re: tmux bug (?) and problem (and more)

2014-06-23 Thread Emanuel Berg
Nicholas Marriott writes: > What tmux version? $ tmux -V tmux 1.9 > If you do without the sleeps and it goes wrong, how > many tmux servers do you end up with? (run "ps > -eopid,ppid,comm" and look for tmux with a ppid of > 1). OK, I'll remove the sleeps and do that the next time it happens. A

Re: tmux bug (?) and problem (and more)

2014-06-23 Thread Emanuel Berg
Nicholas Marriott writes: > If you do without the sleeps and it goes wrong, how > many tmux servers do you end up with? (run "ps > -eopid,ppid,comm" and look for tmux with a ppid of > 1). Now I get it! I reinserted the sleepyheads and it works, this time I get $ ps -e -o pid,ppid,comm | grep t

Re: tmux bug (?) and problem (and more)

2014-06-24 Thread Emanuel Berg
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

Re: tmux bug (?) and problem (and more)

2014-06-24 Thread Emanuel Berg
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

Re: tmux bug (?) and problem (and more)

2014-06-24 Thread Emanuel Berg
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 -

Re: tmux bug (?) and problem (and more)

2014-06-26 Thread Emanuel Berg
Nicholas Marriott writes: > 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 wh