Control-Backspace Does Not Work (Windows)
See original GitHub issue- I am on the latest Hyper.app version
- I have searched the issues of this repo and believe that this is not a duplicate
- Windows 10 64bit (build 1607):
- Hyper.app 1.3.3:
- The issue is reproducible in vanilla Hyper.app:
Issue
I use Hyper on both my macOS device and my windows desktop, on Mac I am able to remove words with ease using alt-delete, on Windows trying to get the same results using ctrl-backspace instead does not delete the previous string of characters but instead places a ‘w’ character every time the combination is pressed (see gif attached). On both platforms, I am running the most update to date version of the app and have the same plugins installed.
(note) I have tried to see if running the app without plugins (vanilla) would resolve the issue, to which the issue persists regardless.
Plugins:
{
'hypersixteen', // theme
'hyper-dark-scrollbar',
'hyperpower',
'hyper-blink',
'hyperterm-clicky',
'hyperterm-cursor'
}
I don’t recall if the ctrl-backspace functionality worked in a previous version or if this is something that will be fixed/added in a future update for Windows. If there is any way around this help would be appreciated!
Issue Analytics
- State:
- Created 6 years ago
- Reactions:18
- Comments:22 (1 by maintainers)
Top GitHub Comments
Same problem here (Windows 10). It works with Alt+Backspace (for some reason…)
While windows may be the most widely used operating system, it’s worth noting hyper was originally designed as a Mac terminal emulator and that it supports more *nix operating systems vs just windows. While the majority of computers use Windows I’m certain 1.) We cannot confirm how many hyper users are using on windows and 2.) That most of the windows users will not ever use a terminal, let alone hyper, which still makes it a minority in this case.
Then you have the fact that ctrl-w is more commonly accepted by POSIX compliant systems, where there is a standard set where windows seemingly has none. (See kill_word, M-d, etc… this is another can of worms that I don’t think is totally in scope for Windows users)
And last but not least, if the option is customizable and the default is to adhere to an apparent standard, then what is there to fix? I personally, who use hyper on Mac and linux, find ctrl-w to work on the 3k+ systems I interact with via CLI. Is it then “broken” to me because it doesn’t come out of the box using that key combo? Should I then submit a bug report because my key combo isn’t the default?
Ultimately it will be the developer’s sole discretion and I have a feeling if it is changed, it MIGHT change solely for Windows users, if at all (Who have yet to be confirmed as the majority users of hyper) - and that would then lend itself to portability issues and disparities between platforms as now if I have to use hyper on my windows machine, suddenly my key combo that works on 2 other machines doesn’t work on the one special snowflake.
On Wed, Oct 2, 2019, 05:47 Esteban Luchsinger notifications@github.com wrote: