Skip to content
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

commandMarker again: Also allow command id, not only command name #166

Closed
Moonbase59 opened this issue Jul 21, 2021 · 1 comment · Fixed by #169
Closed

commandMarker again: Also allow command id, not only command name #166

Moonbase59 opened this issue Jul 21, 2021 · 1 comment · Fixed by #169
Assignees

Comments

@Moonbase59
Copy link

Moonbase59 commented Jul 21, 2021

Warming up issue #38 again, it seems using the non-changing command ids instead of the command palette names gains some popularity, as in @deathau’s Command URI plugin, and @Vinzent03’s Advanced Obsidian URI. They use a "free format", i.e. you can specify either the command name or the command id.

Maybe it would be worth studying their code and implementing the same for Obsidian Leaflet?

Reason: Command names change with the selected Obsidian language, making it hard for people who switch languages often, because all command logic breaks. The command ID never changes, so would be an ideal candidate to use.

Unfortunately, there is no official command id list (and plugins can add to the commands anyway), but anyone could use my Obsidian Command and Hotkey List (new version) to show command ids and their currently assigned hotkeys within Obsidian. This requires the Dataview plugin to be installed and operational.

Here’s the link to the code, in the Obsidian Forums:
https://forum.obsidian.md/t/dataviewjs-snippet-showcase/17847/37

Not high priority, though. Just put it here since more plugin authors pick it up.

@Moonbase59
Copy link
Author

Brilliant! This works great, thanks!

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 a pull request may close this issue.

2 participants