Tmux - Revision history

Petingoso: Split blocks for more obvious reading

2026-02-10T18:44:49Z

Split blocks for more obvious reading

← Older revision		Revision as of 18:44, 10 February 2026
Line 22:		Line 22:
	=== Using Plugins ===		=== Using Plugins ===

			Tmux plugins can be also configured using <code>programs.tmux.plugins</code>. They can be found as NixOS packages: [https://search.nixos.org/packages?type=packages&query=tmuxPlugins tmuxPlugins]. Each of the tmux plugin is run via <code>run-shell</code> automatically.

	Tmux plugins can be also configured using <code>programs.tmux.plugins</code>. They can be found as NixOS packages: [https://search.nixos.org/packages?type=packages&query=tmuxPlugins tmuxPlugins]. Each of the tmux plugin is run via <code>run-shell</code> automatically.
	Some plugins need to be run after having had some custom configuration done>, but extraConfig gets executed after. For example <code>tmuxPlugins.cpu</code> needs the status line be declared before the plugin is run. For that scenario, <code>run-shell</code> can be added within <code>extraConfig</code>:		Some plugins need to be run after having had some custom configuration done>, but extraConfig gets executed after. For example <code>tmuxPlugins.cpu</code> needs the status line be declared before the plugin is run. For that scenario, <code>run-shell</code> can be added within <code>extraConfig</code>:
	<syntaxhighlight lang="nix">		<syntaxhighlight lang="nix">

Dangerflask: /* Global configuration */ Add trailing ; to code blocks

2025-12-11T13:19:22Z

Global configuration: Add trailing ; to code blocks

← Older revision		Revision as of 13:19, 11 December 2025
Line 14:		Line 14:
	...		...
	'';		'';
	}		};
	</syntaxhighlight>		</syntaxhighlight>

Line 33:		Line 33:
	run-shell ${pkgs.tmuxPlugins.cpu}/share/tmux-plugins/cpu/cpu.tmux		run-shell ${pkgs.tmuxPlugins.cpu}/share/tmux-plugins/cpu/cpu.tmux
	'';		'';
	}		};
	</syntaxhighlight>		</syntaxhighlight>

Pigs: Add category CLI Applications, link to pkgs

2025-05-17T16:56:40Z

Add category CLI Applications, link to pkgs

← Older revision		Revision as of 16:56, 17 May 2025
Line 1:		Line 1:
	''tmux'' is a "terminal multiplexer: it enables a number of terminals (or windows), each running a separate program, to be created, accessed, and controlled from a single screen. ''tmux'' may be detached from a screen and continue running in the background, then later reattached."		[https://github.com/tmux/tmux/wiki tmux] is a "terminal multiplexer: it enables a number of terminals (or windows), each running a separate program, to be created, accessed, and controlled from a single screen. ''tmux'' may be detached from a screen and continue running in the background, then later reattached."


	== Global configuration ==		== Global configuration ==

	''tmux'' can be configured globally from <code>/etc/nixos/configuration.nix</code>.		{{nixos:package\|tmux}} can be configured globally from <code>/etc/nixos/configuration.nix</code>.

	As an example:		As an example:
Line 44:		Line 44:
	* [https://wiki.archlinux.org/index.php/Tmux Arch Wiki page on tmux]		* [https://wiki.archlinux.org/index.php/Tmux Arch Wiki page on tmux]
	* [https://github.com/tmux/tmux tmux repository]		* [https://github.com/tmux/tmux tmux repository]

			[[Category:CLI Applications]]

Pigs: /* Using Plugins */Use current channel for search.nixos.org link

2025-05-07T16:55:40Z

Using Plugins: Use current channel for search.nixos.org link

← Older revision		Revision as of 16:55, 7 May 2025
Line 23:		Line 23:


	Tmux plugins can be also configured using <code>programs.tmux.plugins</code>. They can be found as NixOS packages: [https://search.nixos.org/packages?~~channel=24.11&from=0&size=50&sort=relevance&~~type=packages&query=tmuxPlugins tmuxPlugins]. Each of the tmux plugin is run via <code>run-shell</code> automatically.		Tmux plugins can be also configured using <code>programs.tmux.plugins</code>. They can be found as NixOS packages: [https://search.nixos.org/packages?type=packages&query=tmuxPlugins tmuxPlugins]. Each of the tmux plugin is run via <code>run-shell</code> automatically.
	Some plugins need to be run after having had some custom configuration done>, but extraConfig gets executed after. For example <code>tmuxPlugins.cpu</code> needs the status line be declared before the plugin is run. For that scenario, <code>run-shell</code> can be added within <code>extraConfig</code>:		Some plugins need to be run after having had some custom configuration done>, but extraConfig gets executed after. For example <code>tmuxPlugins.cpu</code> needs the status line be declared before the plugin is run. For that scenario, <code>run-shell</code> can be added within <code>extraConfig</code>:
	<syntaxhighlight lang="nix">		<syntaxhighlight lang="nix">

Mmkaram: Nixpkgs channel was old/unavailable, updated to 24.11

2025-02-13T02:52:21Z

Nixpkgs channel was old/unavailable, updated to 24.11

← Older revision		Revision as of 02:52, 13 February 2025
Line 23:		Line 23:


	Tmux plugins can be also configured using <code>programs.tmux.plugins</code>. They can be found as NixOS packages: [https://search.nixos.org/packages?channel=22.11&from=0&size=50&sort=relevance&type=packages&query=tmuxPlugins tmuxPlugins]. Each of the tmux plugin is run via <code>run-shell</code> automatically.		Tmux plugins can be also configured using <code>programs.tmux.plugins</code>. They can be found as NixOS packages: [https://search.nixos.org/packages?channel=24.11&from=0&size=50&sort=relevance&type=packages&query=tmuxPlugins tmuxPlugins]. Each of the tmux plugin is run via <code>run-shell</code> automatically.
	Some plugins need to be run after having had some custom configuration done>, but extraConfig gets executed after. For example <code>tmuxPlugins.cpu</code> needs the status line be declared before the plugin is run. For that scenario, <code>run-shell</code> can be added within <code>extraConfig</code>:		Some plugins need to be run after having had some custom configuration done>, but extraConfig gets executed after. For example <code>tmuxPlugins.cpu</code> needs the status line be declared before the plugin is run. For that scenario, <code>run-shell</code> can be added within <code>extraConfig</code>:
	<syntaxhighlight lang="nix">		<syntaxhighlight lang="nix">

Mic92: remove 404 link

2024-10-30T22:37:27Z

remove 404 link

← Older revision		Revision as of 22:37, 30 October 2024
Line 19:		Line 19:
	Note that <code>extraConfig</code> writes directly to <code>/etc/tmux.conf</code>		Note that <code>extraConfig</code> writes directly to <code>/etc/tmux.conf</code>

	~~There is a good example of [https://github.com/srid/nixos-config/blob/master/home/tmux.nix tmux configuration here].~~

	=== Using Plugins ===		=== Using Plugins ===


	Tmux plugins can be also configured using <code>programs.tmux.plugins</code>. They can be found as NixOS packages: [https://search.nixos.org/packages?channel=22.11&from=0&size=50&sort=relevance&type=packages&query=tmuxPlugins tmuxPlugins]. Each of the tmux plugin is run via <code>run-shell</code> automatically.		Tmux plugins can be also configured using <code>programs.tmux.plugins</code>. They can be found as NixOS packages: [https://search.nixos.org/packages?channel=22.11&from=0&size=50&sort=relevance&type=packages&query=tmuxPlugins tmuxPlugins]. Each of the tmux plugin is run via <code>run-shell</code> automatically.
	Some plugins need to be run after having had some custom configuration done>, but extraConfig gets executed after. For example <code>tmuxPlugins.cpu</code> needs the status line be declared before the plugin is run. For that scenario, <code>run-shell</code> can be added within <code>extraConfig</code>:		Some plugins need to be run after having had some custom configuration done>, but extraConfig gets executed after. For example <code>tmuxPlugins.cpu</code> needs the status line be declared before the plugin is run. For that scenario, <code>run-shell</code> can be added within <code>extraConfig</code>:

imported>Crodjer at 15:38, 15 May 2023

2023-05-15T15:38:23Z

← Older revision		Revision as of 15:38, 15 May 2023
Line 20:		Line 20:

	There is a good example of [https://github.com/srid/nixos-config/blob/master/home/tmux.nix tmux configuration here].		There is a good example of [https://github.com/srid/nixos-config/blob/master/home/tmux.nix tmux configuration here].

			=== Using Plugins ===
			Tmux plugins can be also configured using <code>programs.tmux.plugins</code>. They can be found as NixOS packages: [https://search.nixos.org/packages?channel=22.11&from=0&size=50&sort=relevance&type=packages&query=tmuxPlugins tmuxPlugins]. Each of the tmux plugin is run via <code>run-shell</code> automatically.
			Some plugins need to be run after having had some custom configuration done>, but extraConfig gets executed after. For example <code>tmuxPlugins.cpu</code> needs the status line be declared before the plugin is run. For that scenario, <code>run-shell</code> can be added within <code>extraConfig</code>:
			<syntaxhighlight lang="nix">
			programs.tmux = {
			enable = true;
			extraConfig = ''
			...
			set -g status-right '#[fg=black,bg=color15] #{cpu_percentage}  %H:%M '
			run-shell ${pkgs.tmuxPlugins.cpu}/share/tmux-plugins/cpu/cpu.tmux
			'';
			}
			</syntaxhighlight>

	== Per-user configuration ==		== Per-user configuration ==

imported>Crodjer: The option is called `extraConfig` and not `extraTmuxConf`

2023-05-15T13:28:38Z

The option is called `extraConfig` and not `extraTmuxConf`

← Older revision		Revision as of 13:28, 15 May 2023
Line 11:		Line 11:
	enable = true;		enable = true;
	clock24 = true;		clock24 = true;
	~~extraTmuxConf~~ = '' # used for less common options, intelligently combines if defined in multiple places.		extraConfig = '' # used for less common options, intelligently combines if defined in multiple places.
	...		...
	'';		'';
Line 17:		Line 17:
	</syntaxhighlight>		</syntaxhighlight>

	Note that <code>~~extraTmuxConf~~</code> writes directly to <code>/etc/tmux.conf</code>		Note that <code>extraConfig</code> writes directly to <code>/etc/tmux.conf</code>

	There is a good example of [https://github.com/srid/nixos-config/blob/master/home/tmux.nix tmux configuration here].		There is a good example of [https://github.com/srid/nixos-config/blob/master/home/tmux.nix tmux configuration here].

imported>Gkb: Replace outdated link with the updated one.

2022-11-24T02:46:26Z

Replace outdated link with the updated one.

← Older revision		Revision as of 02:46, 24 November 2022
Line 19:		Line 19:
	Note that <code>extraTmuxConf</code> writes directly to <code>/etc/tmux.conf</code>		Note that <code>extraTmuxConf</code> writes directly to <code>/etc/tmux.conf</code>

	~~Example:~~ https://github.com/srid/~~nix~~-config/blob/master/~~nixos~~/tmux.nix		There is a good example of [https://github.com/srid/nixos-config/blob/master/home/tmux.nix tmux configuration here].

	== Per-user configuration ==		== Per-user configuration ==

imported>Srid: update link to example

2020-12-16T19:05:20Z

update link to example

← Older revision		Revision as of 19:05, 16 December 2020
Line 18:		Line 18:

	Note that <code>extraTmuxConf</code> writes directly to <code>/etc/tmux.conf</code>		Note that <code>extraTmuxConf</code> writes directly to <code>/etc/tmux.conf</code>

			Example: https://github.com/srid/nix-config/blob/master/nixos/tmux.nix

	== Per-user configuration ==		== Per-user configuration ==

	However, if you want to configure per user, you could use [[Home Manager]]. This also grants you with more options available directly through nix, as opposed to through an extra config option. Though it should be noted that a few of the options have different names.		However, if you want to configure per user, you could use [[Home Manager]]. This also grants you with more options available directly through nix, as opposed to through an extra config option. Though it should be noted that a few of the options have different names.

	~~Example: https://github.com/srid/nix-config/blob/master/nix/home/tmux.nix~~

	== See also ==		== See also ==