On Fri, Jan 24, 2014 at 10:55:09PM -0600, J Raynor wrote: > > I don't really see a need for this at all, especially given the > > complexity it'll add to the client > > Do you not see a need for the TODO list item (anymore), or just the > proposed implementation?
The TODO list item. > > If it's the latter, how about something simpler? The client could > read the config file and look for: > > #!socket_path /path/to/socket > > Everything after "#!socket_path" is taken as the path name. The > server doesn't have to change at all, and the client doesn't need any > command tables or cmdlists. But since the client can't call > cmd_string_parse(), there'd be no tilde or variable expansion in the > path. I don't like this idea, I think if it exists it has to look the same as a normal option. Your second suggestion is the most reasonable way to do it but it would still not always work (what if someone sets it with if-shell?). It's a lot of extra code for something one person asked for four years ago. Anyway, people can now use TMUX_TMPDIR to put the socket directory elsewhere if they want. ------------------------------------------------------------------------------ CenturyLink Cloud: The Leader in Enterprise Cloud Services. Learn Why More Businesses Are Choosing CenturyLink Cloud For Critical Workloads, Development Environments & Everything In Between. Get a Quote or Start a Free Trial Today. http://pubads.g.doubleclick.net/gampad/clk?id=119420431&iu=/4140/ostg.clktrk _______________________________________________ tmux-users mailing list tmux-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/tmux-users
