-
-
Notifications
You must be signed in to change notification settings - Fork 85
Unresolved Issues
Issues are sometimes left unresolved and lose their chances for the resolution forever. This happens e.g. when the reporter disappears or when the issue becomes not reproducible for unknown factors. Such issues would stack in the issue list forever without no chances to be resolved. Instead, I will summarize and collect such issues here.
https://github.com/akinomyoga/ble.sh/issues/523
https://github.com/kovidgoyal/kitty/issues/3587
As far as I know, ble.sh correctly supports the extra flags for NumLock and
CapsLock by kitty, so the problem should not happen. In fact, I cannot
reproduce the problem with kitty 0.31.0 and 0.34.6 (the latest version as of
the report). This must be related to the specific setup the reporter used, but
the reporter did not respond.
I feel it unlikely, but one opssibility would be the user sets up the
keybinding through ble-bind -k, which registers a key for the specific byte
sequence.
It does not reproduce.
The reporter seems to have concluded that this is caused by Starship, but we can only conclude it when the problem arises with Starship but without ble.sh. The reporter's last message is unclear about it, but I do not see the reason that the plain Starship would cause such a problem. I suspect it is caused by the cobination of Starship and ble.sh. This might be related to the rerendering of the initial prompt.
https://github.com/akinomyoga/ble.sh/issues/484 https://github.com/akinomyoga/ble.sh/issues/333