Describe the bug
When I tested on iTerm2 i was able to navigate through lines using cmd+up. On kitty, however, I cannot since it types A instead of moving line up.
On iTerm2, when I press shift+up it shows A. So I suppose that on kitty, cmd is treated the same as shift when using tmux.
Both Kitty and iTerm2 use zsh.
Other behaviors
lualine.nvim
On kitty using tmux, lualine.nvim goes up and down when I press cmd+up/down while on iTerm it does not. I have no idea which is the desired behavior.
To Reproduce
Steps to reproduce the behavior:
Open Tmux on Kitty.
Execute something so that your shell have a history.
Press cmd+up
See error
Environment details
❯ brew info tmux
==> tmux: stable 3.3a (bottled), HEAD
Press Ctrl+Shift+F6 (cmd+option+comma on macOS) in kitty, to copy debug output about kitty and its
configuration to the clipboard and paste it here.
On older versions of kitty, run kitty --debug-config instead
Additional context
Try to reproduce the problem with kitty --config NONE if you cannot then post a minimal kitty.conf that reproduces the problem. If the problem involves interaction with some other terminal program post a minimal config for that program to reproduce the problem as well.
Describe the bug When I tested on iTerm2 i was able to navigate through lines using
cmd+up
. On kitty, however, I cannot since it typesA
instead of moving line up.On iTerm2, when I press
shift+up
it showsA
. So I suppose that on kitty,cmd
is treated the same asshift
when using tmux.Both Kitty and iTerm2 use zsh.
Other behaviors
lualine.nvim
cmd+up/down
while on iTerm it does not. I have no idea which is the desired behavior.To Reproduce Steps to reproduce the behavior:
cmd+up
Environment details
Press Ctrl+Shift+F6 (cmd+option+comma on macOS) in kitty, to copy debug output about kitty and its configuration to the clipboard and paste it here.
On older versions of kitty, run kitty --debug-config instead
Additional context Try to reproduce the problem with
kitty --config NONE
if you cannot then post a minimal kitty.conf that reproduces the problem. If the problem involves interaction with some other terminal program post a minimal config for that program to reproduce the problem as well.