Re: [Patch] Don't complain about nested tmux if it's a new server.

Committed, thanks! On Fri, Feb 05, 2010 at 08:46:43AM -0800, Micah Cowan wrote: > Micah Cowan wrote: > > Micah Cowan wrote: > >> Nicholas Marriott wrote: > >>> Hi > >>> > >>> This is a cool idea, tmux should definitely just do the right thing. > >>> > >>> We could call realpath() to get around the

Re: [Patch] Don't complain about nested tmux if it's a new server.

Micah Cowan wrote: > Micah Cowan wrote: >> Nicholas Marriott wrote: >>> Hi >>> >>> This is a cool idea, tmux should definitely just do the right thing. >>> >>> We could call realpath() to get around the // issue. If we did it on path in >>> main.c and that would clean up TMUX as well. >> Alright. >

Re: [Patch] Don't complain about nested tmux if it's a new server.

Micah Cowan wrote: > Nicholas Marriott wrote: >> Hi >> >> This is a cool idea, tmux should definitely just do the right thing. >> >> We could call realpath() to get around the // issue. If we did it on path in >> main.c and that would clean up TMUX as well. > > Alright. > > I'm thinking it may be

Re: [Patch] Don't complain about nested tmux if it's a new server.

Nicholas Marriott wrote: > Hi > > This is a cool idea, tmux should definitely just do the right thing. > > We could call realpath() to get around the // issue. If we did it on path in > main.c and that would clean up TMUX as well. Alright. I'm thinking it may be worthwhile to parse TMUX properl

Re: [Patch] Don't complain about nested tmux if it's a new server.

Hi This is a cool idea, tmux should definitely just do the right thing. We could call realpath() to get around the // issue. If we did it on path in main.c and that would clean up TMUX as well. Is it too early to do it in main.c? I don't think it is necessary to use stat(), a string comparison