v3.6
Tightens clipboard reliability for the common nvim-inside-tmux setup on macOS.
Clipboard
Yanks inside nvim-inside-tmux on macOS were reaching the system clipboard only when nvim's auto-detected pbcopy provider happened to work — which fails on re-attached tmux sessions, sessions with a stripped PATH, or after macOS pasteboard detachment. The yellow tmux highlight from copy-mode worked, but nvim yanks silently dropped.
core/options.lua now picks one of three clipboard modes:
$SSH_TTYset: clipboard left empty (unchanged) — yanks stay in unnamed register, no provider attempted.$TMUXset, not SSH: force the OSC 52 provider viavim.ui.clipboard.osc52(neovim 0.10+). Path becomes nvim → OSC 52 → tmux → terminal → system clipboard, robust againstpbcopy/xclipauto-detection quirks.- Otherwise: nvim auto-detects (
pbcopyon macOS,xclip/wl-copyon Linux).
Requirements when running inside tmux
set -g set-clipboard onin tmux — already added in dotfiles.- An OSC-52-capable terminal: iTerm2, kitty, WezTerm, Ghostty, alacritty all work. Apple Terminal.app does not — switch terminals or yanks won't reach the Mac clipboard.
- iTerm2 specifically requires Preferences → General → Selection → Allow clipboard access via terminal control sequence to be enabled.
CLAUDE.md updated to describe all three modes.
Full changelog: v3.5...v3.6