On Monday, March 29, 2021 at 6:22:34 AM UTC-5 Edward K. Ream wrote: *Aha*: Content filters will modify how rst3 handles @rst trees in a > completely general way. Event filters have (using p) full access to the > entire outline, including all ancestors and descendants of p. >
Some further comments: Instead of using @data nodes to define filters, it makes more sense to use scripts or plugins. I'll create an example plugin soon. rst3 neither knows nor cares how filters work. Anything goes. For example, a filter could run p.b through a templating engine like jinja2. Once can imagine filters giving the effect of the legacy rst3 command, but I'll create such filters only if someone desperately needs them. I'll probably will include a few simplified utilities from the old code, like the code that finds and parses option @doc parts. Edward -- You received this message because you are subscribed to the Google Groups "leo-editor" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/leo-editor/18147ce2-f5e0-422d-8585-bdb14d25198fn%40googlegroups.com.
