tmux Window Management commands do not work from conf file












0















I want to have automatically splitted panes when starting my tmux session. However though other commands work in my .tmux.conf, like set -g mouse on, every window or pane configuration command is ignored. If I try to run it using C-b : source-file ~/.tmux.conf, tmux just closes saying [exited].



uname -a:



Linux cristian-desktop 4.15.0-43-generic #46-Ubuntu SMP Thu Dec 6 14:45:28 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux


(running it from an ssh session on iTerm2 in OSX 10.14)



tmux -V:



tmux 2.6


cat .tmux.conf:



# session initialization

new -s SessionName -n WindowName 'ls'

splitw -h -p 50 -t 0 'uname -r'

selectw -t 0

# Enable mouse control (clickable windows, panes, resizable panes)

set -g mouse on


cat tmux-client-18536.log:



1546440595.157098 client started (18536): version 2.6, socket /tmp/tmux-1000/default, protocol 8

1546440595.158093 on Linux 4.15.0-43-generic #46-Ubuntu SMP Thu Dec 6 14:45:28 UTC 2018; libevent 2.1.8-stable (poll)

1546440595.158140 socket is /tmp/tmux-1000/default

1546440595.158162 trying connect

1546440595.158324 add peer 0x5644c29ee5e0: 6 ((nil))

1546440595.158434 sending message 100 to peer 0x5644c29ee5e0 (4 bytes)

1546440595.158456 sending message 101 to peer 0x5644c29ee5e0 (15 bytes)

1546440595.158469 sending message 102 to peer 0x5644c29ee5e0 (11 bytes)

1546440595.158483 sending message 108 to peer 0x5644c29ee5e0 (15 bytes)

1546440595.158499 sending message 104 to peer 0x5644c29ee5e0 (0 bytes)

1546440595.158513 sending message 107 to peer 0x5644c29ee5e0 (4 bytes)

1546440595.158527 sending message 105 to peer 0x5644c29ee5e0 (1516 bytes)

1546440595.158567 sending message 105 to peer 0x5644c29ee5e0 (27 bytes)

1546440595.158580 sending message 105 to peer 0x5644c29ee5e0 (52 bytes)

1546440595.158592 sending message 105 to peer 0x5644c29ee5e0 (34 bytes)

1546440595.158603 sending message 105 to peer 0x5644c29ee5e0 (21 bytes)

1546440595.158615 sending message 105 to peer 0x5644c29ee5e0 (24 bytes)

1546440595.158626 sending message 105 to peer 0x5644c29ee5e0 (13 bytes)

1546440595.158637 sending message 105 to peer 0x5644c29ee5e0 (20 bytes)

1546440595.158648 sending message 105 to peer 0x5644c29ee5e0 (19 bytes)

1546440595.158659 sending message 105 to peer 0x5644c29ee5e0 (14 bytes)

1546440595.158670 sending message 105 to peer 0x5644c29ee5e0 (19 bytes)

1546440595.158681 sending message 105 to peer 0x5644c29ee5e0 (20 bytes)

1546440595.158692 sending message 105 to peer 0x5644c29ee5e0 (17 bytes)

1546440595.158703 sending message 105 to peer 0x5644c29ee5e0 (35 bytes)

1546440595.158714 sending message 105 to peer 0x5644c29ee5e0 (65 bytes)

1546440595.158726 sending message 105 to peer 0x5644c29ee5e0 (23 bytes)

1546440595.158737 sending message 105 to peer 0x5644c29ee5e0 (23 bytes)

1546440595.158748 sending message 105 to peer 0x5644c29ee5e0 (19 bytes)

1546440595.158759 sending message 105 to peer 0x5644c29ee5e0 (24 bytes)

1546440595.158770 sending message 105 to peer 0x5644c29ee5e0 (20 bytes)

1546440595.158781 sending message 105 to peer 0x5644c29ee5e0 (16 bytes)

1546440595.158792 sending message 105 to peer 0x5644c29ee5e0 (8 bytes)

1546440595.158804 sending message 105 to peer 0x5644c29ee5e0 (25 bytes)

1546440595.158815 sending message 105 to peer 0x5644c29ee5e0 (17 bytes)

1546440595.158826 sending message 105 to peer 0x5644c29ee5e0 (54 bytes)

1546440595.158837 sending message 105 to peer 0x5644c29ee5e0 (31 bytes)

1546440595.158849 sending message 105 to peer 0x5644c29ee5e0 (134 bytes)

1546440595.158861 sending message 105 to peer 0x5644c29ee5e0 (30 bytes)

1546440595.158872 sending message 105 to peer 0x5644c29ee5e0 (32 bytes)

1546440595.158883 sending message 105 to peer 0x5644c29ee5e0 (20 bytes)

1546440595.158894 sending message 105 to peer 0x5644c29ee5e0 (16 bytes)

1546440595.158905 sending message 105 to peer 0x5644c29ee5e0 (16 bytes)

1546440595.158916 sending message 106 to peer 0x5644c29ee5e0 (0 bytes)

1546440595.158927 sending message 200 to peer 0x5644c29ee5e0 (4 bytes)

1546440595.158938 client loop enter

1546440595.166051 peer 0x5644c29ee5e0 message 207

1546440595.166063 sending message 208 to peer 0x5644c29ee5e0 (0 bytes)

1546440609.330112 peer 0x5644c29ee5e0 message 203

1546440609.330124 sending message 205 to peer 0x5644c29ee5e0 (0 bytes)

1546440609.330253 peer 0x5644c29ee5e0 message 204

1546440609.330259 client loop exit


I also asked the same question here.






window config tmux pane







share|improve this question





























    0















    I want to have automatically splitted panes when starting my tmux session. However though other commands work in my .tmux.conf, like set -g mouse on, every window or pane configuration command is ignored. If I try to run it using C-b : source-file ~/.tmux.conf, tmux just closes saying [exited].



    uname -a:



    Linux cristian-desktop 4.15.0-43-generic #46-Ubuntu SMP Thu Dec 6 14:45:28 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux


    (running it from an ssh session on iTerm2 in OSX 10.14)



    tmux -V:



    tmux 2.6


    cat .tmux.conf:



    # session initialization
    
new -s SessionName -n WindowName 'ls'
    
splitw -h -p 50 -t 0 'uname -r'
    
selectw -t 0
    
# Enable mouse control (clickable windows, panes, resizable panes)
    
set -g mouse on


    cat tmux-client-18536.log:



    1546440595.157098 client started (18536): version 2.6, socket /tmp/tmux-1000/default, protocol 8
    
1546440595.158093 on Linux 4.15.0-43-generic #46-Ubuntu SMP Thu Dec 6 14:45:28 UTC 2018; libevent 2.1.8-stable (poll)
    
1546440595.158140 socket is /tmp/tmux-1000/default
    
1546440595.158162 trying connect
    
1546440595.158324 add peer 0x5644c29ee5e0: 6 ((nil))
    
1546440595.158434 sending message 100 to peer 0x5644c29ee5e0 (4 bytes)
    
1546440595.158456 sending message 101 to peer 0x5644c29ee5e0 (15 bytes)
    
1546440595.158469 sending message 102 to peer 0x5644c29ee5e0 (11 bytes)
    
1546440595.158483 sending message 108 to peer 0x5644c29ee5e0 (15 bytes)
    
1546440595.158499 sending message 104 to peer 0x5644c29ee5e0 (0 bytes)
    
1546440595.158513 sending message 107 to peer 0x5644c29ee5e0 (4 bytes)
    
1546440595.158527 sending message 105 to peer 0x5644c29ee5e0 (1516 bytes)
    
1546440595.158567 sending message 105 to peer 0x5644c29ee5e0 (27 bytes)
    
1546440595.158580 sending message 105 to peer 0x5644c29ee5e0 (52 bytes)
    
1546440595.158592 sending message 105 to peer 0x5644c29ee5e0 (34 bytes)
    
1546440595.158603 sending message 105 to peer 0x5644c29ee5e0 (21 bytes)
    
1546440595.158615 sending message 105 to peer 0x5644c29ee5e0 (24 bytes)
    
1546440595.158626 sending message 105 to peer 0x5644c29ee5e0 (13 bytes)
    
1546440595.158637 sending message 105 to peer 0x5644c29ee5e0 (20 bytes)
    
1546440595.158648 sending message 105 to peer 0x5644c29ee5e0 (19 bytes)
    
1546440595.158659 sending message 105 to peer 0x5644c29ee5e0 (14 bytes)
    
1546440595.158670 sending message 105 to peer 0x5644c29ee5e0 (19 bytes)
    
1546440595.158681 sending message 105 to peer 0x5644c29ee5e0 (20 bytes)
    
1546440595.158692 sending message 105 to peer 0x5644c29ee5e0 (17 bytes)
    
1546440595.158703 sending message 105 to peer 0x5644c29ee5e0 (35 bytes)
    
1546440595.158714 sending message 105 to peer 0x5644c29ee5e0 (65 bytes)
    
1546440595.158726 sending message 105 to peer 0x5644c29ee5e0 (23 bytes)
    
1546440595.158737 sending message 105 to peer 0x5644c29ee5e0 (23 bytes)
    
1546440595.158748 sending message 105 to peer 0x5644c29ee5e0 (19 bytes)
    
1546440595.158759 sending message 105 to peer 0x5644c29ee5e0 (24 bytes)
    
1546440595.158770 sending message 105 to peer 0x5644c29ee5e0 (20 bytes)
    
1546440595.158781 sending message 105 to peer 0x5644c29ee5e0 (16 bytes)
    
1546440595.158792 sending message 105 to peer 0x5644c29ee5e0 (8 bytes)
    
1546440595.158804 sending message 105 to peer 0x5644c29ee5e0 (25 bytes)
    
1546440595.158815 sending message 105 to peer 0x5644c29ee5e0 (17 bytes)
    
1546440595.158826 sending message 105 to peer 0x5644c29ee5e0 (54 bytes)
    
1546440595.158837 sending message 105 to peer 0x5644c29ee5e0 (31 bytes)
    
1546440595.158849 sending message 105 to peer 0x5644c29ee5e0 (134 bytes)
    
1546440595.158861 sending message 105 to peer 0x5644c29ee5e0 (30 bytes)
    
1546440595.158872 sending message 105 to peer 0x5644c29ee5e0 (32 bytes)
    
1546440595.158883 sending message 105 to peer 0x5644c29ee5e0 (20 bytes)
    
1546440595.158894 sending message 105 to peer 0x5644c29ee5e0 (16 bytes)
    
1546440595.158905 sending message 105 to peer 0x5644c29ee5e0 (16 bytes)
    
1546440595.158916 sending message 106 to peer 0x5644c29ee5e0 (0 bytes)
    
1546440595.158927 sending message 200 to peer 0x5644c29ee5e0 (4 bytes)
    
1546440595.158938 client loop enter
    
1546440595.166051 peer 0x5644c29ee5e0 message 207
    
1546440595.166063 sending message 208 to peer 0x5644c29ee5e0 (0 bytes)
    
1546440609.330112 peer 0x5644c29ee5e0 message 203
    
1546440609.330124 sending message 205 to peer 0x5644c29ee5e0 (0 bytes)
    
1546440609.330253 peer 0x5644c29ee5e0 message 204
    
1546440609.330259 client loop exit


    I also asked the same question here.






    window config tmux pane







    share|improve this question



























      0












      0








      0








      I want to have automatically splitted panes when starting my tmux session. However though other commands work in my .tmux.conf, like set -g mouse on, every window or pane configuration command is ignored. If I try to run it using C-b : source-file ~/.tmux.conf, tmux just closes saying [exited].



      uname -a:



      Linux cristian-desktop 4.15.0-43-generic #46-Ubuntu SMP Thu Dec 6 14:45:28 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux


      (running it from an ssh session on iTerm2 in OSX 10.14)



      tmux -V:



      tmux 2.6


      cat .tmux.conf:



      # session initialization
      
new -s SessionName -n WindowName 'ls'
      
splitw -h -p 50 -t 0 'uname -r'
      
