-
Notifications
You must be signed in to change notification settings - Fork 96
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
Possible keybind overlap with Atom? #198
Comments
version : 0.47.0 By the way the default keybind from atom is set in \keymaps\emacs.json {
".platform-darwin atom-workspace, .platform-darwin atom-text-editor": {
"cmd-alt-b": "build:trigger",
"cmd-alt-v": "build:toggle-panel",
"cmd-alt-g": "build:error-match",
"cmd-alt-h": "build:error-match-first",
"cmd-alt-t": "build:select-active-target"
},
".platform-linux atom-workspace, .platform-linux atom-text-editor, .platform-win32 atom-workspace, .platform-win32 atom-text-editor": {
"ctrl-alt-b": "build:trigger",
"ctrl-alt-v": "build:toggle-panel",
"ctrl-alt-g": "build:error-match",
"ctrl-alt-h": "build:error-match-first",
"ctrl-alt-t": "build:select-active-target"
},
".build": {
"escape": "build:stop"
},
".build-confirm": {
"enter": "build:confirm",
"escape": "build:no-confirm"
}
}
|
Yes, that is what the |
Edit: From what I undersand Atom should give priority to the command highlighted in green, but it does not appear to be the case currently. Edit2: Nevermind, apparently some kind of operating system glitch prevented my atom to properly use this hotkey, after a hard reboot and a refresh of Atom folder and savefiles everything is fine and CTRL-ALT-B will build my code now. Thanks for your help @noseglid |
I don't do this very often, pardon my Github etiquette,
CTRL-ALT-B (build:trigger on atom-build) overlap with editor:move-to-previous-subword-boundary from atom-text-editor (which is the case by default I believe)
I don't know if it's a well known fact and I'm stating the obvious here, but I had to rebind build:trigger for a few months now, every new patch.
The text was updated successfully, but these errors were encountered: