When comparing KiTTY vs tmux, the Slant community recommends KiTTY for most people. In the question“What are the best terminal emulators for Windows?” KiTTY is ranked 5th while tmux is ranked 15th. The most important reason people chose KiTTY is:
- Sessions filter - Shortcuts for pre-defined command - The session launcher - Automatic logon script - URL hyperlinks - Running a locally saved script on a remote session - Send to tray - Transparency - Quick start of a duplicate session - SSH Handler: Internet Explorer integration - pscp.exe and WinSCP integration - New command-line options
Specs
Ranked in these QuestionsQuestion Ranking
Pros
Pro Includes additional features over PuTTy
- Sessions filter
- Shortcuts for pre-defined command
- The session launcher
- Automatic logon script
- URL hyperlinks
- Running a locally saved script on a remote session
- Send to tray
- Transparency
- Quick start of a duplicate session
- SSH Handler: Internet Explorer integration
- pscp.exe and WinSCP integration
- New command-line options
Pro Startup sessions
Support start-up sessions which allow you to specify the window/tab layout, working directories, and programs to run on startup.
Pro Source Code Available
Source code is available so you could modify or review changes.
Pro Can store login credentials
Ability to store passwords/passphrases locally.
Pro Clickable URLs
URLs are parsed and can be clicked.
Pro Auto login script
Automatic processing of commands after conncetion was made.
Pro True Color support
Supports True Color, so software like Vim can display a really nice pallet.
Pro Portable version available
Pro Background image
Ability to overlay the terminal background with an image.
Pro Unicode
Uses Unicode for the best character compatibility.
Pro Easily split panes
There is a keyboard shortcut that makes it easy to split a window and create more panes.
Pro Windows linked to sessions
tmux calls the individual shell instances windows. They are displayed like tabs in the status line. These windows can be shared between different sessions, so that any given shell instance can be in any number of tmux sessions used for different purposes or by different users. This allows configurations like the following example: User A: wAB, wA1, wA2; User B: wB1, wAB, wB2
Pro Preserve the state
As long as you don't close your session, you may even lose your SSH connection, it'll keep your state just as it was. So you can resume where you left off (via tmux attach
).
Pro Maximize screen space
As a tiling window manager, it'll make use of all the space. As you have multiple workspaces and you can resize, etc. you can adjust to see what matters most.
Pro Frequently updated
Tmux is in a state of constant development. Updates are frequent and bug reports usually get an answer within days.
Pro Customizable
Open ~/.tmux.conf to get started. You can customize keybindings, the bottom status bar, color schemes, the clock screen, your time zone, and more.
Pro Mouse support
Mouse support can optionally be enabled, allowing e.g. scrolling with the mouse wheel, or switching panes with mouse clicks.
Pro Only need to learn a few keyboard shortcuts and commands to make much headway
Cons
Con No centralized configuration
Each session holds its own configuration of all features. This means that if one wants to change a configuration common to all sessions (say, the terminal font), it has to be changed in each stored session separately.
A better solution would be to have a default configuration and store only the changed elements for each session (both configurations would be merged, with e priority on the specific one).
Con No tabbed sessions
No built-in support for tabbed sessions. Requires an add-on.
Con No mouse support in alternative screens
Like vim, less, etc.
Con Poorly designed key binding
Counter-intuitive keyboard shortcuts make tmux very hard to use and learn.
Con Bad scrolling support
Con No builtin telnet or serial support
It's considered bloat by the maintainers and for this reason there's no builtin support for them.