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
The kitty.conf keybindings don't work when invoked with sudo. The pass_keys.py script captures "sudo" as the first executed command rather than nvim (the second command).
One partial solution to this is to change lines 9 of pass_keys.py to:
return any(re.search(vim_id, p['cmdline'][p['cmdline'][0] == 'sudo'] if len(p['cmdline']) else '', re.I) for p in fp)
However, I can't figure out why this doesn't allow switching from the sudo nvim kitty window to the next adjacent kitty window. It works fine with non-sudo nvim windows.
Any help would be greatly appreciated!
The text was updated successfully, but these errors were encountered:
I believe sudo processes have their own session and environment that kitty does not touch. In other words, kitty can't even see processes run in sudo. I was not able to reproduce your workaround for this reason. However if sudo nvim is showing up in your logs, then you should be able to put
The kitty.conf keybindings don't work when invoked with sudo. The pass_keys.py script captures "sudo" as the first executed command rather than nvim (the second command).
One partial solution to this is to change lines 9 of
pass_keys.py
to:However, I can't figure out why this doesn't allow switching from the
sudo nvim
kitty window to the next adjacent kitty window. It works fine with non-sudo nvim windows.Any help would be greatly appreciated!
The text was updated successfully, but these errors were encountered: