Command + Space no longer catchable
I can no longer use Command + Space inside iTerm2.
I have been using iTerm2 for years, and configured it so that the Command keys acts as the Alt key. I recently applied the security patch for macOS Sierra 10.12.6, and while all other key combinations continue to work, Command + Space is no longer transmitted to the terminal application, which is a pain as it is bound to set-mark
in my favorite environment, qemacs
.
Where can I change this behavior?
macos keyboard sierra shortcut emacs
add a comment |
I can no longer use Command + Space inside iTerm2.
I have been using iTerm2 for years, and configured it so that the Command keys acts as the Alt key. I recently applied the security patch for macOS Sierra 10.12.6, and while all other key combinations continue to work, Command + Space is no longer transmitted to the terminal application, which is a pain as it is bound to set-mark
in my favorite environment, qemacs
.
Where can I change this behavior?
macos keyboard sierra shortcut emacs
set-mark should be ctrl-space.
– Thorbjørn Ravn Andersen
Feb 10 at 18:17
@ThorbjørnRavnAndersen:set-mark
is bound to both ctrl-space and alt-space inqemacs
. Depending on the next cursor movement, eg: alt-f or ctrl-n, one is more efficient than the other and my left fingers have gotten used to select the quickest.
– chqrlie
Feb 10 at 22:28
add a comment |
I can no longer use Command + Space inside iTerm2.
I have been using iTerm2 for years, and configured it so that the Command keys acts as the Alt key. I recently applied the security patch for macOS Sierra 10.12.6, and while all other key combinations continue to work, Command + Space is no longer transmitted to the terminal application, which is a pain as it is bound to set-mark
in my favorite environment, qemacs
.
Where can I change this behavior?
macos keyboard sierra shortcut emacs
I can no longer use Command + Space inside iTerm2.
I have been using iTerm2 for years, and configured it so that the Command keys acts as the Alt key. I recently applied the security patch for macOS Sierra 10.12.6, and while all other key combinations continue to work, Command + Space is no longer transmitted to the terminal application, which is a pain as it is bound to set-mark
in my favorite environment, qemacs
.
Where can I change this behavior?
macos keyboard sierra shortcut emacs
macos keyboard sierra shortcut emacs
edited Feb 10 at 17:21
Nimesh Neema
15.4k64277
15.4k64277
asked Feb 10 at 16:40
chqrliechqrlie
1616
1616
set-mark should be ctrl-space.
– Thorbjørn Ravn Andersen
Feb 10 at 18:17
@ThorbjørnRavnAndersen:set-mark
is bound to both ctrl-space and alt-space inqemacs
. Depending on the next cursor movement, eg: alt-f or ctrl-n, one is more efficient than the other and my left fingers have gotten used to select the quickest.
– chqrlie
Feb 10 at 22:28
add a comment |
set-mark should be ctrl-space.
– Thorbjørn Ravn Andersen
Feb 10 at 18:17
@ThorbjørnRavnAndersen:set-mark
is bound to both ctrl-space and alt-space inqemacs
. Depending on the next cursor movement, eg: alt-f or ctrl-n, one is more efficient than the other and my left fingers have gotten used to select the quickest.
– chqrlie
Feb 10 at 22:28
set-mark should be ctrl-space.
– Thorbjørn Ravn Andersen
Feb 10 at 18:17
set-mark should be ctrl-space.
– Thorbjørn Ravn Andersen
Feb 10 at 18:17
@ThorbjørnRavnAndersen:
set-mark
is bound to both ctrl-space and alt-space in qemacs
. Depending on the next cursor movement, eg: alt-f or ctrl-n, one is more efficient than the other and my left fingers have gotten used to select the quickest.– chqrlie
Feb 10 at 22:28
@ThorbjørnRavnAndersen:
set-mark
is bound to both ctrl-space and alt-space in qemacs
. Depending on the next cursor movement, eg: alt-f or ctrl-n, one is more efficient than the other and my left fingers have gotten used to select the quickest.– chqrlie
Feb 10 at 22:28
add a comment |
1 Answer
1
active
oldest
votes
The system has defined a shortcut that intercepted this on my mac:
commandspace was bound in System Preferences to Select the previous input source in the Input Sources panel of the Shortcuts tab.
This setting might have been in effect already, but since I have only a single input source (US QWERTY keyboard), it may have been ignored before.
In any case, deselecting the shortcut fixed the problem. Since it can be a pain to have to go fishing for a binding in all panels, here is an app (recommended by bmike) that shows you the current live shortcuts in any app as it runs.
- https://www.cheatsheetapp.com/CheatSheet/
1
Nice answer. I’ll add a handy tool I use to avoid the painstaking process of searching the mac settings to see if a specific key did get nabbed. You do still have to go make a change, but at least you know where the key presses went.
– bmike♦
Feb 10 at 17:13
add a comment |
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "118"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: false,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: null,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fapple.stackexchange.com%2fquestions%2f351054%2fcommand-space-no-longer-catchable%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
The system has defined a shortcut that intercepted this on my mac:
commandspace was bound in System Preferences to Select the previous input source in the Input Sources panel of the Shortcuts tab.
This setting might have been in effect already, but since I have only a single input source (US QWERTY keyboard), it may have been ignored before.
In any case, deselecting the shortcut fixed the problem. Since it can be a pain to have to go fishing for a binding in all panels, here is an app (recommended by bmike) that shows you the current live shortcuts in any app as it runs.
- https://www.cheatsheetapp.com/CheatSheet/
1
Nice answer. I’ll add a handy tool I use to avoid the painstaking process of searching the mac settings to see if a specific key did get nabbed. You do still have to go make a change, but at least you know where the key presses went.
– bmike♦
Feb 10 at 17:13
add a comment |
The system has defined a shortcut that intercepted this on my mac:
commandspace was bound in System Preferences to Select the previous input source in the Input Sources panel of the Shortcuts tab.
This setting might have been in effect already, but since I have only a single input source (US QWERTY keyboard), it may have been ignored before.
In any case, deselecting the shortcut fixed the problem. Since it can be a pain to have to go fishing for a binding in all panels, here is an app (recommended by bmike) that shows you the current live shortcuts in any app as it runs.
- https://www.cheatsheetapp.com/CheatSheet/
1
Nice answer. I’ll add a handy tool I use to avoid the painstaking process of searching the mac settings to see if a specific key did get nabbed. You do still have to go make a change, but at least you know where the key presses went.
– bmike♦
Feb 10 at 17:13
add a comment |
The system has defined a shortcut that intercepted this on my mac:
commandspace was bound in System Preferences to Select the previous input source in the Input Sources panel of the Shortcuts tab.
This setting might have been in effect already, but since I have only a single input source (US QWERTY keyboard), it may have been ignored before.
In any case, deselecting the shortcut fixed the problem. Since it can be a pain to have to go fishing for a binding in all panels, here is an app (recommended by bmike) that shows you the current live shortcuts in any app as it runs.
- https://www.cheatsheetapp.com/CheatSheet/
The system has defined a shortcut that intercepted this on my mac:
commandspace was bound in System Preferences to Select the previous input source in the Input Sources panel of the Shortcuts tab.
This setting might have been in effect already, but since I have only a single input source (US QWERTY keyboard), it may have been ignored before.
In any case, deselecting the shortcut fixed the problem. Since it can be a pain to have to go fishing for a binding in all panels, here is an app (recommended by bmike) that shows you the current live shortcuts in any app as it runs.
- https://www.cheatsheetapp.com/CheatSheet/
edited Feb 10 at 22:23
answered Feb 10 at 17:01
chqrliechqrlie
1616
1616
1
Nice answer. I’ll add a handy tool I use to avoid the painstaking process of searching the mac settings to see if a specific key did get nabbed. You do still have to go make a change, but at least you know where the key presses went.
– bmike♦
Feb 10 at 17:13
add a comment |
1
Nice answer. I’ll add a handy tool I use to avoid the painstaking process of searching the mac settings to see if a specific key did get nabbed. You do still have to go make a change, but at least you know where the key presses went.
– bmike♦
Feb 10 at 17:13
1
1
Nice answer. I’ll add a handy tool I use to avoid the painstaking process of searching the mac settings to see if a specific key did get nabbed. You do still have to go make a change, but at least you know where the key presses went.
– bmike♦
Feb 10 at 17:13
Nice answer. I’ll add a handy tool I use to avoid the painstaking process of searching the mac settings to see if a specific key did get nabbed. You do still have to go make a change, but at least you know where the key presses went.
– bmike♦
Feb 10 at 17:13
add a comment |
Thanks for contributing an answer to Ask Different!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fapple.stackexchange.com%2fquestions%2f351054%2fcommand-space-no-longer-catchable%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
set-mark should be ctrl-space.
– Thorbjørn Ravn Andersen
Feb 10 at 18:17
@ThorbjørnRavnAndersen:
set-mark
is bound to both ctrl-space and alt-space inqemacs
. Depending on the next cursor movement, eg: alt-f or ctrl-n, one is more efficient than the other and my left fingers have gotten used to select the quickest.– chqrlie
Feb 10 at 22:28