Here's the patch in question:
http://github.com/ThomasAdam/tmux/commit/b50a375d54c4d76e55fb8ba2e1901109f1127bff
OpenBSD patchset 684:
Catch SIGCHLD to avoid a zombie, from patrick keshishian
Ignored signals are inherited by child processes (at least on systems
like Mac OS X), which means that lot
already fixed but not sync'd to sf yet
On Wed, May 12, 2010 at 10:57:50AM +0200, Mark Edgar wrote:
> Here's the patch in question:
>
> http://github.com/ThomasAdam/tmux/commit/b50a375d54c4d76e55fb8ba2e1901109f1127bff
> OpenBSD patchset 684:
> Catch SIGCHLD to avoid a zombie, from patrick keshish
You can't make the status line turn black for panes other than the
current one, but with bell-action set to "any" bells/visual-bell should
happen for any pane.
On Wed, May 12, 2010 at 05:06:59AM +0200, bikefridaywal...@gmail.com wrote:
> Right now I have tmux setup to monitor activity only on spe
On Tue, May 11, 2010 at 03:02:00PM +0300, Lars Nooden wrote:
> On Tue, 11 May 2010, Nicholas Marriott wrote:
> > Yeah we should probably relax that to allow group permissions, try this.
>
> The patch itself allows tmux to tolerate a socket which has group read
> write permissions allowed. In pra
Excellent! I wonder, though, if this is possible for the bell, why not for
the status line? I guess that's a rhetorical question in that it's more of
a feature request than a request for a mechanical explanation. :D
On Wed, 12 May 2010, Nicholas Marriott wrote:
> You can't make the status line t
Yes, this is an error, it should mark the status line for activity/bell
in any pane in a window (except if the window is the current window),
not just the current pane.
On Wed, May 12, 2010 at 09:26:29PM +0200, bikefridaywal...@gmail.com wrote:
> Excellent! I wonder, though, if this is possible f
