Replies: 1 comment
-
Hi @bagge That is not possible at the moment. You may be able to hack something together like this: require('kitty-scrollback').setup({
ksb_builtin_last_cmd_output = function(kitty_data)
local has_last_visited_cmd_output = vim
.system({ kitty_data.kitty_path, '@', 'get-text', '--match=id:' .. kitty_data.window_id, '--extent', 'last_visited_cmd_output' })
:wait().stdout
:gsub('\n', '') ~= ''
return {
kitty_get_text = {
extent = has_last_visited_cmd_output and 'last_visited_cmd_output' or 'last_cmd_output',
},
}
end,
})
This overrides the kitty-scrollback.nvim If you don't mind two keymaps, something like this is the safer bet:
Hope this helps. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
To reduce the number of key bindings for similar things I'll have to remember I have tried to achieve the following in kitty:
(i.e. I am trying to avoid having to learn to use a separate key binding to open kitty-scrollback in the last_visited_command config)
Is there someway to achieve that? I have tried with some key sequence mappings in kitty.conf but that doesn't seem to work (makes it unable to just browse the old prompts). Was also contemplating to use modes but can't quite figure out how to get the intended behaviour. Or should I look for creating a special config in kitty-scrollback?
Beta Was this translation helpful? Give feedback.
All reactions