Re: Bug: Inconsistent behaviour about inline markup

writes: > But please take this also as a BugReport (because there seems to be no > regular bug tracker for orgmode). I see no need to restrict the allowed > characters that way they are. PRE and POST should be the same. > The only one exception is [ for POST because I suspect this isn't > impleme

Re: Bug: Inconsistent behaviour about inline markup

Dear Timothy, On 2023-01-15 14:22 Timothy wrote: > See . Thanks a lot. That help to make my code consistent. But please take this also as a BugReport (because there seems to be no regular bug tracker for orgmode). I see no need to restr

Re: Bug: Inconsistent behaviour about inline markup

Hi Christian, > Please point to the correct documentation if there is one. See . All the best, Timothy -- Timothy (‘tecosaur’/‘TEC’), Org mode contributor. Learn more about Org mode at . Support Org development at

Bug: Inconsistent behaviour about inline markup

Hello, I'm not sure if this is a bug or intended by design. Please point to the correct documentation if there is one. I'm also not sure if Orgmode is the related component here or if there is any other? What I describe is in the context of auto-formating markup in orgmode. When you type "=v