> Entirely separate process that could fork a "tmux -C attach", it > wouldn't even need to be C.
Ah, now I understand what you meant. That's quite different from what I had in mind. The desire to log sessions can't be that strange. Different terminal emulators, like putty, iTerm, and KDE's konsole, have the ability to log all session output, so I can't be the only one who uses this. The problem with having the terminal emulator do the logging is that if you're using tmux inside them and you switch between tmux-windows, they don't know that. They just log whatever gets written to the screen, so you end up with different tmux window/pane output getting mixed together in the same log file. That's why I thought it'd be useful to have tmux do the logging, and I was planning on adding the functionality to tmux itself, instead of an external program, to provide more flexiblity; not everyone wants to log everything, for example. I'll still attempt an implementation. ------------------------------------------------------------------------------ Get your SQL database under version control now! Version control is standard for application code, but databases havent caught up. So what steps can you take to put your SQL databases under version control? Why should you start doing it? Read more to find out. http://pubads.g.doubleclick.net/gampad/clk?id=49501711&iu=/4140/ostg.clktrk _______________________________________________ tmux-users mailing list tmux-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/tmux-users
