You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have searched the issues of this repo and believe that this is not a duplicate
OS version and name: macOS 10.15.3
Hyper.app version: 3.0.2 (stable)
The issue is reproducible in vanilla Hyper.app: Is Vanilla
Issue
In MOSH (https://mosh.mit.edu/) for exit I am need to input ctrl+^ (actually for this I am pressed keys ctrl, shift, 6).
From MOSH manual:
ESCAPE SEQUENCES
The default escape character used by Mosh is ASCII RS (decimal 30).
This is typically typed as Ctrl-^ or Ctrl-Shift-6, on US English keyboards.
In Chrome this combination catched by event keypress like this (key code === 30):
In Hyper this combination not worked.
In iTerm and native terminal app - this combination worked.
How to reproduce:
In Hyper connect to linux which have command showkey (I am use debian) and run
showkey -a
and then press ctrl, shift, 6 - nothing was happends.
2. In other terminal do same - and you will see:
Thank you for you work!
The text was updated successfully, but these errors were encountered:
I am on the latest Hyper.app version
I have searched the issues of this repo and believe that this is not a duplicate
OS version and name: macOS 10.15.3
Hyper.app version: 3.0.2 (stable)
The issue is reproducible in vanilla Hyper.app:
Is Vanilla
Issue
In MOSH (https://mosh.mit.edu/) for exit I am need to input
ctrl+^
(actually for this I am pressed keysctrl
,shift
,6
).From MOSH manual:
In Chrome this combination catched by event
keypress
like this (key code === 30):In
Hyper
this combination not worked.In
iTerm
and native terminal app - this combination worked.How to reproduce:
Hyper
connect to linux which have commandshowkey
(I am use debian) and runand then press
ctrl
,shift
,6
- nothing was happends.2. In other terminal do same - and you will see:
Thank you for you work!
The text was updated successfully, but these errors were encountered: