Skip to main content

optionally run several commands when starting tmux


I have a ~/.tmux/dev file which looks like this:


selectp -t 0    # select the first pane
splitw -h -p 50 # split it into two halves

selectp -t 1    # select the new, second (1) pane
splitw -v -p 50 # split it into two halves

selectp -t 0    # go back to the first pane
send-keys 'vim .' Enter

If I run tmux source-file ~/.tmux/dev from inside a tmux session, it works fine.


I want to create a bash script that opens tmux and automatically runs those commands.


I tried running


tmux new 'tmux source-file ~/.tmux/dev'

but I only see two panes; the pane with vim is missing.


I have read How do I get tmux to open up a set of panes without manually entering them?, but before installing a tool for managing tmux configs, I would like to grok what's happening here.


Thanks in advance for any light you can shed on the subject.



Answer



This is what is happening:




  1. tmux new 'tmux source-file ~/.tmux/dev'


    The new commands creates a new session with a single window that has a single pane. The command tmux source-file ~/.tmux/dev runs in this new pane.



    • So, you have a new session N (where N is some number), with

    • a single window N:0 (or whatever you have base-index set to), with

    • a single pane N:0.0 (or whatever you have base-pane-index set to),

    • running the command tmux source-file ~/.tmux/dev.




  2. The source-file command is processed.



    1. The extra panes are added.

    2. Pane 0 is (re)selected.

    3. The send-keys command then “types” vim . + Enter at pane 0.
      This input is ignored because this pane is just running the tmux client that sent the source-file command.



  3. The tmux client exits, thus closing pane 0.


So the unexpected bit is that pane 0 (i.e. N:0.0) is running (only) the source-file command which ignores your “typed” command. This pane never runs an interactive shell that could interpret the “typed” command.


There are at least a couple of ways you can fix this:




  • Start ~/.tmux/dev with new-window so that pane 0 is running your “default command” (i.e. probably an interactive shell).


    This method has the benefit of not assuming that your current pane is running an interactive shell, and also not assuming that the current pane is 0 (i.e. what happens if you run your original series of commands against a pane that is part of an already split window?). It means you can safely bind source-file ~/.tmux/dev to a key that you can run in any context (since it creates a new window for all of its panes). From the shell you can run either tmux source-file ~/.tmux/dev (to create a new window in the current session), or your original tmux new 'tmux source-file ~/.tmux/dev' to create a new session.


    A minor drawback to this method is that when you run tmux new 'tmux source-file ~/.tmux/dev', the initial window will still run the client that sends source-file and exit fairly quickly. This means that your “main window” (the one with the splits) will be one higher than your base-index and a future new window will be placed before the “main window”. You could fix this by using something like this:


    tmux new 'tmux move-window -t 99 \; source-file ~/.tmux/dev'

    It moves the (ephemeral) initial window to a high index so that the new-window in ~/.tmux/dev will end up at base-index.




  • Use (e.g.) tmux new 'tmux source-file ~/.tmux/dev ; zsh -l' so that the pane ends up running an interactive shell after the source-file command finishes.


    The ugly bit about this is that you end up “hard coding” your preferred shell into this command. Also, the send-keys input (vim . + Enter) is technically sent before the shell starts; this is probably okay, but may not always be completely reliable.


    You could avoid “hard coding” your shell by querying tmux for the default-command (or if that is not set, default-shell (or if that is not set, using SHELL)), but that may be more work than you really want to do.




Comments

Post a Comment

Popular Posts

keyboard - Is there any utility/method to change Windows key bindings to type rare chars to currently empty bindings?

I'm currently typing this post with my windows XP machine and (Spanish) keyboard, and I'd like to add some extra symbols to my text. I could open the "char map" windows utility, look for the desired symbols, and paste them. But I'd like something quickier. For example, when I'm using my OSX Mac at work, I can easily add a ©, ™, ® or similar symbols, just pressing some weird ALT-GR + G / H / J, key combinations. In my (Spanish) keyboard mapping, these combinations are empty, as they don't produce any char at all, which, on the other hand, is perfectly normal and desirable. So, I thought: Why couldn't I add some extra key mappings on top of my currently empty ALT-GR + G/J/H Keys in my Spanish keyboard, and thus, being able to quickly type these special symbols? So that's my question: Is there any utility/method to achieve that effect under windows? (My version is XP). I've even googled this for some time but no luck. I've been a long term Hot...
Post a Comment
Read more

virtualization - How to select paravirtualization interface in VirtualBox?

Given a windows 8 host system (Intel Core i5) and a Linux Fedora host, I would like to determine the optimal setting for the paravirtual interface. Options are none Default Legacy minimal Hyper-V KVM This page suggest the selection is only based on the guest system: The biggest change in VirtualBox 5.0 is the introduction of paravirtualization support, bringing higher performance and time-keeping accuracy to supported guest operating systems (Hyper-V on Windows and KVM on Linux). Is that correct? Answer The VirtualBox Manual , in the section titled Paravirtualization providers explains very clearly when each should be used (emphasis added): Minimal: Announces the presence of a virtualized environment. Additionally, reports the TSC and APIC frequency to the guest operating system. This provider is mandatory for running any Mac OS X guests. KVM: Presents a Linux KVM hypervisor interface which is recognized by Linux kernels starting with version 2.6.25. VirtualBox's implementati...
Post a Comment
Read more

Desktop reboots itself on sleep or hibernate

I have been using an ASUS M2NPV-VM motherboard for main home desktop workstation, operating Windows Vista x64. This computer has right from day one not been able to enter hibernate or standby; after Windows performs its final actions and brings the machine down, it would automatically revive itself for a reboot. Updating to the second latest BIOS (1201)has not helped (the latest BIOS revision would induce video refresh problems rendering it unusable). I have been reading related discussions on incidents similar to mine to no avail of a true workable solution. They appear to be more speculative guesses rather than actual knowledge on the inner workings of motherboard hardware. Does anybody have any electronic engineering experience on PC energy-saving standards to provide a more informed opinion how to go about getting this to work? More stories: this motherboard could not even reboot properly the first thing i used it. It was due to refresh rate of the onboard GPU, which had no influe...
Post a Comment
Read more

security - How is Linux not prone to viruses, malware and those kinds of things?

How is Linux protected against viruses? This question was a Super User Question of the Week . Read the blog entry for more details or contribute to the blog yourself Answer Well, it factually is not... it's just less subject to hackers developing viruses that target Linux systems. Consumer grade computers usually run on Windows and thus, when targeting a wide audience, Windows is the way to go. Don't misunderstand Linux and viruses, there definitely ARE Linux viruses. Some distros have additional protection layers such as SELinux (See here ) in Ubuntu for example. Then there's the default firewall and the fact that alien files don't automatically have permission to be executed. Specific execution permission has to be granted before execution is possible. (See here ) Then there are several other factors that make Linux a hard place to be for viruses usually non-root users on linux systems have no to little executable files at their disposal that would allow for virus...
Post a Comment
Read more