Yep. I thought of having status_replace1 do the check but this is better.
On Mon, Jan 03, 2011 at 09:14:06PM +0000, Thomas Adam wrote: > On Mon, Jan 03, 2011 at 09:09:11PM +0000, Nicholas Marriott wrote: > > Good catch. status_replace1 is only called from status_replace so I > > think its better to fix it there: > > If you can guarantee it will always be that way round (and that nothing in > the future won't ever likely call status_replace1() directly), sure. This > also works. :) > > -- Thomas Adam > > -- > "It was the cruelest game I've ever played and it's played inside my head." > -- "Hush The Warmth", Gorky's Zygotic Mynci. ------------------------------------------------------------------------------ Learn how Oracle Real Application Clusters (RAC) One Node allows customers to consolidate database storage, standardize their database environment, and, should the need arise, upgrade to a full multi-node Oracle RAC database without downtime or disruption http://p.sf.net/sfu/oracle-sfdevnl _______________________________________________ tmux-users mailing list tmux-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/tmux-users
