You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
$ pymux
$ vim newfile
$ ctrl+b
$ shift+% (vertical split)
$ mouse click on second pane, then click back again
$ crash
UnicodeDecodeError: 'utf-8' codec can't decode byte 0x8c in position 4: invalid start byte
Crash occurs on mate-terminal with both pyvim and vim, only when using mouse click to switch the panes. Default configuration.
Sorry, pymux did not create a crash file in /tmp, nor in /var/tmp. The only files that were left there were open sockets pymux.sock.<user>.1
The text was updated successfully, but these errors were encountered:
Thanks a lot for reporting this bug! I appreciate it.
This should be a bug in the client part, that doesn't dump a stack, but this is already very helpful like this.
I will investigate next week. It shouldn't be hard to solve.
Jonathan
I think this was fixed in the following commit from three days ago: 0eafae8
(Not sure, but I'll verify again, and hopefully push a new release to pypi.)
UnicodeDecodeError: 'utf-8' codec can't decode byte 0x8c in position 4: invalid start byte
Crash occurs on mate-terminal with both pyvim and vim, only when using mouse click to switch the panes. Default configuration.
Sorry, pymux did not create a crash file in /tmp, nor in /var/tmp. The only files that were left there were open sockets
pymux.sock.<user>.1
The text was updated successfully, but these errors were encountered: