Cannot use backspace when entering new quest
when typing in a new quest the backspace key seems to be bound to the letter h and therefore backspace does not work.
To Reproduce Steps to reproduce the behavior:
- open quest-tui
- press
nkey for new quest - start typing and then try to delete using backspace
- See error
Desktop (please complete the following information):
- OS: NetBSD 9.1_STABLE
- Terminal emulator: xterm
- Shell: ksh
Additional context That's it. But While I'm at it, the blinking menu is pretty annoying... why does it blink?
Hello,
I have done some investigation, it seems that the program thinks you are inputing a CTRL + BACKSPACE somehow. Maybe it is your shell or terminal that does that, it seems that this is related to an issue with crossterm here. I'm going to write a quick fix, could you please tell me if you are able/willing to compile a test version of Quest to help me investigate this issue.
Have a great day,
SDA
please tell me if you are able/willing to compile a test version of Quest to help me investigate this issue.
Absolutely. Just give me some basic instructions to follow and I will do my best :)
For the moment, could you change the delete keybinding? maybe it would solve the problem with deleting.
As @SDAChess mentioned, it seems the issue is related to crossterm.
Also, it would be helpful if you could try Quest with other terminals/shells to narrow down the problem and paste the exact error since currently, I'm unable to provide the mentioned setup to reproduce the error.
Also, it would be helpful if you could try
Questwith other terminals/shells to narrow down the problem and paste the exact error since currently, I'm unable to provide the mentioned setup to reproduce the error.
Still in a ksh shell I get these results in the following terminals:
xst/st - backspace works as expected, menu blinks
kitty - all good, backspace works and no menu blinking.
I will try later tonight on another machine running linux with zsh and Alacritty
No issues on Alacritty in a zsh shell.
Although it is setting a background colour which overrides my terminal transparency settings... :confused: