Using multiple "Opening Characters" for extension #463

New Issue

claunia · 2026-01-29T14:37:26Z

claunia commented

2026-01-29 14:37:26 +00:00

Originally created by @0xclx on GitHub (May 12, 2021).

Hello!

I have written a few Extensions so far, but they all relied on a single trigger symbol / character.
Now I wanted to ask if it was possible to perhaps use something like "Issue xxx" where as "Issue" is the triggerword instead of a "#" and takes teh following alphanumerical string (with or without whitespace) and processes/parses it.
As far as I know, OpeningCharacters is just an array of characters with each character in the array acting as the trigger individually.

Is there a way to achieve something like "#1234 acts the same as Issue 1234"?

Originally created by @0xclx on GitHub (May 12, 2021). Hello! I have written a few Extensions so far, but they all relied on a single trigger symbol / character. Now I wanted to ask if it was possible to perhaps use something like "Issue xxx" where as "Issue" is the triggerword instead of a "#" and takes teh following alphanumerical string (with or without whitespace) and processes/parses it. As far as I know, OpeningCharacters is just an array of characters with each character in the array acting as the trigger individually. Is there a way to achieve something like "#1234 acts the same as Issue 1234"?

claunia added the question label 2026-01-29 14:37:26 +00:00

claunia referenced this issue

2026-01-29 14:48:59 +00:00

[PR #464] [MERGED] Expose IndentCount of FencedCodeBlock #1044

claunia referenced this issue

2026-01-29 14:49:03 +00:00

[PR #464] Expose IndentCount of FencedCodeBlock #1048

Sign in to join this conversation.