aboutsummaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorNicholas Marriott <nicholas.marriott@gmail.com>2009-01-10 15:25:44 +0000
committerNicholas Marriott <nicholas.marriott@gmail.com>2009-01-10 15:25:44 +0000
commit0e736bf3d76d3edd85b66e1f60f0efc350df94a5 (patch)
tree098c0446e946e04a0f2012595fe82c6834d37f8c
parent31509a8aa4383aee2219005bddb7252b5d7c2d57 (diff)
downloadrtmux-0e736bf3d76d3edd85b66e1f60f0efc350df94a5.tar.gz
rtmux-0e736bf3d76d3edd85b66e1f60f0efc350df94a5.tar.bz2
rtmux-0e736bf3d76d3edd85b66e1f60f0efc350df94a5.zip
Tweak some more.
-rw-r--r--FAQ11
1 files changed, 8 insertions, 3 deletions
diff --git a/FAQ b/FAQ
index 42a78f06..d3fefbc5 100644
--- a/FAQ
+++ b/FAQ
@@ -22,6 +22,11 @@ include as much of the following information as possible:
Please send feature requests by email to nicm@users.sourceforge.net.
+* Why do you use the screen termcap inside tmux? It sucks.
+
+It is already widely available. It is planned to change to something else
+such as xterm-color at some point, if possible.
+
* tmux freezes my terminal when I attach to a session. I even have to kill -9
the shell it was started from to recover!
@@ -65,10 +70,10 @@ attaching a client to a tmux session:
* How do I use a 256 colour terminal?
tmux will attempt to detect a 256 colour terminal both by looking at the Co
-termcap entry and, as this is broken on some platforms for some terminals such
-as xterm-256color, by looking for the string "256col" in the termcap name.
+termcap entry and, as this is broken for some terminals such as xterm-256color,
+by looking for the string "256col" in the termcap name.
-If both these methods failed, the -2 flag may be passed to tmux when attaching
+If both these methods fail, the -2 flag may be passed to tmux when attaching
to a session to indicate the terminal supports 256 colours.
* vim or $otherprogram doesn't display 256 colours. What's up?