-
Notifications
You must be signed in to change notification settings - Fork 61
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
hotkeys like C-n conflict with browser #6
Comments
For what it's worth, this is a Chrome issue. It is not currently possible to fix this in Chrome. C-w, C-n, & C-t are reserved for the browser. See: https://code.google.com/p/chromium/issues/detail?id=119881 See also: |
Chrome doesn't steal the bindings if you save ymacs as an app and have it open in its own window (annoying, but it works). |
Downloaded and opened js/Ymacs/test/index.html, the page & scripts load fine but keys do not work in Firefox Nightly. I cannot use C-Tab for the obvious but even C-x 2 jumps to the second tab open in nightly and is never seen by Ymacs, not sure if Mozilla have locked them down or ymacs is not stopping the default properly. A popup box or something for editing the bindings would be great as I use browser bindings as well and would happily swap control to insert or tilde. |
With Brave you can edit these annoying shortcuts keys in Settings/System/Shortcuts. Hover with the mouse on the shortcut you hate the most and click the minus circle, hooray! |
@nicolas-mace Glad to hear that at least one browser went sane about it! I found a solution for Firefox too, not for the faint of heart, but it's doable — https://lisperator.net/blog/dogfooding-ymacs/#fix-ctrl-w |
for example, in Chrome,
C-n
is bound on the function to create a new window. is it possible for ymacs to get beyond the browser-level hotkey binding priority?Environment:
uname -a
:Linux kernel 3.6.11-ck i686 Intel(R) Core(TM) i5-2410M CPU @ 2.30GHz GenuineIntel GNU/Linux
(gentoo)chrome --version
:Google Chrome 28.0.1500.89 beta
awesome --version
:awesome v3.4.15
The text was updated successfully, but these errors were encountered: