Vinzent03 / obsidian-advanced-uri

Advanced modes for Obsidian URI
MIT License
766 stars 44 forks source link

trouble with command ID/name #159

Closed seatrout closed 9 months ago

seatrout commented 9 months ago

I am confused by the difference between a command ID and the command name.

In particular, I want to call the Pandoc extension command to export a file as word (because it uses Obsidian's rendered markdown, and plain pandoc is bad at footnotes, block quotes, and so on).

But none of the pandoc extension's commands show up using this extension's copy command ID

Do I then use command name instead? How much do I have to escape that string?

Vinzent03 commented 9 months ago

I can't reproduce your issue. Are you using the Advanced URI: copy URI for command command? You first specify the file and afterward select the command to execute.

seatrout commented 9 months ago

To reproduce my issue, just try to use the Advanced URI: copy URI for command on commands such as Pandoc Plugin: Export as Word Document (docx) — they are not shown; in fact none of the pandoc subcommands are. So my question was how do I pass in Pandoc Plugin: Export as Word Document (docx) as a command? I tried escaping it in various ways and none of them seemed to help. It's possible to work around this — I finally wrote a script to call pandoc externally and to mimic the tricks the extension uses to reproduce what we see on screen in Obsidian. So it's a low priority. But it is reproducible.

Vinzent03 commented 9 months ago

Well, it still works perfectly fine for me. Are you using the latest version of both plugins? Either way, you can try the following uri.

obsidian://advanced-uri?commandid=obsidian-pandoc%253Apandoc-export-docx
seatrout commented 9 months ago

ah! Thank you: so it needs

  1. The separate words joining with hyphens
  2. the colon double escaped.

This wasn't clear from the documents. Perhaps it could be made clearer. I had read them to mean that all the spaces in a command name had to be escaped, not replaced with hyphens.


Andrew Brown Writes for people mobile: +44-(0)7968-945618

On Fri, 23 Feb 2024 at 14:41, Vinzent @.***> wrote:

Well, it still works perfectly fine for me. Are you using the latest version of both plugins? Either way, you can try the following uri.

obsidian://advanced-uri?commandid=obsidian-pandoc%253Apandoc-export-docx

— Reply to this email directly, view it on GitHub https://github.com/Vinzent03/obsidian-advanced-uri/issues/159#issuecomment-1961455121, or unsubscribe https://github.com/notifications/unsubscribe-auth/ABII7JJR77A4UUIBZIJILQ3YVCTDFAVCNFSM6AAAAABDERDINKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSNRRGQ2TKMJSGE . You are receiving this because you authored the thread.Message ID: @.***>

Vinzent03 commented 9 months ago

That's not the case. There is a difference between name and id. The one I gave you is using the command id and not the name. The id contains hyphens as defined by the plugin developer.