# io.github.libtmux.Buffers.Buffers.EXACT_NAMED_DELETE

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

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.