Historical errata for tmux

Around location 95 under the “Conventions” heading.

The first bullet point reads:
CTRL B means “press the Control and b keys simultaneously”

I think that should read:
CTRL b means “press the Control and b keys simultaneously”

since the next bullet point talks about CTRL R and that you won’t explicitly show the SHIFT key in the keystrokes

In the “Closing Panes” section, the command listed is “PREFIX X” but on my Mac running tmux 1.6 it seems the X needs to be lowercase.

In general the choice of font for the shortcut keys is confusing, especially with a small-caps version of Prefix right to the left.

Around location 270 under “Closing Panes”
says to kill a pane with “PREFIX X” but i have to use “PREFIX x” on ubuntu 11.10 using tmux 1.6

Around location 320 in the summary is states:
PREFIX W Displays a selectable list of windows in the current session

but I believe this should be
PREFIX w

PREFIX X to close a pane should be use x

It can then run the left side of the expression, which creates a new session with our username as the session’s name.
should be:
“right side”

In the mobipocket version of the book, it shows no difference between Ctrl-b and Ctrl-B keyboard shortcuts. Both show as CTRL B in “Kindle for PC” and "Mobipocket Reader 6.2) at least. Location 99 in Kindle.

In this line:
We can use color0 to color255

color should be written as colour (with a “u” in it), at least on my system (tmux 1.6 on Ubuntu 11.10), otherwise tmux says “bad colour”.

The text at the bottom of the page should contain >> but has been escaped to >&gt
—- [snip] —-
Back on the server, we add the key to the authorized_keys file.
tmux@puzzles$ cat id_rsa.pub >> ~/.ssh/authorized_keys

In PDF, almost last on page:

tmux@puzzles$ cat id_rsa.pub >> ~/.ssh/authorized_keys

“>” should be a “>”

“-v” splits vertically

tmux split-window -v -p 10 -t development
Splits the current window in the “development” session horizontally but sets its height to 10% of the total window size.

set -g default-command “reattach-to-user-namespace -l /bin/bash is missing a ” at the end

Closing Panes - “You can also kill a pane with PREFIX X” - that should be PREFIX x (lowercase).

Sorry for the duplicate submission. I seem to recall that in the past the PragProg errata submission links have included the relevant page number, and taken you to an erratum submission page that told you what errata had already been reported for the relevant book page and version. That was much better!

Resizing Panes - “We’ll use PREFIX h, PREFIX j, PREFIX k, and PREFIX l to change the size of the panes:” - those should be uppercase H, J, K and L, as shown in the bindings that follow.

For Future Reference section - a couple of small suggestions: (1) I think you should use the shorter form ‘new’ rather than ‘new-session’ here, as earlier you wrote that you would be doing that for the rest of the book; (2) over the page you tell us about PREFIX q - surprising, as we didn’t see this in the earlier section on panes. I guess that it relates to content in an earlier draft, and shouldn’t be in this summary section now.

In the “For Future Reference” section on this page, the sentence “Can be shortened to bind.” should be in the description of bind-key, not in the description of bind-key -r.

Provided .tmux.conf configuration file at first defines PREFIX h as select left pane
bind h select-pane -L
and then overrides PREFIX h as split panes in the same directory
bind h send-keys " ~/tmux-panes -v" C-m
It would be better not to use the same key - probably would be better to use different key for splitting panges in the same directory.

…kill a pane with Prefix X,

However, it should be a lowercase x (I think) since the uppercase X doesn’t seem to do anything.

hi there - great book - you probably want to unhtml escape the command:

tmux@puzzles$ cat id_rsa.pub >> ~/.ssh/authorized_keys

On various pages in the epub version, the line-height/leading on code examples gets messed up. It seems to happen when a block of code has to continue to the next page at the start of the 2nd page.

hxxp://i.imgur.com/Na2NY.jpg (page 71 of 126, chapter 3.1 in iBooks portrait)

The wget line for retrieving “colortest”, the “-O colortest” is not the same colour as the rest of the wget command

On Ubuntu 10.04.4 LTS (Lucid) the default version is missing features. In Update Manager -> Settings -> Updates choose "Unsupported updates (lucid-backports), then install the more up-to-date version using Synaptic or Aptitude.

Page number in PDF jumps from 31 - 34 with only one page between the two (specifically, the start of Chapter 3, which has no page number). Additionally, the header format changes from “outside-edge” alignment to inside-edge alignment when printed in booklet format.

The colouring of the word colortest (the -O option) in the wget statement is black when the rest of the wget command is rendered in purple. Ideally, it should be purple as well.

The default Homebrew build seems to use ‘Prefix x’ to kill a pane rather than ‘Prefix X’ as listed in the book.

The command at the top of the page (`tmuxinator open development`) starts editing a config file called ‘development.yml’, but the commands on the following page start using a project called ‘devproject’. With tmuxinator (version 0.5.0 at least) these commands result in an error “There’s no command or project ‘devproject’ in tmuxinator”.

The commands for maximizing and restoring panes throws errors (’Can’t find pane #n etc, and just spawns a new window)

Following along with book, section 1.5 will produce a warning/error

sessions should be nested with care. unset $TMUX to force.

Consider doing:

1: explaining the error, and warn about avoiding nesting
2. open a new window instead of a session
3. add instructions to close open session first before opening new one

or some combination of the above.

Ebook approx location 960
4.2 Copying and Pasting Text
3rd paragraph in

It says “To paste the contents we just captured, we switch to Copy mode and press PREFIX ].”

On my workstation (ubuntu 12.04, tmux 1.6) I do not have to enter Copy mode in order to paste. I only use PREFIX ]

I think the revised sentence should be:
“To paste the contents we just captured press PREFIX ].”

join-panes command needs to be fixed. It should be join-pane -s 1.1

On a fresh install of Mac OS X Lion, I installed Xcode and Homebrew, then ran “brew install tmux​​” as instructed. Homebrew reports: “Error: No available formula for tmux”. Maybe there’s a bug or change in the latest Homebrew? However, it’s simple to install from source yourself if you search online (no links allowed here in these comments). For example, ask Google about “Installing and setting up tmux on Mac OS Lion”.

the “has-session” example at the top of the page checks for the existance of a “remote” session, but creates (and connects) to a “development” session

“keeping in mind that while we set our windows to start with an index of one, our panes always start with an index of zero:”, this assertion is untrue since p.17 we set the “pane-base-index” option to 1 in order to “have some consistency between our pane and window numbering.”

The “join-pane -s 1.0” that follow is also wrong (but erratum #49386 already reported that problem.)

In 2.2 Customizing Keys, Commands, and User Input, the book says: “Not only is PREFIX % hard to press, as it involves
holding three keys, but without looking at the command reference, there’s no easy way to remember what it does”.

But it IS easy to remember. Look at the per cent sign. Clearly there is a bubble split in two with a slash!

This mnemonic could be mentioned.

Grep all occurrences for the word “simply” and remove 99% of them. Will make the book a hundred times better. We need to stop this “simply” epidemic before it kills all intelligent beings. Thanks.

The book says:
“We’ll set the horizontal split to PREFIX | and the vertical split to PREFIX - .”
and:
“At first glance, this may look backwards…”

It’s not just at first glance. The tmux terminology IS backwards. Vertical split is vertical not horizontal. You are right, tmux is wrong.

You don’t need to be apologetic about making sense! So don’t say “We’ll set the horizontal split to PREFIX | and the vertical split to PREFIX - .” because that is a lie.

Let’s save the human race together and take good care of our spines and always say how things are. Let’s not lie to please.

Repeat after me: “I’m not here to please others. I’m here for others”.

Thank you.

The -g flag is not necessary on server settings.

set -sg escape-time 1

should just be

set -s escape-time 1

remark to #49172 same here for source version 1.6 seems to be OS independent (luckily).

sidebar(para:2) seems to me that operating system should read
Window Manager or windows system (as OS has been defined as Linux in this scope).

bind -n became apperantely bind -r @ para 4 in code section
BTW why config/tmux.conf instead of ~/.tmux.conf here?

On page 23 you check for the emptiness of the $TMUX environment variable to determine if .bashrc (or friends) is executed inside tmux or not and set TERM to xterm-256color if that is not the case.

On page 65, you use the value of $TERM to do the same check again.

I believe that this is errorprone and brittle.
E.g. one might recall the value of $TERM incorrectly, as you
did in the text (set to term-256…, checking for screen-256…).
Would it not be preferable that you check for test -z “$TMUX” again on
page 65, or am I missing something in the context.

If that is the case, sorry for the noise.

The word “middle” is printed as “mid- dle” on page 31, “Working with Panes”, of the epub. (It is wrapped in the PDF, which is OK there.)

On Debian Wheezy (tmux 1.6), panes are closed with “Prefix x” instead of “Prefix X”.

“shorten” misspelled as “short- en” in the epub. (Wrapped in PDF.)

It says Prefix X to kill a window but really Prefix x seems to do it (lowercase).

“we switch to Copy mode and press PREFIX ].” - Maybe it’s just my setup, but I think it should read -
“we switch out of Copy mode and press PREFIX ].”

The paragraph, just after the first block of code reads “This means “Take window 1 of the The code tag should not be here. session and join it to the current window,” since we didn’t specify a target." I’m guessing “The code tag should not be here.” is intended as and editorial note.

To fire up …
$ tmuxinator development

should read

$ tmuxinator start development

Looks like some notes crept into the final text:

“This means “Take window 1 of the The code tag should not be here. session and join it to the current window,” since we didn’t specify a target."

very minor, but there is a stray period in the section “Moving Windows Between Session” in the text “press the key combination. and then”.

• CTRL - R means the same thing, except that you’ll need to use the SHIFT key to produce the capital “R.” I won’t explicitly show the SHIFT key in any of these keystrokes.

Based on the text and previous line I’d expect CTRL-B, not CTRL-R

The text contains: “The code tag should not be here.” which is obviously in error - probably some content would make more sense here. Please send me a short notice when this also gets fixed. Thanks :)

When customizing keys, I found that “bind - split-window -v” did NOT work unless I issued “unbind -” first.
tmux version 1.8 as included with iTerm2

Non-sensical sentence in section 6.1:

This means “Take window 1 of the The code tag should not be here. session and join it to the current window,” since we didn’t specify a target.

The text suggests to create the file ~/development (in $HOME) but the snippets from the script are titled config/development. I see that this is part of the URL to obtain the script but for someone with the paper book or a PDF Reader without hyperlinking capability this is confusing.

“Let’s write a simple script using these and
similar commands that creates a new tmux session and creates a window with a couple panes and a couple windows.”

The sentence references “window” twice and probably means two different things (X-Window and tmux-Window). I find this slightly confusing. For users coming from GNU screen there is the additional complication that a Window in screen is something different form a Window in tmux. I think screen windows are more like panes in tmux, but I’m not sure if it is that simple.

I think some clarification about “Window” (maybe in a ‘Joe asks’ box) could be helpful.

tmux send-keys -t development:1.0 ‘[keys]’ C-m

To be consistent with the convention in the book to use a
pane-base-index of 1 and the description this should be …ment:1.1 ‘[keys]’…

Also breaking the commands with hyphens could be confusing to beginners.

In fact, we can capture the current buffer to a text file like this:

It should be “current pane” instead of “current buffer”, because the command actually saves the pane (via the buffer) to a file.

“You’ll be presented with a list that looks like Figure 12, Choosing a buffer of text to insert, on page 49.”

Figure 12 doesn’t show the selection list but the situation after the selection has been made.

“This means “Take window 1 of the The code tag should not be here. session and join it to the current window,” since we didn’t specify a target."

I don’t think “The code tag should not be here.” should be there. =)

Escaped quote marks missing from OSX version of system-clipboard-to-tmux-buffer config code (halfway down page). Should read:

bind C-v run “tmux set-buffer \\”$(reattach-to-user-namespace pbpaste)\\“; tmux paste-buffer”

While explaining PREFIX-f, you could add that it not only finds windows with a certain name, but also finds/lists all windows that contain the given word anywhere (in an open text editor, as part of the shell prompt, in a debug output, etc.).

(Unrelated: Maybe you could also mention that tmux gets developed in openbsd, just to give some credit.)

Anyways, thanks for this great book; I really enjoy reading it!

The book states the default configuration of switch-client bindings are:

bind -r ( switch-client -p
bind -r ) switch-client -n

However, the -r is not part of the default config.

Typing exit in any Terminal window will close all the Terminal windows attached!

I believe this should read:
Typing exit in any Terminal window will close all of the Terminal windows attached!

Last Code Snippet cannot be copy/pasted. Paste result is:

set
set
set
set
-g
-g
-g
-g
pane-border-fg green
pane-border-bg black
pane-active-border-fg white
pane-active-border-bg yellow

In the paragraph discussing the synchronize-panes command, the sentence “… you can turn it off with set-window-option synchronize-panes on.” should be “… set-window-option synchronize-panes off.”

Lst paragraph. Text says that the panes in the following example drawing of a window with two panes are stacked horizontally.
It should say “vertically” since it’s a vertical split.

When I try to use the maximizing and restoring panes shortcuts, the screen just flips completely and I can’t see what I’m typing anymore. This is like that until I type exit and this is killed. The rest of my tmux session is normal then. I use tmux 1.9a. Is their an error in the Up and Down bindings? I copy pasted the rules in my .tmux.conf file and when I press C-a Up or Down. Everything is flipping.

tmuxinator can be used on computers without Ruby installed. In the last sentence on that page, it reads “it does require a Ruby interpreter on your machine though, so it may not be something you’ll set up on every environment where you’d like to use tmux.” However, (at least) the recent version of tmuxinator has the `tmuxinator debug` command, which will output the shell commands that are generated by tmuxinator. This output can then be copied to any machine lacking Ruby and executed in stead of `tmuxinator start`.

This is the correct url …/script.php?script_id=1349 instead of …/download_script.php?src_id=4568

Tmux can be installed now on windows OS (thought CygWin)

First install the CygWin software and then install the TMUX package from CygWin GUI

The section “Handling the Mouse” needs to be updated. In Tmux 2.1 the mouse options where changed, and it’s now only exist one option[1].

[1] raw.githubusercontent.com/tmux/tmux/master/CHANGES

Amazon “location” 867 (may be relative to my reader) - there are no PDF page numbers on Kindle version - sorry; Chapter 3, Section 2. In the file scripting/app.conf (both in the book and via the code download URL (medi…com/titles/bhtmux/code/scripting/app.conf) have the 7th line as:

send-keys -t development:1.1 ‘cd ~/work/devproject’ C-m

..if the intention is to have vim cd you need to send a ‘:’ to get into command mode (otherwise you get an error from vim), so it should probably be:

send-keys -t development:1.1 ‘:cd ~/work/devproject’ C-m

…with the colon before cd to get vim in command mode. At least that modification works on my machine taking the stock file from the url above. Maybe the author’s vim is set up to launch in command mode; mine apparently is not.

In scripting/app.conf, the line
“send-keys -t development:1.1 ‘cd ~/devproject’ C-m ”

sends the cd command to the first pane of the first window… which is vim! It should be “send-keys -t development:1.2 ‘cd ~/devproject’ C-m”, as properly said in the prior page.