• Split handling of external dialogs into two scripts, to improve job control
• Added support for dialog as external menu handler
• Split Layouts menu into 3 sub menus
• moved "public IP" back to main
• Prevent styling from being used when tmux < 3.4

Tmux provides a few basic popup menus by default, but they're quite limited and difficult to extend due to their complex, mouse-based one-liner implementations. A more integrated, user-friendly approach with better navigation and flexibility seemed like the right solution.

Not solely meant for beginners, I use it myself all the time:

• When connecting using terminals without much support for Meta or Ctrl, this gives access to all the actions that aren't available with the regular shortcuts. For instance, when running the built in Terminal on MacOS the console keyboard is pretty limited.
• Tasks that would need external scripts to avoid hard-to-read complex bind one-liners, such as killing the current session without getting disconnected.
• When direct typing would be much longer. Example: Kill the server directly with 12 keys: <prefix> : kill-ser <tab> <enter> with the menus 5 keys: <prefix> \ A x y
• Actions used to seldom to be remembered as shortcuts.

Once installed, hit the trigger to get the main menu to pop up. The default is <prefix> \ see Configuration below for how to change it.

The grey one is generated with whiptail, as can be seen whiptail menus use a lot more screen real estate, however if they don't fit they can be scrollable unlike the tmux menus. The rest are generated by the tmux built-in display-menu

The above table covers compatibility for the general tool. Some menu items has a min tmux version set, if the running tmux doesn't match this, that item will be skipped. If it turns out that incorrect limits have been set on some feature, please let me know!

The easiest way to install tmux-menus is via the Tmux Plugin Manager.

1. Add plugin to the list of TPM plugins in .tmux.conf:

   set -g @plugin 'jaclu/tmux-menus'

2. Hit <prefix> I to install the plugin and activate it. The plugin should now be usable.

1. Clone the repository

   git clone https://github.com/jaclu/tmux-menus ~/clone/path

2. Add this line to the bottom of .tmux.conf

   run-shell ~/clone/path/menus.tmux

3. Reload the tmux environment

   # type this inside tmux
   $ tmux source-file ~/.tmux.conf

The plugin should now be activated.

For tmux < 3.0 the tmux featuredisplay-menu is not available.

If found whiptail or dialog will be used to display menus.

The preferred option is whiptail, but if not found dialog will be used instead. If neither is available, this plugin will abort displaying an error message.

Since these are full-screen apps, when either is used, the current (if any) task is suspended, dialogs are run, and when done the suspended task is reactivated.

The menu system works the same using external menu handlers, however the menu shortcuts are not as convenient, since they do not differentiate between upper and lower case letters, and does not at all support special keys like 'Left' or 'Home'

To use external dialog handling on modern tmuxes set this env variable:

• for whiptail use export TMUX_MENU_HANDLER=1
• for dialog use export TMUX_MENU_HANDLER=2

In most cases whiptail is installed by default on Linux distros. If not, install it using the package manager. One gotcha is that in the Red Hat universe the package is not called whiptail, the package containing whiptail is called newt.

MacOS does not come with whiptail, but it is available in the Homebrew package newt.

The default trigger is <prefix> \ The trigger is configured like this:

set -g @menus_trigger F12

Please note that non-standard keys, like the default backslash need to be prefixed with a \ like \\ in order not to confuse tmux.

In order to trigger menus without first hitting <prefix>

set -g @menus_without_prefix Yes

This param can be either Yes/true or No/false (the default)

The default locations are: C for tmux >= 3.2 P otherwise. If whiptail/dialog is used, menu location is ignored

set -g @menus_location_x W
set -g @menus_location_y S

For all location options see the tmux man page, search for display-menu. The basic options are:

By default menu items are cached, set this to No to disable all caching.

set -g @menus_use_cache No

To be more precise, items listed inside static_content() are cached. Some items need to be freshly generated each time a menu is displayed, those items are defines in dynamic_content() see scripts/pane_move.sh for an example of this. In that case, "Swap current pane with marked" is only displayed if there is a marked pane.

The plugin remembers what tmux version was used last time. If another version is detected as the plugin is initialized, the entire cache is dropped, so that the right version dependent items can be selected as the cache is re-populated. Same if a menu script is changed, if the script is newer than the cache, that cache item is regenerated.

See Styling.md

set -g @menus_config_file '~/.configs/tmux.conf'

In the main menu, the tmux config file to be reloaded. The default location for this is:

1. @menus_config_file - if this is defined in the tmux config file, it will be used.
2. $TMUX_CONF - if this is present in the environment, it will be used.
3. $XDG_CONFIG_HOME/tmux/tmux.conf - if $XDG_CONFIG_HOME is defined.
4. ~/.tmux.conf - Default if none of the above are set.

When a reload is requested, the conf file will be prompted for, defaulting to the first match above. It can be manually changed.

Per default logging is disabled. If this is desired, provide a log file name like this:

set -g @menus_log_file '~/tmp/tmux-menus.log'

tmux does not give any error if a menu doesn't fit the available screen, it just does not display the menu.

The only hint is that the menu is terminated instantaneously.

Since this test is far from perfect, and some computers are really slow, the current assumption is that if it was displayed < 0.5 seconds, it was likely due to screen size. In that case this error will be displayed on the status-bar:

tmux-menus ERROR: Screen might be too small

It will also be displayed if the menu is closed right away intentionally or unintentionally, so there will no doubt sometimes be false positives. If it doesn't happen the next time the menu is attempted, it can be ignored.

Each menu is a script, so can eaily be editrf it and once saved, the new content is displayed the next time that menu is triggered.

Rapid development with minimal fuzz!

If an edited menu fails to be displayed, run that menu from the command line, something like:

./items/sessions.sh

This directly triggers that menu and displays any syntax errors on the command line.

If @menus_log_file is defined, either in the tmux conf, or hardcoded in scripts/helpers.sh around line 289. Logging can be used in menus:

log_it "foo is now [$foo]"

If having two terminals with one tailing a log file is unpractical, setting the log file to /dev/stderr would essentially make it into echo. Choosing /dev/stderr instead of /dev/stdout avoids triggering errors if the log_it is called during string assignment.

Each item consists of at least two params

• min tmux version for this item, set to 0.0 if assumed to always work
• Type of menu item, see below
• Additional params depending on the item type

Item types and their parameters

• M - Open another menu
  • shortcut for this item, or "" if none wanted
  • label
  • menu script
• C - run tmux Command
  • shortcut for this item, or "" if none wanted
  • label
  • tmux command
• E - run External command
  • shortcut for this item, or "" if none wanted
  • label
  • external command
• T - Display text line
  • text to display. Any initial "-" (making it unselectable in tmux menus) will be skipped if whiptail is used, since a leading "-" would cause it to crash.
• S - Separator/Spacer line line
  • no params

#!/bin/sh

static_content() {
  # Be aware:
  #   'set -- \' creates a new set of parameters for menu_generate_part
  #   'set -- "$@" \' should be used when appending parameters

  set -- \
    0.0 M Left "Back to Main menu  $nav_home" "main.sh" \
    0.0 S \
    0.0 T "Example of a line extending action" \
    2.0 C "r" "Rename this session" "command-prompt -I '#S' \
        'rename-session -- \"%%\"'" \
    0.0 S \
    0.0 T "Example of action reloading the menu" \
    1.8 C "z" "Zoom pane toggle" "resize-pane -Z $menu_reload"

  menu_generate_part 1 "$@"
}

menu_name="Simple Test"

#  Full path to tmux-menux plugin
#  This script is assumed to have been placed in the items folder of
#  this repo, if not, D_TM_BASE_PATH needs to bechanged the path of the repo
D_TM_BASE_PATH="$(dirname -- "$(dirname -- "$(realpath "$0")")")"

# shellcheck source=scripts/dialog_handling.sh
. "$D_TM_BASE_PATH"/scripts/dialog_handling.sh

If whilst building the dialog, a break is needed, to check somecondition, just pause the set -- param assignments, do the check and then resume param assignment using set -- "$@"

Something like this:

...
    1.8 C z "Zoom pane toggle" "resize-pane -Z $menu_reload"

if tmux display-message -p '#{pane_marked_set}' | grep -q '1'; then
    set -- "$@" \
        2.1 C s "Swap current pane with marked" "swap-pane $menu_reload"
fi

set -- "$@" \
    1.7 C p "Swap pane with prev" "swap-pane -U $menu_reload" \
...

Contributions are welcome, and they're appreciated. Every little bit helps, and credit is always given.

The best way to send feedback is to file an issue