I'm using v0.13.3 on macOS 10.14 Mojave. Kitty's features and performance have convinced me to use it instead of the built-in Terminal app, and now I am in the process of bringing my keyboard shortcuts over from Terminal to Kitty.
One shortcut I am stuck on is cmd + . which in Terminal behaves exactly like ctrl + c.
I am unable to implement this functionality in Kitty for two reasons:
- Via
kitty --debug-keyboard, I can see that Kitty knows when I press and then release cmd. It does not register anything at all, however, when I hit . while holding down cmd. Only . appears to be affected. I can see the debugger report other combinations correctly, such as cmd + l or cmd + o or cmd + p.
- Even if I could get Kitty to recognize that
cmd + . was being inputted, I do not know how to map that combination to ctrl + c. Should I send interrupt or is there a way to have it send hex? (For hex I would need to send \x03.
I would appreciate any assistance with pointing me in the right direction with this matter. Thank you fort your time.
I'm using v0.13.3 on macOS 10.14 Mojave. Kitty's features and performance have convinced me to use it instead of the built-in Terminal app, and now I am in the process of bringing my keyboard shortcuts over from Terminal to Kitty.
One shortcut I am stuck on is
cmd + .which in Terminal behaves exactly likectrl + c.I am unable to implement this functionality in Kitty for two reasons:
kitty --debug-keyboard, I can see that Kitty knows when I press and then releasecmd. It does not register anything at all, however, when I hit.while holding downcmd. Only.appears to be affected. I can see the debugger report other combinations correctly, such ascmd + lorcmd + oorcmd + p.cmd + .was being inputted, I do not know how to map that combination toctrl + c. Should I sendinterruptor is there a way to have it send hex? (For hex I would need to send\x03.I would appreciate any assistance with pointing me in the right direction with this matter. Thank you fort your time.