Max Nikulin <maniku...@gmail.com> writes: >> Nested objects of the same type are not really a limitation of top-down >> parser. It is the syntax of objects that might but does not have to be. >> We might come up with a syntax that allow nesting. > > I would be glad to learn that I am wrong. The current parser picks first > terminating token ignoring other opening tokens in between. The only way > I see is unique identifiers for opening and closing tokens to allow > match them in pairs. It would be tedious to type and to copy fragments > from similar text.
Not necessarily. The current parser also allows balanced brackets inside an object. Search for "balanced" in https://orgmode.org/worg/org-syntax.html and you will see many examples. In addition, we can allow multiple forms of tokens. For example, @wrap{simple wrap}; @wrap{{we can have } inside}}; @wrap{outer wrap; @wrap{inner wrap}; back}. @wrap{{outer wrap; @wrap{{inner wrap allowing } as well}}; back}}. > A similar problem is importing and exporting fragments of mail messages > having multilevel quotes. #+begin_quote is not enough, it is necessary > to use something else for inner citations, e.g. #+begin_quote1. As you see, my solution is conceptually similar to #+begin_quote1 idea. > Moreover I would prefer to have links as links even when they need some > special treatment. What about @wrap[#+attr_html: :alt "Text"]{[[/path/to/image]]}? -- 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>
