# io.github.libtmux.Buffers.Buffers

- **Module:** io.github.libtmux.Buffers
- **Package:** io.github.libtmux:libtmux
- **Language:** Java
- **Kind:** class
- **Source:** https://github.com/libtmux/libtmux-java/blob/842228310449e879ebcaa3f910597757c9dbffd6/libtmux/src/main/java/io/github/libtmux/Buffers.java#L16
- **Page:** https://libtmux.org/en/java/latest/reference/io-github-libtmux-buffers-buffers/

The tmux server's paste buffers.

Buffers are the server's, not a session's: anything copied in one session can be pasted into
another. They are addressed by name rather than by the stack position tmux also accepts, because
a position moves whenever anything else is copied.

## Members

- `EXACT_NAMED_DELETE` (attribute): tmux's own history dates the fix to {@code 0f6227f4} ("When deleting or renaming a buffer and a buffer name is specified, complain if the buffer doesn't exist instead of silently deleting or renaming the most recent buffer", GitHub issue 3205); {@code git tag --contains} places it on {@code 3.4} and nothing earlier, so 3.3 and 3.3a both have the bug. Confirmed on the matrix: {@code set-buffer -b a x; set-buffer -b b y; delete-buffer -b nope} answers {@code unknown buffer: nope} on 3.4 and leaves both buffers, but on 3.3a it exits 0 and takes {@code b}, the one {@code delete-buffer} was never told to touch.
- `Buffers` (method)
- `list` (method): Captures every buffer the server holds, in tmux's order.
- `set` (method): Puts text in a named buffer, replacing whatever was there.
- `show` (method): What a buffer holds.
- `delete` (method): Removes a buffer by its exact name.
- `save` (method): Writes a buffer's contents to a file.
- `load` (method): Reads a file into a named buffer.