coq_nvim
coq_nvim copied to clipboard
Not enough values to unpack in tmux parse.py
I get this error when updating COQ. I run it in neovim: v0.8.0-dev-1185-geb4844b5e-dirty and also tmux: next-3.4
Traceback (most recent call last):
File "/home/u009893/.local/share/nvim/site/pack/packer/start/coq-nvim/.vars/runtime/lib/python3.10/site-packages/pynvim_pp/logging.py", line 31, in suppress_and_log
yield None
File "/home/u009893/.local/share/nvim/site/pack/packer/start/coq-nvim/coq/clients/tmux/worker.py", line 39, in _poll
await self.periodical()
File "/home/u009893/.local/share/nvim/site/pack/packer/start/coq-nvim/coq/clients/tmux/worker.py", line 45, in periodical
current, panes = await snapshot(
File "/home/u009893/.local/share/nvim/site/pack/packer/start/coq-nvim/coq/tmux/parse.py", line 107, in snapshot
panes = await _panes(tmux, all_sessions=all_sessions)
File "/home/u009893/.local/share/nvim/site/pack/packer/start/coq-nvim/coq/tmux/parse.py", line 75, in _panes
return tuple(cont())
File "/home/u009893/.local/share/nvim/site/pack/packer/start/coq-nvim/coq/tmux/parse.py", line 55, in cont
(
ValueError: not enough values to unpack (expected 7, got 1)
When reverting to the dev branch i get the same error but it then expects 9 values to unpack.
A more controlled update of my environment gives that this is due to recent changes in the tmux repository. The changes that seems to cause this are show in tmuxdiff
I am also getting this behavior on tmux next-3.4. Downgrading to tmux 3.3 fixes the problem
Specifically, looks like the current _SEP
symbol (\x1f
) is handled differently in tmux 3.4 and instead of returning the proper symbol a (possibly escaped?) \037
symbol is returned. This command returns different output when running tmux instance is 3.3a or 3.4-next:
printf "#{session_id}\x1f#{pane_id}\x1f#{pane_title}" | xargs -I{} tmux list-panes -F {}
I have tmux 3.3a
in both mac and linux machines and neovim v0.9.1
and I get this error only in linux, it works perfectly fine in mac (macOS Ventura 13.4).
interesting. I only get this error on macOS
I'm having exactly the same problem after upgrading tmux to next-3.4
.
This is happening to me in 3.3 as well...