On Wed, Aug 21, 2013 at 04:26:41PM -0500, J Raynor wrote: > There are some conditions I don't know how to generate, so I couldn't > test those. But I tried testing what I could, and it appears that > this preserves the behavior of neww and split-window, and that the > prefixes for "new -c" match the -c behavior for neww and split-window. > > Does cmd_default_path1 need to be a separate function? It's short and > it's only called by cmd_default_path.
No, and they need better names. I need to think about it a bit. > > In cmd_default_path0, can anything actually reach the "return (base);" > statement that's just above the "find_home:" label? I think you are right now. > > Cmd-new-session doesn't honor "default-path" when setting the cwd of > the first pane created in the new session. I realize this is existing > behavior and not specific to your patch. But should it honor that > setting? I guess it should since we do read a bunch of other stuff for the new session from the global options. > > If so, then take a look at the attached patch. It's basically your > patch with a little extra in cmd-new-session.c to get new-session to > set the first pane's cwd to default-path. ------------------------------------------------------------------------------ Introducing Performance Central, a new site from SourceForge and AppDynamics. Performance Central is your source for news, insights, analysis and resources for efficient Application Performance Management. Visit us today! http://pubads.g.doubleclick.net/gampad/clk?id=48897511&iu=/4140/ostg.clktrk _______________________________________________ tmux-users mailing list tmux-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/tmux-users
