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
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.
>
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
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
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
Currently, tmux complains if you create or attach a session within
another tmux session (that is, if $TMUX is set). This is true even if
the new session being created is on a new _server_ being created (e.g.,
"tmux -L new").
This patch addresses this issue by silently succeeding when the new
sessi
