tmux behave differently between the command lines and equivalent config file (.tmux.conf)

command line:

bash$ tmux new \; split-window -h \;

config file (.tmux.conf), (and then, in the command line, we just type 'tmux')

new
split-window -h

The command line version nicely shows me a split window at the startup, and it creates only one session. However, the config file version behave differently:

• It creates 2 sessions, with session name "0" and "1" rather than just one seesion.
• Session "0" has the split windows, identical to what I saw in the command line version.
• Session "1" has a single full window.
• It stops at session "1".

So, in the config file version, I finally reach the session "1" on the screen. If I do an 'exit', and then attach session 0, then, it goes to session "0" with the same results as the command line version.

If, alternatively, the config file contains only the split line:

split-window -h

then when 'tmux' is typed, it shows an error message at the startup:

.tmux.conf:1: no current target 

And no split windows (since the split window command fails, as we can see it complains the 1st line of the configuration has no current target.)

Apparently, command line version is what I want/need.

What's wrong with the config file version?

tmux behave differently between the command lines and equivalent config file (.tmux.conf)

command line:

bash$ tmux new \; split-window -h \;

config file (.tmux.conf), (and then, in the command line, we just type 'tmux')

new
split-window -h

The command line version nicely shows me a split window at the startup, and it creates only one session. However, the config file version behave differently:

• It creates 2 sessions, with session name "0" and "1" rather than just one seesion.
• Session "0" has the split windows, identical to what I saw in the command line version.
• Session "1" has a single full window.
• It stops at session "1".

So, in the config file version, I finally reach the session "1" on the screen. If I do an 'exit', and then attach session 0, then, it goes to session "0" with the same results as the command line version.

If, alternatively, the config file contains only the split line:

split-window -h

then when 'tmux' is typed, it shows an error message at the startup:

.tmux.conf:1: no current target 

And no split windows (since the split window command fails: As we can see, it complains the 1st line of the configuration to have no current target.)

Apparently, command line version is what I want/need.

What's wrong with the config file version?

tmux behave different between the command lines and equivalent config file (.tmux.conf)

command line:

bash$ tmux new \; split-window -h \;

config file (.tmux.conf), (and then, in the command line, we just type 'tmux')

new
split-window -h

The command line version nicely shows me a split window at the startup, and it creates only one session. However, the config file version behave differently:

• It creates 2 sessions, with session name "0" and "1" rather than just one seesion.
• Session "0" has the split windows, identical to what I saw in the command line version.
• Session "1" has a single full window.
• It stops at session "1".

So, in the config file version, I finally reach the session "1" on the screen. If I do an 'exit', and then attach session 0, then, it goes to session "0" with the same results as the command line version.

If, alternatively, the config file contains only the split line:

split-window -h

then when 'tmux' is typed, it shows an error message at the startup:

.tmux.conf:1: no current target 

And no split windows (since the split window command files, as we can see it complains the 1st line of the configuration has no current target.)

Apparently, command line version is what I want/need.

What's wrong with the config file version?

tmux behave differently between the command lines and equivalent config file (.tmux.conf)

command line:

bash$ tmux new \; split-window -h \;

config file (.tmux.conf), (and then, in the command line, we just type 'tmux')

new
split-window -h

The command line version nicely shows me a split window at the startup, and it creates only one session. However, the config file version behave differently:

• It creates 2 sessions, with session name "0" and "1" rather than just one seesion.
• Session "0" has the split windows, identical to what I saw in the command line version.
• Session "1" has a single full window.
• It stops at session "1".

So, in the config file version, I finally reach the session "1" on the screen. If I do an 'exit', and then attach session 0, then, it goes to session "0" with the same results as the command line version.

If, alternatively, the config file contains only the split line:

split-window -h

then when 'tmux' is typed, it shows an error message at the startup:

.tmux.conf:1: no current target 

And no split windows (since the split window command fails, as we can see it complains the 1st line of the configuration has no current target.)

Apparently, command line version is what I want/need.

What's wrong with the config file version?