Closed zikajk closed 12 months ago
Does the hideMarkup
option not do what you want?
It's not exposed as an option by default on the Org
widget, but I could expose it. In the meantime the easy way to see the effect is with the OrgText
widget, or in Orgro where it's exposed in the UI as "Reader Mode".
Proposal: extend the parsing logic to effectively conceal these markup symbols
Hiding parts of markup is a presentation-layer concern, and shouldn't concern the parser (except as to require a certain level of granularity in the parse result such that unwanted symbols are easily distinguished from other results).
Does the
hideMarkup
option not do what you want?It's not exposed as an option by default on the
Org
widget, but I could expose it. In the meantime the easy way to see the effect is with theOrgText
widget, or in Orgro where it's exposed in the UI as "Reader Mode".
It does, i wasn't aware of it, thank you.
I just published v4.4.0 which exposes hideMarkup
as a parameter on Org
and OrgText
. It does more than just hide markup, though, so it might not fit your use case exactly.
If you have specific additional needs, please open a new ticket.
Certain Org markup symbols (e.g., ~, =) remain visible in the rendered output, potentially disrupting the clean visual representation. Proposal: extend the parsing logic to effectively conceal these markup symbols, while possibly introducing an option for devs who prefer to keep them visible.