Ok, this week I will implement it About the command, do you prefer two separate commands for locking/unlocking and waiting signaling? What name(s)/parameters should the commands have? Should I use a separate file for defining the tree/global variables(like I did with the monitor.c file)
I think the only real issue I have now is on how to handle pane exits, even more now that we will use flags for locking. For example, if a pane holding a lock exits before unlocking what can we do? Perhaps we can also store the ref to the pane currently holding the lock so if we detect a pane exits we can unlock. But even so, is there an easy way to detect when a pane exits? ------------------------------------------------------------------------------ Everyone hates slow websites. So do we. Make your web apps faster with AppDynamics Download AppDynamics Lite for free today: http://p.sf.net/sfu/appdyn_d2d_feb _______________________________________________ tmux-users mailing list tmux-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/tmux-users
