On Fri, Nov 29, 2013 at 21:21:41 -0500, Timothy Brown wrote: > You have it right. Perhaps the current behavior is the intended > behavior; but what i’d like is for save-buffer to write to the fifo > but either show an error message (“no readers” or the like) or block, > in the worst case, until I read from the fifo. I haven’t taken a > deep look yet, but i’m guessing that O_NDELAY may be set but there’s > just no intuitive error message indicating what happens. > > If I am reading from the fifo actively, save-buffer works as expected.
What is done in uzbl to support the FIFO at all times is to just open it as "r+" so that it thinks it has a writer. I don't think block-until-there's-a-reader is possible (I think SIGPIPE is tossed into the mix right away). --Ben ------------------------------------------------------------------------------ Rapidly troubleshoot problems before they affect your business. Most IT organizations don't have a clear picture of how application performance affects their revenue. With AppDynamics, you get 100% visibility into your Java,.NET, & PHP application. Start your 15-day FREE TRIAL of AppDynamics Pro! http://pubads.g.doubleclick.net/gampad/clk?id=84349351&iu=/4140/ostg.clktrk _______________________________________________ tmux-users mailing list tmux-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/tmux-users
