On Sun, Aug 18, 2013 at 1:42 AM, Nicholas Marriott
<nicholas.marri...@gmail.com> wrote:
> I think either you or me are miss the point :-).
Oh, I'll bet it's me.
> There is no point adding something to pipe-pane or something that does the
> same as pipe-pane. People who want to log individual panes can already do it
> with pipe-pane as it is now.
Is the whole point of pipe-pane to do logging? Or have people simply
found that they can use it for that purpose? If logging is
pipe-pane's purpose, then to some degree it does make sense to add to
it so that people have 1 place to go for logging.
> My idea is that we make it easier for people who want to log everything, so
> they don't need to go through and do pipe-pane for each pane.
The pipepane-autolog option allows this. If set to 1, logging starts
automatically when a new pane is created.
> My idea is
> that a window option would let you log all panes (to different files if you
> put eg #{pane_id} in the path). It'd only be global or per window but I have
> plans for options that might change that later.
The pipepane-default-logname option allows for #{pane_id} and other
#-options in the default log name. Or you can set the log name to
something different for individual panes. The options can be global
by doing "set -g pipepane-autolog 1" in tmux.conf. Otherwise, you can
enable logging per session, or per pane.
> But the idea is that this is something new, not just a replacement for
> pipe-pane "exec cat > foo".
Well, it doesn't replace the cats. You can still have them if you want.
> I also think it should be separate from
> pipe-pane so you can use the two independently.
Ok. Using the log-pane patch takes us back to that
separation/independence, but still provides the autolog feature and
log name stuff mentioned above, just with "logpane" being the prefix
for the options instead of "pipepane". But the log-pane command
seemed too similar to pipe-pane, so I've got some work to do.
> Of course an option would need some magic to detect when to stop and start
> logging. Perhaps it might be better to have flags on some command, I'm not
> sure.
Could that command be log-pane? :-)
If there's an existing command that might be a good fit to alter to
provide the start/stop-logging functionality, just let me know what it
is. I'm not too familiar with all that tmux-options can do, so it'd
be a helpful starting point.
------------------------------------------------------------------------------
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
