Replies: 2 comments 9 replies
-
I think the issue is that the terminal isn't ready when you press something. It's not about being "first" but rather the time it takes to load. Once it finishes loading, |
Beta Was this translation helpful? Give feedback.
-
Hi @drowning-cat thanks for the reply I tried this, my .zshrc now looks like this:
And no matter how long I wait (I've tried waiting a full minute) if I press up the output is So it doesn't seem to be a loading config issue, any other ideas of what it could be? |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
Thanks for the great plugin!
I cannot work out why when I launch my terminal my first input is not correctly registered. It seems that the first input is interpreted by
sh
and notzsh
as when I press the up arrow I seeOA
or when I paste withctrl
+shift
+v
it outputs[200~<pasted text>~
. From some googling these are the keycodes and so aren't being read by my shell, but output into the terminal. However, I amzsh
and this does not happen except in the snacks terminal.Note this only happens on the first input and not the rest, some keys just enter a blank input and it happens every time I re-open the terminal.
I've tried launching in many different ways, what I thought would, but hasn't is:
I am aware this may be an issue with my terminal and not snacks, but I cannot work out why it only happens in snacks. Also I have tried both kitty and ghostty.
Beta Was this translation helpful? Give feedback.
All reactions