Talk:Tmux
New Tmux terminfo
I suggest changing all references to screen
or screen-256color
to tmux
and tmux-256color
as the new terminfo has been added to ncurses 6 (now in stable in Arch). You can find the announcement at http://invisible-island.net/ncurses/NEWS.html#index-t20150502 (the 6th point), or confirm by yourself by going to /usr/share/terminfo/t/. This mainly fixes the italic issue referenced here: https://wiki.archlinux.org/index.php/Tmux#Fix_reverse-video.2Fitalic_mode_in_urxvt. ~ Nicop06
- Agreed jasonwryan (talk) 23:57, 18 October 2015 (UTC)
- Actually, it seems that the
screen-256color
terminfo is working since the upgrade to nurses 6. I suggest completly removing the section to avoid any confusion. Nicop06 (talk) 21:38, 5 January 2016 (UTC)
- Actually, it seems that the
- I've been using
TERM=tmux-256color
since the update. Overall things work, but there are some places and programs which have issues with it. The most common one is prezto (zsh config) doesn't use color for a lot of commands. I believe it fails to detect if term has color and falls back to color-less command arguments. I just filed a bug report for prezto. There were some other issues which I can't remember right now. Maybe some info notice should be added about this. MaikuMori (talk) 09:15, 6 January 2016 (UTC)
- I've been using
- So it turned out it's not a bug in
prezto
, butcoreutils
. It's tracked here. The fix will be incoreutils-8.25
. After that's fixed I see no reason to not useTERM=tmux-256color
everywhere. My 2c. MaikuMori (talk) 21:45, 29 January 2016 (UTC)
- So it turned out it's not a bug in
- Arch is using coreutils 8.30-1 now, let's move to
tmux-256color
? --Noraj (talk) 11:21, 12 September 2018 (UTC)
- Arch is using coreutils 8.30-1 now, let's move to
X clipboard integration
I updated the config options to be pasted into `tmux.conf` according to the new mode-table names in tmux. The old ones didn't work for me in vi-mode while the new ones do.
Can somebody check the emacs ones? I'm not sure about those. --jakobh ✉ 16:10, 1 March 2017 (UTC)
Tips and tricks
Can I add this section under Tips and tricks on the wiki?
# More friendly split pane bind-key h split-window -h bind-key v split-window -v
--Noraj (talk) 11:24, 12 September 2018 (UTC)
- The description should be more descriptive than "More friendly split pane" - what is it actually doing? And the comment should be in the surrounding text, not in the code block. -- Lahwaacz (talk) 13:28, 12 September 2018 (UTC)
- That was what is was going to do, you can now take a look at it [1].--Noraj (talk) 18:51, 12 September 2018 (UTC)
beware of 'exec tmux' if using Midnight Commander(without --nosubshell)
Because mc
will run bash interactive like bash -rcfile .bashrc
this means exec tmux
also gets executed and thus create a small startup delay when running mc
(and who knows what else). To test that mc
does this, in ~/.bashrc
after this line [[ $- != *i* ]] && return
just add [[ -n "$MC_SID" ]] && echo "ran by 'mc' $MC_SID" >>/tmp/b
and in another terminal run tail -F /tmp/b
. To workaround this, only exec tmux
if both MC_SID
and TMUX
env. vars are empty, ie. this [[ -z "$TMUX" ]] && exec tmux
should probably be [[ -z "$TMUX" && -z "$MC_SID" ]] && exec tmux
. Tested Midnight Commander 4.8.24-84-gcef0bb013, tmux 3.1a. Gentoo eshoes (talk) 01:27, 2 May 2020 (UTC)
256 colors
As of tmux 2.1, this is now tmux, or tmux-256color.
I couldn't find the relevant change in the changelog. Further, setting this to tmux-256color
didn't work for me on termite with tmux 3.1_b-1.
Although, using xterm-256color
worked fine.
MrHritik (talk) 23:33, 15 October 2020 (UTC)
Autostart with systemd
After setting this up, I was not able to run certain commands as shown below, apparently because I lost access to dbus. If it's not a problem, I'd suggest adding a note.
$ reboot Failed to set wall message, ignoring: Interactive authentication required. Failed to reboot system via logind: Interactive authentication required. Failed to talk to init daemon. $ $ systemctl --user Failed to connect to bus: No medium found $ $ alsamixer cannot open mixer: Host is down $ $ speaker-test speaker-test 1.2.6 Playback device is default Stream parameters are 48000Hz, S16_LE, 1 channels Using 16 octaves of pink noise Playback open error: -112,Host is down $ $ pactl list sinks Connection failure: Connection refused pa_context_connect() failed: Connection refused $
—This unsigned comment is by Funcrab (talk) 11:40, 17 January 2022. Please sign your posts with ~~~~!