Problem distinguishing between sessions named '1' and '10' #346
Comments
|
You can use = for exact match. |
|
Correct. This is intended default behaviour. For your purposes, see:
|
serban
added a commit
to serban/dotfiles
that referenced
this issue
Nov 12, 2018
See tmux/tmux#346. From the tmux man page: target-session is tried as, in order: 1. A session ID prefixed with a $. 2. An exact name of a session (as listed by the list-sessions command). 3. The start of a session name, for example `mysess' would match a session named `mysession'. 4. An fnmatch(3) pattern which is matched against the session name. If the session name is prefixed with an `=', only an exact match is accepted (so `=mysess' will only match exactly `mysess', not `mysession'). If a single session is found, it is used as the target session; multiple matches produce an error. If a session is omitted, the current session is used if available; if no cur- rent session is available, the most recently used is chosen.
|
This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs. |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
I have a session named '10' (and no session named '1'). The command
tmux has-session -t 1returns true. In addition to thistmux switch-client -t 1switches to session 10.This only happens if session '1' does not exist. Trying the same thing with an existing session '1' and a missing session '10' works fine.
I am using tmux 2.1.
The text was updated successfully, but these errors were encountered: