On 2015-01-21 11:01 +0000, Nicholas Marriott wrote: > This all seems like stuff that should be fixed in the other programs > you mention rather than worked around in tmux. Don't they have a way > to exempt a process from being killed? Programs have been forking like > tmux does for 40 years, it's not new.
I have to concur with the OP. Even though you can work around for most of the things but being able to start the server in the foreground does simplify other workflows as well like starting tmux in debuggers or sanitizers and so on. And I also noticed that most daemons and background applications have a flag to run themselves in the foreground. Were such patch exist for tmux, would you guys accept? Not that I'm volunteering, just wondering. -- Balazs ------------------------------------------------------------------------------ New Year. New Location. New Benefits. New Data Center in Ashburn, VA. GigeNET is offering a free month of service with a new server in Ashburn. Choose from 2 high performing configs, both with 100TB of bandwidth. Higher redundancy.Lower latency.Increased capacity.Completely compliant. http://p.sf.net/sfu/gigenet _______________________________________________ tmux-users mailing list tmux-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/tmux-users
