Max Nikulin writes:
> By the way, is it explicitly specified that within an element namely
> top-down strategy must be used to recognize objects?
https://orgmode.org/worg/org-syntax.html has it, I think.
--
Ihor Radchenko // yantar92,
Org mode contributor,
Learn more about Org mode at
On 11/10/2023 19:26, Ihor Radchenko wrote:
Max Nikulin writes:
P.S. Juan Manuel at certain moment discovered that pandoc allows nesting
for *b1 *b2* b3*.
Which is a bug in pandoc.
I think we discussed this topic a number of times in the past - our
markup is a compromise between simplicity
> Fixed, on main.
Thanks!
--
Tom Alexander
pgp: https://fizz.buzz/pgp.asc
Max Nikulin writes:
>> No, **bold** it is not a bug. The parser is recursive with inner markup
>> not "seeing" its parent. So, we first parse the outer bold and then
>> continue parsing the contents separately, as *bold*.
>
> I just find the following rather confusing:
>
> (org-export-string-as
On 11/10/2023 16:15, Ihor Radchenko wrote:
Max Nikulin writes:
Isn't nested bold for "**bold**" a bug? Generally it is not allowed and
*b1 *b2* b3*
is parsed as bold only for "b1 *b2".
No, **bold** it is not a bug. The parser is recursive with inner markup
not "seeing" its parent.
Max Nikulin writes:
> Isn't nested bold for "**bold**" a bug? Generally it is not allowed and
>
> *b1 *b2* b3*
>
> is parsed as bold only for "b1 *b2".
No, **bold** it is not a bug. The parser is recursive with inner markup
not "seeing" its parent. So, we first parse the outer bold and
On 10/10/2023 19:07, Ihor Radchenko wrote:
"Tom Alexander" writes:
I used the following test document:
```
__foo__
**foo**
```
Fixed, on main.
https://git.savannah.gnu.org/cgit/emacs/org-mode.git/commit/?id=fe23bec60
Isn't nested bold for "**bold**" a bug? Generally it is not allowed and
"Tom Alexander" writes:
> I used the following test document:
> ```
> __foo__
>
> **foo**
> ```
>
> I'd expect the two to behave the same but the first one parses as:
> ```
> (paragraph
> "_"
> (subscript "foo")
> "__"
> )
> ```
Fixed, on main.