tmux sets stdin nonblocking then sets it blocking again on exit, we could probably not do that unless we are going to use it, and restore it only if it wasn't already nonblocking. But TBH does it matter that much? Why not just set it nonblocking yourself after you run tmux?
On Tue, Nov 15, 2016 at 11:01:54PM +0530, Prabhuram K wrote: > Hi, > I have an application and run it under tmux. > The application sets** STDIN_FILENO, STDOUT_FILENO and STDERR_FILENO to > nonblocking using fcntl calls. > The application internally loads the tmux configuration file using system > command (tmux source-file xxx). Soon after this is executed inside from my > application, all the STDIN/STDOUT/STDERR fds sets back to blocking state. > Not sure what is the problem here. Why tmux always sets the fds to > blocking state. Is there a way to always set to non-blocking. > Any help is highly appreciated. > > Thanks, > Prabhu > > -- > You received this message because you are subscribed to the Google Groups > "tmux-users" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [1][email protected]. > To post to this group, send email to [2][email protected]. > For more options, visit [3]https://groups.google.com/d/optout. > > References > > Visible links > 1. mailto:[email protected] > 2. mailto:[email protected] > 3. https://groups.google.com/d/optout -- You received this message because you are subscribed to the Google Groups "tmux-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