selectw -t 0
      
# Enable mouse control (clickable windows, panes, resizable panes)
      
set -g mouse on


      cat tmux-client-18536.log:



      1546440595.157098 client started (18536): version 2.6, socket /tmp/tmux-1000/default, protocol 8
      
1546440595.158093 on Linux 4.15.0-43-generic #46-Ubuntu SMP Thu Dec 6 14:45:28 UTC 2018; libevent 2.1.8-stable (poll)
      
1546440595.158140 socket is /tmp/tmux-1000/default
      
1546440595.158162 trying connect
      
1546440595.158324 add peer 0x5644c29ee5e0: 6 ((nil))
      
1546440595.158434 sending message 100 to peer 0x5644c29ee5e0 (4 bytes)
      
1546440595.158456 sending message 101 to peer 0x5644c29ee5e0 (15 bytes)
      
1546440595.158469 sending message 102 to peer 0x5644c29ee5e0 (11 bytes)
      
1546440595.158483 sending message 108 to peer 0x5644c29ee5e0 (15 bytes)
      
1546440595.158499 sending message 104 to peer 0x5644c29ee5e0 (0 bytes)
      
1546440595.158513 sending message 107 to peer 0x5644c29ee5e0 (4 bytes)
      
1546440595.158527 sending message 105 to peer 0x5644c29ee5e0 (1516 bytes)
      
1546440595.158567 sending message 105 to peer 0x5644c29ee5e0 (27 bytes)
      
1546440595.158580 sending message 105 to peer 0x5644c29ee5e0 (52 bytes)
      
1546440595.158592 sending message 105 to peer 0x5644c29ee5e0 (34 bytes)
      
1546440595.158603 sending message 105 to peer 0x5644c29ee5e0 (21 bytes)
      
1546440595.158615 sending message 105 to peer 0x5644c29ee5e0 (24 bytes)
      
1546440595.158626 sending message 105 to peer 0x5644c29ee5e0 (13 bytes)
      
1546440595.158637 sending message 105 to peer 0x5644c29ee5e0 (20 bytes)
      
1546440595.158648 sending message 105 to peer 0x5644c29ee5e0 (19 bytes)
      
1546440595.158659 sending message 105 to peer 0x5644c29ee5e0 (14 bytes)
      
1546440595.158670 sending message 105 to peer 0x5644c29ee5e0 (19 bytes)
      
1546440595.158681 sending message 105 to peer 0x5644c29ee5e0 (20 bytes)
      
1546440595.158692 sending message 105 to peer 0x5644c29ee5e0 (17 bytes)
      
1546440595.158703 sending message 105 to peer 0x5644c29ee5e0 (35 bytes)
      
1546440595.158714 sending message 105 to peer 0x5644c29ee5e0 (65 bytes)
      
1546440595.158726 sending message 105 to peer 0x5644c29ee5e0 (23 bytes)
      
1546440595.158737 sending message 105 to peer 0x5644c29ee5e0 (23 bytes)
      
1546440595.158748 sending message 105 to peer 0x5644c29ee5e0 (19 bytes)
      
1546440595.158759 sending message 105 to peer 0x5644c29ee5e0 (24 bytes)
      
1546440595.158770 sending message 105 to peer 0x5644c29ee5e0 (20 bytes)
      
1546440595.158781 sending message 105 to peer 0x5644c29ee5e0 (16 bytes)
      
1546440595.158792 sending message 105 to peer 0x5644c29ee5e0 (8 bytes)
      
1546440595.158804 sending message 105 to peer 0x5644c29ee5e0 (25 bytes)
      
1546440595.158815 sending message 105 to peer 0x5644c29ee5e0 (17 bytes)
      
1546440595.158826 sending message 105 to peer 0x5644c29ee5e0 (54 bytes)
      
1546440595.158837 sending message 105 to peer 0x5644c29ee5e0 (31 bytes)
      
1546440595.158849 sending message 105 to peer 0x5644c29ee5e0 (134 bytes)
      
1546440595.158861 sending message 105 to peer 0x5644c29ee5e0 (30 bytes)
      
