Use case or problem
I use Obsidian on both Mac and Windows, (work computer and home computer), and the lack of different platform-specific hotkeys is driving me mad. I can’t use the built-in Sync system because of this issue, but I do sync across devices. This results in the same exact hotkeys.json file existing on every platform, and every night when I switch computers from work to home, I have to reconfigure my shortcuts. This seems like such a basic oversight. There is no other software I use across platforms that has global-multiplatform shortcuts.
There is a possibility I am doing something wrong and this is my fault that I haven’t figured out a way to do this.
Use platform-specific shortcuts. Or at least, allow people to choose that option.
Current workaround (optional)
Related feature requests (optional)
If this issue didn’t exist, I would still be using the official Obsidian Sync service, which allowed me to turn off sync of hotkeys on my Mac. Dropbox + Dropsync, and I assume every other popular sync service, has background sync on mobile, which is why I switched over. This was a dealbreaker feature for me.
If you don’t want to use Sync, you can still use two different config folders.
BTW, which hotkey are bothering you?
We have already some platform specific hotkeys.
How do I select different config directories by platform? Also, this would add more headache, because if I go nuclear on not having the same config directory on all platforms, I would wipe my ability to sync plugins and everything else in the config. I still want to sync these things, just not the hotkeys file
I configure almost all of them to keep them consistent with other programs, namely VSCode.
I still don’t understand why you want different hotkey for windows and mac in the same vault? and which ones specifically.
I use the same keyboard across my mac and windows computers. I want the same combination of keys to execute the same operation across all programs I use to make the transition between these platforms not crazy-making. Mac and windows have different modifier keys. Command+C and Control+C for copy as an example. They both have a Control key however. I’ve gone through enormous lengths to standardize these, for example, swapping these modifier keys (Command is control and control is command) on the mac, so that they both have copy as the same key combination.
As a result, I need platform-specific hotkeys. I customize every hotkey from Obsidian defaults as far as I am aware. Here is a partial list of my customizations. My choices align with general standards for keyboard shortcuts in combination with some of the VScode defaults, my second-most-used program.
I am confused. Obsidian already handles ctrl on win/linux as cmd on mac (it’s internally coded as mod key).
Ok, upon re reading your message maybe you don’t want the above. It’s very peculiar choice and it won’t help your muscle memory. Anyway, now I understand where you are coming from.
Thanks, I know this is a bit of a quagmire. Even more than the modifier key is the choice of what the Mac’s control and opt would map to on Window’s win and alt keys. One might think opt = alt, and ctrl = windows I guess, though an argument could definitely be made for the opposite, but when you plug the same keyboard into both platforms, this is not how it goes. (At least for the keyboard I use)
The fact that these diverged at some point, despite the rest of the keyboard UI being standardized is really a interesting point of history. Platform-specific hotkeys would really ease the burden of all of us being subject to Apple and Microsoft’s desires to bind everyone to a single platform in a cult-like fashion, hahaha. I’d 100% use Windows at work if mac wasn’t a requirement.
I experimented with changing the configuration folder under About, and see that it doesn’t affect all devices, so different devices can have different configurations and therefore different hotkeys. I’ll use that feature for now, even though that requires me to repeat making any plugin/other settings changes across each device whenever I do. Nevertheless, I’m grateful for solution that is less frustrating that where I started. Thanks.
I’ll still keep the feature request open though.