Closed 10b14224cc closed 8 months ago
I'm afraid I dont have the time/interest to debug Starship's bash integration script. Last time I looked at it I found various issues. From your problem description I'd guess something is preventing the kitty shell integration script from output the escape code to indicate prompt extent and output start properly.
bash is the hardest shell to write robust scripts for, I suggest switching to zsh or fish instead, you are much less likely to encounter these kinds of issues.
If you wish to debug it yourself, kitty's script is in the file kitty.bash.
If you wish to debug it yourself, kitty's script is in the file kitty.bash.
Do you mean kitty.bash
in starship's repo?
So is this a starship bug?
Yes I would guess this is a starship bug, it is interfering with kitty's shell integration. And no kitty.bash is the kitty shell integration script. I dont remember what the starship bash integration file is called.
Actually I had 5 mins so I tried it and it doesnt repro for me with default kitty and starship configs.
Actually I had 5 mins so I tried it and it doesnt repro for me with default kitty and starship configs.
I think is a ble.sh bug in interacting with starship.
It doesn't happen if I don't load ble.sh.
Actually I had 5 mins so I tried it and it doesnt repro for me with default kitty and starship configs.
ble.sh's maintainer pinned it down: https://github.com/akinomyoga/ble.sh/issues/403#issuecomment-1935774146
And #7107 is the fix.
Describe the bug
Using starship,
kitty @ get-text --extent=last_cmd_output
returns the last prompt together with the last command output.See also: https://github.com/mikesmithgh/kitty-scrollback.nvim/issues/179#issuecomment-1924045919
To Reproduce Steps to reproduce the behavior:
echo "hello"
andecho "hi"
kitty_mod+g
hi
(output of last command) together with last promptScreenshots If applicable, add screenshots to help explain your problem.
Environment details