1546440595.158872 sending message 105 to peer 0x5644c29ee5e0 (32 bytes)
      
1546440595.158883 sending message 105 to peer 0x5644c29ee5e0 (20 bytes)
      
1546440595.158894 sending message 105 to peer 0x5644c29ee5e0 (16 bytes)
      
1546440595.158905 sending message 105 to peer 0x5644c29ee5e0 (16 bytes)
      
1546440595.158916 sending message 106 to peer 0x5644c29ee5e0 (0 bytes)
      
1546440595.158927 sending message 200 to peer 0x5644c29ee5e0 (4 bytes)
      
1546440595.158938 client loop enter
      
1546440595.166051 peer 0x5644c29ee5e0 message 207
      
1546440595.166063 sending message 208 to peer 0x5644c29ee5e0 (0 bytes)
      
1546440609.330112 peer 0x5644c29ee5e0 message 203
      
1546440609.330124 sending message 205 to peer 0x5644c29ee5e0 (0 bytes)
      
1546440609.330253 peer 0x5644c29ee5e0 message 204
      
1546440609.330259 client loop exit


      I also asked the same question here.






      window config tmux pane







      share|improve this question
















      I want to have automatically splitted panes when starting my tmux session. However though other commands work in my .tmux.conf, like set -g mouse on, every window or pane configuration command is ignored. If I try to run it using C-b : source-file ~/.tmux.conf, tmux just closes saying [exited].



      uname -a:



      Linux cristian-desktop 4.15.0-43-generic #46-Ubuntu SMP Thu Dec 6 14:45:28 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux


      (running it from an ssh session on iTerm2 in OSX 10.14)



      tmux -V:



      tmux 2.6


      cat .tmux.conf:



      # session initialization
      
new -s SessionName -n WindowName 'ls'
      
splitw -h -p 50 -t 0 'uname -r'
      
selectw -t 0
      
# Enable mouse control (clickable windows, panes, resizable panes)
      
set -g mouse on


      cat tmux-client-18536.log:



      1546440595.157098 client started (18536): version 2.6, socket /tmp/tmux-1000/default, protocol 8
      
1546440595.158093 on Linux 4.15.0-43-generic #46-Ubuntu SMP Thu Dec 6 14:45:28 UTC 2018; libevent 2.1.8-stable (poll)
      
1546440595.158140 socket is /tmp/tmux-1000/default
      
1546440595.158162 trying connect
      
1546440595.158324 add peer 0x5644c29ee5e0: 6 ((nil))
      
1546440595.158434 sending message 100 to peer 0x5644c29ee5e0 (4 bytes)
      
1546440595.158456 sending message 101 to peer 0x5644c29ee5e0 (15 bytes)
      
1546440595.158469 sending message 102 to peer 0x5644c29ee5e0 (11 bytes)
      
1546440595.158483 sending message 108 to peer 0x5644c29ee5e0 (15 bytes)
      
1546440595.158499 sending message 104 to peer 0x5644c29ee5e0 (0 bytes)
      
1546440595.158513 sending message 107 to peer 0x5644c29ee5e0 (4 bytes)
      
1546440595.158527 sending message 105 to peer 0x5644c29ee5e0 (1516 bytes)
      
1546440595.158567 sending message 105 to peer 0x5644c29ee5e0 (27 bytes)
      
1546440595.158580 sending message 105 to peer 0x5644c29ee5e0 (52 bytes)
      
1546440595.158592 sending message 105 to peer 0x5644c29ee5e0 (34 bytes)
      
1546440595.158603 sending message 105 to peer 0x5644c29ee5e0 (21 bytes)
      
1546440595.158615 sending message 105 to peer 0x5644c29ee5e0 (24 bytes)
      
1546440595.158626 sending message 105 to peer 0x5644c29ee5e0 (13 bytes)
      
1546440595.158637 sending message 105 to peer 0x5644c29ee5e0 (20 bytes)
      
1546440595.158648 sending message 105 to peer 0x5644c29ee5e0 (19 bytes)
      
1546440595.158659 sending message 105 to peer 0x5644c29ee5e0 (14 bytes)
      
