fix: Handle backspace in Bash

[joelspadin]

Bash returns the ASCII code for DELETE instead of BACKSPACE when pressing backspace. Added a special case for that.

Likely fixes #63

[caksoylar]

Seems to work fine for me (fixes backspace on fish, delete works OK; on bash, fixes backspace but delete still doesn't work which is better).

[caksoylar]

So I have more context: what's the reason for having rich and manual handling implementations? I assume rich didn't cover all our use cases, but is there opportunity to simplify the interface and not have to do manual input processing?

Currently it's weird because when I run zmk keyboard new the keyboard name prompt uses Rich, where backspace works fine but arrow keys don't, and the filters for e.g. interconnect uses the manual handling, where arrow keys work OK.

[joelspadin]

Rich prompts don't have anything close to the menu system, as far as I'm aware. Running a prompt function doesn't return until the user presses enter, so there's no way to use a prompt for the filter text but draw the menu as well.

[joelspadin]

Seems to work fine for me (fixes backspace on fish, delete works OK; on bash, fixes backspace but delete still doesn't work which is better).

Delete is working for me on Bash (version 5.2.21) in WSL Ubuntu. Could you run python3 and try the following to see what it prints?

import os
os.read(sys.stdin.fileno(), 4)
# press the delete key

I get

>>> import os
>>> os.read(sys.stdin.fileno(), 4)
^[[3~

[caksoylar]

Sorry, red herring. I must have mixed up the testing, both backspace and delete work in bash/fish when I try now.