tmux for MobaXterm

An old friend meets a new friend: tmux for MobaXterm!

In a previous sysadmin life, I used tmux to good effect. Today, I’m using a Windows 8.1 system as my primary work desktop and recently got into MobaXterm for my Linux/terminal/X11 needs. While my most common usage scenario for tmux is invoking it on a remote server/VM instead of directly on my local machine, I thought it would be a good exercise to install tmux for local usage on MobaXterm and sharing that work by creating a plugin.

Download: tmux 1.9a for MobaXterm (tmux.mxt3)

tmux.mxt3 includes the following software:

The licenses for the above software is included within the mxt3 (zip) file.

For additional MobaXterm plugins and installation instructions, see the MobaXterm plugins page.

Additional credits:

5 thoughts to “tmux for MobaXterm”

  1. Thanks for a cool plugin. Haven’t used tmux in years, but it’s great to see it for MobaXterm. Now I just have to remind myself of all the commands. :)

    Note; I had a similar problem as Steve, where the .bashrc file wasn’t getting parsed by MobaXterm because all the stock commands were loaded after it (thus ignoring some commands that I put in there). By using the trick in the stackoverflow link, it solved my problem. Double win!

    Thanks for your hard work and a great plugin!

    1. Steve, if you’re still having this issue, check out the stackoverflow reference above. It definitely hit me too, and the solution was simple: source it from your .bash_profile file. .Bashrc runs BEFORE MobaXterm loads, so your changes are lost, but .bash_profile runs AFTER (essentially running it twice, but it works).

  2. Thank you for this plugin.
    I have a small problem : it seems that my bashrc file is not sourced by tmux.

    I put a .bashrc file in MobaXterm home directory (C:\Users\username\Documents\MobaXterm\home) which is sourced by MobaXterm at startup.
    But when I run tmux, another instance of Bash is run without sourcing my bashrc.
    I see it because my prompt changes and I have no more aliases.

    If I manually source this file : source $HOME/.bashrc, I get back my prompt, aliases, etc.
    So I guess it’s just a mather of initialization.

    Have you any clue about this?

Leave a Reply

Your email address will not be published. Required fields are marked *