1 ## What should I do before opening an issue?
3 Before opening an issue, please ensure that:
5 - Your problem is a specific problem or question or suggestion, not a general
8 - `$TERM` inside tmux is screen, screen-256color, tmux or tmux-256color. Check
9 by running `echo $TERM` inside tmux.
11 - You can reproduce the problem with the latest tmux release, or a build from
14 - Your question or issue is not covered [in the
15 manual](https://man.openbsd.org/tmux.1) (run `man tmux`).
17 - Your problem is not mentioned in [the CHANGES
18 file](https://raw.githubusercontent.com/tmux/tmux/master/CHANGES).
20 - Nobody else has opened the same issue recently.
22 ## What should I include in an issue?
24 Please include the output of:
27 uname -sp && tmux -V && echo $TERM
32 - Your platform (Linux, macOS, or whatever).
34 - A brief description of the problem with steps to reproduce.
36 - A minimal tmux config, if you can't reproduce without a config.
38 - Your terminal, and `$TERM` inside and outside of tmux.
40 - Logs from tmux (see below). Please attach logs to the issue directly rather
41 than using a download site or pastebin. Put in a zip file if necessary.
43 - At most one or two screenshots, if helpful.
45 ## How do I test without a .tmux.conf?
47 Run a separate tmux server with `-f/dev/null` to skip loading `.tmux.conf`:
50 tmux -Ltest kill-server
51 tmux -Ltest -f/dev/null new
54 ## How do I get logs from tmux?
56 Add `-vv` to tmux to create three log files in the current directory. If you can
57 reproduce without a configuration file:
60 tmux -Ltest kill-server
61 tmux -vv -Ltest -f/dev/null new
64 Or if you need your configuration:
73 - `tmux-server*.log`: server log file.
75 - `tmux-client*.log`: client log file.
77 - `tmux-out*.log`: output log file.
79 Please attach the log files to your issue.