-
-
Notifications
You must be signed in to change notification settings - Fork 64
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
[BUG] <ESC> not working anywhere else but geforce-now #153
Comments
Same issue. More info: I tested previous releases and this issue occurs since v1.7.0. Reverting to v1.6.0 "fixes" it. I also noticed that in games like Cyberpunk 2077 pressing Might be related to #137. |
Also, the double-click focus is not guaranteed. Oftentimes I find myself spamming right-click for the mouse to regain focus, which is in my opinion very frustrating.. |
use Shift + Esc |
That solution appears to not be working. It's as if the Esc key is not even recognized when used alongside Shift. |
Closing. In case this issue still affects anyone, please discuss it in #137 |
Describe the bug
Not only does it lose focus when pressed inside geforce-now (#137), but it also makes it impossible to press outside of geforce now.
One example that I have been very bothered by is the inabliltiy to
<ESC>
inside neovim (or any other terminal-app). Because of this issue I am unable to cancel any form of neovim command-related operation unless I either terminate the terminal-tab||
that I erase the whole operation and hit enter on an empty:
just to mimick an<ESC>
.To Reproduce
Gefroce Now
nvim
):
+ input whatever operation you wish to execute.Example:
echo "hello, world!"
<ESC>
Screenshots
No response
Operating System
NixOS
Desktop Environment
XMonad
Display Server
X11
Installation method
packaged the appimage version
Version
1.7.0
Is this a fresh install of the app or an update from a past version?
Update from 1.6.0
Did this issue appear right away upon installation/updating, or spontaneously?
Yes, right after the installation of the latest version
Additional context
No response
The text was updated successfully, but these errors were encountered: