Skip to content

Conversation

@KevinDCarlson
Copy link
Contributor

Modern OS X seems to reserve C-space for toggling keyboard encodings. The VS Code plugin suggests C-c C-r as usually a reasonable replacement for C-c C-space, so I've suggested adding the same tip. I don't know enough about C-c C-r to know whether this is dangerous advice or needs more expansion, or whether it's worth trying to understand how to override the system's control of C-space entirely.

Copy link
Member

@wadler wadler left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks for the suggestion!

I use a Mac, and I've never encountered that particular problem.

Rather than enlarge the text with a sentence or two for each problem some user might encounter, I wonder if it is better to add a "troubleshooting" section with hints such as this one. What do you think?

@KevinDCarlson
Copy link
Contributor Author

Yes, that seems fine. I’m confused about who exactly this affects as one reading of this post is that it ought to affect everyone. Possibly that was briefly true and now it only affects people with multiple keyboards enabled. In fact given that it doesn’t affect all Macs maybe this is fine to just let people Google. https://www.reddit.com/r/MacOSBeta/s/PhcqVbBc2f

@JacquesCarette
Copy link
Collaborator

I think emacs overrides this - I've never had issues with C-space on Aquamacs. So it might be only VSCode that has this issue.

@wenkokke
Copy link
Collaborator

I've not had this issue with VSCode.

@wenkokke
Copy link
Collaborator

Closing for now. Feel free to reopen if you encounter this issue.

@wenkokke wenkokke closed this Jul 27, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants