tmux.conf: Fix unknown key: confirm-before error message #94
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Quoting the man page tmux(1) of v3.1b: | Any other characters preceded by \ are replaced by themselves (that is, | the \ is removed) and are not treated as having any special meaning - so | for example \; will not mark a command sequence and \$ will not expand | an environment variable. and quoting the man page tmux(1) of v2.8: | Each command should be separated by spaces and a semicolon; commands are | executed sequentially from left to right and lines ending with a | backslash continue on to the next line, except when escaped by another | backslash. A literal semicolon may be included by escaping it with a | backslash (for example, when specifying a command sequence to bind-key). This implies that a backslash should also be escaped by a backslash but tmux still used to work with the unescaped backslash in older versions. This change has been tested with the tmux versions running Debian/jessie, Debian/stretch, Debian/buster and Debian/bullseye (currently testing): * Debian/jessie: v1.9 * Debian/stretch: v2.3 * Debian/buster: v2.8 * Debian/bullseye: v3.1 Closes: grml#93
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Quoting the man page tmux(1) of v3.1b:
| Any other characters preceded by \ are replaced by themselves (that is,
| the \ is removed) and are not treated as having any special meaning - so
| for example ; will not mark a command sequence and $ will not expand
| an environment variable.
and quoting the man page tmux(1) of v2.8:
| Each command should be separated by spaces and a semicolon; commands are
| executed sequentially from left to right and lines ending with a
| backslash continue on to the next line, except when escaped by another
| backslash. A literal semicolon may be included by escaping it with a
| backslash (for example, when specifying a command sequence to bind-key).
This implies that a backslash should also be escaped by a backslash but
tmux still used to work with the unescaped backslash in older versions.
This change has been tested with the tmux versions running
Debian/jessie, Debian/stretch, Debian/buster and Debian/bullseye
(currently testing):
Closes: #93