# io.github.libtmux.Names

- **Module:** io.github.libtmux
- **Package:** io.github.libtmux:libtmux
- **Language:** Java
- **Kind:** class
- **Source:** https://github.com/libtmux/libtmux-java/blob/5f88402151ff08fc0390dd438b90963692ec3fe4/libtmux/src/main/java/io/github/libtmux/Names.java#L13
- **Page:** https://libtmux.org/en/java/latest/reference/io-github-libtmux-names-names/

What the running tmux does with a session or window name.

Exactly tmux 3.7 refuses a name containing {@code .} or {@code :}; 3.7a and later keep it and
earlier releases store {@code _} in its place. Refusing it here, before dispatch, keeps a batch or
a workspace build from running the commands ahead of the one tmux would reject.

## Members

### Other members

- [`require`](/en/java/latest/reference/io-github-libtmux-names-names-require/) (method): As {@link #require(String, TmuxVersion)}, for the daemon this server talks to, read without running a command that fires a user's hooks.