You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm opening this issue as discussion instead of suggestion because it is incomplete proposal. I want to share some idea to implement inline macro.
I know, it smells like LaTeX.
Idea
Inline macro syntax needs macro identifier and list of arguments.
We already have good way to represent key-value arguments inline with attached modifier extensions; (key value;key;key). So we only need syntax to represent macro identifier.
In v1 spec, escaped normal character (not whitespace nor punctuation) doesn't have any additional meanings.
We can use that.
\macro-name(key value;params)
As some inline macros might need raw markup text as an argument, we an provide that with existing [...] grammar:
\macro-name[*markup* argument](key value;params)
I'm not sure if [...] should be free-form or not.
If it is free-form, we can replace $...$ syntax with this:
I'm opening this issue as discussion instead of suggestion because it is incomplete proposal. I want to share some idea to implement inline macro.
I know, it smells like LaTeX.
Idea
Inline macro syntax needs macro identifier and list of arguments.
We already have good way to represent key-value arguments inline with attached modifier extensions;
(key value;key;key)
. So we only need syntax to represent macro identifier.In v1 spec, escaped normal character (not whitespace nor punctuation) doesn't have any additional meanings.
We can use that.
As some inline macros might need raw markup text as an argument, we an provide that with existing
[...]
grammar:Example
Cons
\u
is ok,\t
or\n
might confuse users._\m_
or-\m-
? Macro name can conflict with underline/strikethrough closing modifiers.The text was updated successfully, but these errors were encountered: