Tag Info

New answers tagged

0

This question appeared closely related to another one previously posted, which hinted at the possible culprit: the 64-bit version of Cygwin. Indeed it has helped a countless number of users to install the 32bit version of Cygwin, which - in most of cases - made tmux and other applications work. Oddly enough, a sort of "derivative" of this bug was reported ...


0

Found a solution... which is probably not the best, but its working. Open tmux with: tmux -2 which force tmux to assume the terminal supports 256 colours.


1

You can use one of the five preset layout modes (tiled) to achieve this. From your starting point (a single vertical split), open a new pane, which by default will split the active pane and then arrange the panes into tiled mode: Ctrlb,Alt5 From man tmux: M-1 to M-5    Arrange panes in one of the five preset layouts: ...


3

Do you use systemd with socket activation for SSH? If so, there’s a known issue with that. According to the systemd proponents, this is actually a feature – systemd kills all processes spawned by a session when the session terminates. (I can see that being useful, but in the GNU screen, or tmux, case, you definitely don’t want that ☺ nor in most other cases ...


1

Found the culprit in .profile: xbacklight -set 10 Tmux is reading a file for new login shells whenever a new pane is created, because tmux sessions can in theory be joined by multiple ssh-based clients for example. These configuration lines do the trick, avoiding reading .profile: # Avoid spawning login shells and sourcing .profile # every time a new ...


2

Here's the list of default options that are taken from revision 1.51 of window-options.c in the tmux source from OpenBSD-current (this is the development version, sync'ed quite frequently with sourceforge). # Server options. buffer-limit 20 escape-time 500 exit-unattached 0 focus-events 0 message-limit 100 quiet 0 set-clipboard 1 terminal-overrides ...


0

tmux takes it defaults from the compiled in values, overruled by /etc/tmux.conf and then by ~/.tmux.conf. If the latter is not present it will just work with the other values. That means you can just delete the ~/.tmux.conf or leave it empty. Both on Ubuntu 12.04 nor on Linux Mint 17 there seems to be a default /etc/tmux.conf file (in which case the ...


0

If you were to put something like... export "PTTY=$(tty)" ...in your /etc/profile then for every new -login shell you would invoke (which is what generally happens when you open a new terminal window) that environment variable would be made available to all of its child processes - which should include tmux and all of its children. This should enable you ...


1

First of all check if setting variable ZLE_RPROMPT_INDENT to 0 helps. The default is 1. From zsh manual: ZLE_RPROMPT_INDENT If set, used to give the indentation between the right hand side of the right prompt in the line editor as given by RPS1 or RPROMPT and the right hand side of the screen. If not set, the value 1 is used.


1

This was bothering me as well, so I wrote a tmux plugin for this. It's not perfect, but can easily be extended to know how to safely kill most kinds of processes before exiting tmux: tmux-safekill


2

From `man tmux': STATUS LINE [...] By default, the window list shows the index, name and (if any) flag of the windows present in the current session in ascending numerical order. It may be customised with the window-status-format and window-status-current-format options. The flag is one of the following symbols appended to the window name: ...


1

Detach from currently attached session Session Ctrl+ b d or Ctrl+ b :detach Screen Ctrl+ a Ctrl+ d or Ctrl+ a :detach


1

Upgrade to tmux 1.9a which contains the following change making C-j the same as C-m: https://secure.freshbsd.org/commit/openbsd/8b7f9bdcbac2b1eb7c3a918af2cb7cd7c7b315e4


1

You may want to look at the answers to a similar question on the Superuser SE site, Can I re-attach SSH key forwarding through a disconnected Screen session. The answers are likely the same.


2

Your tmux session was started before your ssh agent was started, so the SSH_AUTH_SOCK and SSH_AGENT_PID variables are not set inside it. There are two ways to solve this. You can either copy those variables into the tmux session or run ssh-agent inside tmux to get them set, then run ssh-add to add the key to your ssh agent.


3

All terminal emulators that I've seen only let you resize the window in steps that correspond to the width of one character column. However, if your full-screen window width is not a multiple of the character width, there's not really anything you can do (other than choose a different font size to make it come better).


0

Inside your .zshrc, put [[ $TMUX = "" ]] && export TERM="xterm-256color" And, inside your .tmux.conf set -g default-terminal "screen-256color"


1

Tmux by default will only run one server process per user, and this server process can have multiple sessions. A Tmux client and the server communicate via a Unix domain socket in the /tmp directory. The -L option can be used to specify a different socket; a new server is created for each socket. Source: http://hyperpolyglot.org/multiplexers The tmux ...



Top 50 recent answers are included