1546440595.158670 sending message 105 to peer 0x5644c29ee5e0 (19 bytes)
      
1546440595.158681 sending message 105 to peer 0x5644c29ee5e0 (20 bytes)
      
1546440595.158692 sending message 105 to peer 0x5644c29ee5e0 (17 bytes)
      
1546440595.158703 sending message 105 to peer 0x5644c29ee5e0 (35 bytes)
      
1546440595.158714 sending message 105 to peer 0x5644c29ee5e0 (65 bytes)
      
1546440595.158726 sending message 105 to peer 0x5644c29ee5e0 (23 bytes)
      
1546440595.158737 sending message 105 to peer 0x5644c29ee5e0 (23 bytes)
      
1546440595.158748 sending message 105 to peer 0x5644c29ee5e0 (19 bytes)
      
1546440595.158759 sending message 105 to peer 0x5644c29ee5e0 (24 bytes)
      
1546440595.158770 sending message 105 to peer 0x5644c29ee5e0 (20 bytes)
      
1546440595.158781 sending message 105 to peer 0x5644c29ee5e0 (16 bytes)
      
1546440595.158792 sending message 105 to peer 0x5644c29ee5e0 (8 bytes)
      
1546440595.158804 sending message 105 to peer 0x5644c29ee5e0 (25 bytes)
      
1546440595.158815 sending message 105 to peer 0x5644c29ee5e0 (17 bytes)
      
1546440595.158826 sending message 105 to peer 0x5644c29ee5e0 (54 bytes)
      
1546440595.158837 sending message 105 to peer 0x5644c29ee5e0 (31 bytes)
      
1546440595.158849 sending message 105 to peer 0x5644c29ee5e0 (134 bytes)
      
1546440595.158861 sending message 105 to peer 0x5644c29ee5e0 (30 bytes)
      
1546440595.158872 sending message 105 to peer 0x5644c29ee5e0 (32 bytes)
      
1546440595.158883 sending message 105 to peer 0x5644c29ee5e0 (20 bytes)
      
1546440595.158894 sending message 105 to peer 0x5644c29ee5e0 (16 bytes)
      
1546440595.158905 sending message 105 to peer 0x5644c29ee5e0 (16 bytes)
      
1546440595.158916 sending message 106 to peer 0x5644c29ee5e0 (0 bytes)
      
1546440595.158927 sending message 200 to peer 0x5644c29ee5e0 (4 bytes)
      
1546440595.158938 client loop enter
      
1546440595.166051 peer 0x5644c29ee5e0 message 207
      
1546440595.166063 sending message 208 to peer 0x5644c29ee5e0 (0 bytes)
      
1546440609.330112 peer 0x5644c29ee5e0 message 203
      
1546440609.330124 sending message 205 to peer 0x5644c29ee5e0 (0 bytes)
      
1546440609.330253 peer 0x5644c29ee5e0 message 204
      
