-
-
Notifications
You must be signed in to change notification settings - Fork 3.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
When connecting to a switch, the backspace key cannot take effect directly, you need to press Shift to use it. #5862
Comments
need a configuration supporting Backspace sends ^H. |
I agree with @cloud-yu For example: putty has a setting allowing you to choose whether the backspace key sends DEL ( Version: 1.0.187 |
so where is the setting to choose backspace key?I cant find it |
I'm patiently waiting for this open too. For most things I do in the terminal, backspace and delete work just fine, but 1 editor that I have to use for work, when I press 'delete', it puts a '~' in, and when I press 'backspace', it deletes the letter to the right not the left. In MobaXterm, I can press 'backspace' to delete the letter to the left, and if I press 'shift+backspace' or 'ctrl+backspace' it will delete the letter to the right. Really hoping re-mapping backspace to ^H like you can in Putty, etc... becomes a thing. Otherwise, this has allowed me to move off of both MobaXterm and CryptoTerm (it does a better job than MobaXterm in pretty much everything except ^H support for backspace, and it does a better job than CryptoTerm for WYSE60 stuff). |
when telnet to switch/router the 'backspace' can't delete any, i must use ctr+H ,how to use backspace as usual? |
Temporary solutions Hope to improve this problem |
The new nightly will be ready soon - https://github.com/Eugeny/tabby/actions/runs/5561717712 - you'll find the new backspace setting on the Input tab of your profile config.
|
it works
|
Version: 1.0.173
Platform: macOS x64 21.3.0
Plugins: workspace-manager, title-control, search-in-browser, save-output, quick-cmds, altair
Frontend: xterm
The text was updated successfully, but these errors were encountered: