Adam Porter <a...@alphapapa.net> writes: > 1. Having to use separate BEGIN and END macros is less convenient than > more Lispy constructs, like a macro call with a string argument. But I > guess, to wrap Org elements, like a TODO heading or inline task, it > would be necessary. A macro call with the text as an argument wouldn't > be a task in Org syntax, which would make it less useful outside of > rendered HTML.
Not for inlinetasks. For everything but heading, we can actually use special blocks. For headings, there is also :HTML_HEADLINE_CLASS property. > 2. Those macros, or one much like them, could be useful for the use > case of centering text to stand out, as discussed in the other thread. Yes, but they are currently rather plain (other than having an image): .org-info-box { clear:both; margin-left:auto; margin-right:auto; padding:0.7em; } .org-info-box img { float:left; margin:0em 0.5em 0em 0em; } .org-info-box p { margin:0em; padding:0em; } Wondering if we should add some background. > 3. For cases that don't potentially involve wrapping Org elements, > having a simple macro with the text as its argument might be preferable > to having separate BEGIN and END macros. I wonder if we could have > non-begin-end equivalents of the begin-and-end macros listed there. .org-info-box is certainly not suitable for inline highlights. Do we need such highlights though? Isn't the classic italic/bold/underline enough? -- Ihor Radchenko // yantar92, Org mode contributor, Learn more about Org mode at <https://orgmode.org/>. Support Org development at <https://liberapay.com/org-mode>, or support my work at <https://liberapay.com/yantar92>