Combining the logging with pipe-pane seemed to be the easier option since I'm familiar with both bits of code, so I gave that a shot and I've attached a new patch.
The code for the logging and for having pipe-pane write to a file are a bit simpler than previous patches. There's no need for a separate fd or filename for the logging, and there's no need for a separate file-writing socketpair for pipe-pane. So, struct window_pane doesn't change. Passing -f to pipe-pane makes it interpret argv[0] as a filename instead of a command. Passing -f without a string or with an empty string causes it to use the default logname. Is this better than having a separate command for the logging? Would you still prefer to just have a window option?
pipepane-logging.patch
Description: Binary data
------------------------------------------------------------------------------ Get 100% visibility into Java/.NET code with AppDynamics Lite! It's a free troubleshooting tool designed for production. Get down to code-level detail for bottlenecks, with <2% overhead. Download for free and get started troubleshooting in minutes. http://pubads.g.doubleclick.net/gampad/clk?id=48897031&iu=/4140/ostg.clktrk
_______________________________________________ tmux-users mailing list tmux-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/tmux-users