1546440609.330259 client loop exit


      I also asked the same question here.






      window config tmux pane




      window config tmux pane






      share|improve this question















      share|improve this question













      share|improve this question




      share|improve this question








      edited Jan 2 at 15:09







      cduguet

















      asked Jan 2 at 15:03









      cduguetcduguet

      318216




      318216
























          0






          active

          oldest

          votes











          Your Answer






          StackExchange.ifUsing("editor", function () {
          StackExchange.using("externalEditor", function () {
          StackExchange.using("snippets", function () {
          StackExchange.snippets.init();
          });
          });
          }, "code-snippets");

          StackExchange.ready(function() {
          var channelOptions = {
          tags: "".split(" "),
          id: "1"
          };
          initTagRenderer("".split(" "), "".split(" "), channelOptions);

          StackExchange.using("externalEditor", function() {
          // Have to fire editor after snippets, if snippets enabled
          if (StackExchange.settings.snippets.snippetsEnabled) {
          StackExchange.using("snippets", function() {
          createEditor();
          });
          }
          else {
          createEditor();
          }
          });

          function createEditor() {
          StackExchange.prepareEditor({
          heartbeatType: 'answer',
          autoActivateHeartbeat: false,
          convertImagesToLinks: true,
          noModals: true,
          showLowRepImageUploadWarning: true,
          reputationToPostImages: 10,
          bindNavPrevention: true,
          postfix: "",
          imageUploader: {
          brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
          contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
          allowUrls: true
          },
          onDemand: true,
          discardSelector: ".discard-answer"
          ,immediatelyShowMarkdownHelp:true
          });


          }
          });














          draft saved

          draft discarded


















          StackExchange.ready(
          function () {
          StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f54008584%2ftmux-window-management-commands-do-not-work-from-conf-file%23new-answer', 'question_page');
          }
          );

          Post as a guest















          Required, but never shown

























          0






          active

          oldest

          votes








          0






          active

          oldest

          votes









          active

          oldest

          votes






          active

          oldest

          votes
















          draft saved

          draft discarded




















































          Thanks for contributing an answer to Stack Overflow!


          • Please be sure to answer the question. Provide details and share your research!

          But avoid …



          • Asking for help, clarification, or responding to other answers.

          • Making statements based on opinion; back them up with references or personal experience.


          To learn more, see our tips on writing great answers.




          draft saved


          draft discarded














          StackExchange.ready(
          function () {
          StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f54008584%2ftmux-window-management-commands-do-not-work-from-conf-file%23new-answer', 'question_page');
          }
          );

          Post as a guest















          Required, but never shown





















































          Required, but never shown














          Required, but never shown












          Required, but never shown







          Required, but never shown

































          Required, but never shown














          Required, but never shown












          Required, but never shown







          Required, but never shown







          Popular posts from this blog

          MongoDB - Not Authorized To Execute Command

          Image
          .everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty{ height:90px;width:728px;box-sizing:border-box; } 0 I have successfully enabled authorization on MongoDB and I have created an account on the admin database and then I created an account for my database called test. The following connection string to connect to my test database works successfully: mongo --host 192.168.17.52 --port 27017 -u user1 -p password --authenticationDatabase test Only problem I have now is, I cannot execute commands such as: show dbs. I get the following error when I try to do so: "errmsg" : "not authorized on admin to execute command { listDatabases: 1.0, lsid: { id: UUID("a1d5bc0d-bc58-485e-b232-270758a89455") }, $db: "admin...
          Read more

          in spring boot 2.1 many test slices are not allowed anymore due to multiple @BootstrapWith

          Image
          1 I tried to upgrade a yummy sandwich made of two test slices (@JsonTest and @JdbcTest in my case, crunchy test code in between) adding spring boot 2.1 flavour to it. But it seems it was not much of a success. I cannot annotate my tests with many @...Test since they are now each bringing their own XxxTestContextBootstrapper. It used to work when they all used same SpringBootTestContextBootstrapper. @RunWith(SpringRunner.class) @JdbcTest @JsonTest public class Test { @Test public void test() { System.out.printn("Hello, World !"); } } The error I get from BootstrapUtils is illegalStateException : Configuration error: found multiple declarations of @BootstrapWith for test class I understand I might be doing something wrong here but is there an easy way I could load both Json and Jdbc contex...
          Read more

          Npm cannot find a required file even through it is in the searched directory

          Image
          up vote 0 down vote favorite I got that error: users-Air:pdfuploader user$ npm run start client@0.1.0 start /Users/user/Documents/pdfuploader react-scripts start Could not find a required file. Name: index.html Searched in: /Users/user/Documents/pdfuploader/public npm ERR! code ELIFECYCLE npm ERR! errno 1 npm ERR! client@0.1.0 start: `react-scripts start` npm ERR! Exit status 1 npm ERR! npm ERR! Failed at the client@0.1.0 start script. npm ERR! This is probably not a problem with npm. There is likely additional logging output above. npm ERR! A complete log of this run can be found in: npm ERR! /Users/user/.npm/_logs/2018-11-19T10_19_14_555Z-debug.log users-Air:pdfuploader user$ And the file is in /Users/user/Documents/pdfuploader/public as you can see in my github repository: https://github.c...
          Read more