Repository navigation
libtmux 0.66.0 makes two narrow breaking changes: files Server.save_buffer() creates are readable by their owner only, and Pane.send_keys() with hex_keys=True no longer adds Enter. A socket path too long for tmux now raises SocketPathTooLong, saying how far over the limit it is and where the length came from.
Highlights
- Owner-only
save_bufferfiles. A new fileServer.save_buffer()writes is readable and writable by its owner only. It used to follow the process umask, so saved scrollback and paste buffers were usually readable by every local user. A file that already exists keeps its permissions; callpath.chmod(0o644)after saving to share a new one (#903). - Hex keys without Enter.
Pane.send_keys(..., hex_keys=True)sends only the bytes you give it, so an escape sequence or partial keystroke no longer runs the line. Passenter=Trueto keep the old behaviour. Calls withouthex_keysstill send Enter by default, andenter=Falseandenter=Nonemean what they did (#904). SocketPathTooLong. A socket path too long for a UNIX socket raisesSocketPathTooLong, aLibTmuxException, in place of tmux's bareFile name too long. An explicitsocket_pathis checked when theServeris created and asocket_namewhen a command runs;Server.is_alive()still returnsFalseinstead of raising (#730).
See the changelog for the full list.
What's Changed
- Measure a tmux socket path where tmux resolves it by @tony in #730
- Server(fix[save_buffer]): Create the saved file owner-only by @tony in #903
- Pane(fix[send_keys]): Send hex keys without a trailing Enter by @tony in #904
Full Changelog: v0.65.0...v0.66.0