Re: Allowed characters/formatting in Org text blocks

2022-06-26 Thread Fabio Natali
On 2022-06-26 19:39:25 +0800, Ihor Radchenko wrote: [...] > So, headlines always have higher priority over other elements because > they always serve as separators of the document or parent heading > contents. > > The high priority of headline elements has prons and cons. Hey Ihor, I see, it al

Re: Allowed characters/formatting in Org text blocks

2022-06-26 Thread Ihor Radchenko
Fabio Natali writes: > Incidentally and FWIW, this is a bit counter-intuitive to me. I'd have > expected everything withing a comment or literal block to be treated as > content until the ending statement, =#+end_comment= or =#+end_src= > respectively. I suppose that this makes sense in the large

Re: Allowed characters/formatting in Org text blocks

2022-06-26 Thread Fabio Natali
On 2022-06-26 08:29:02 +0800, Ihor Radchenko wrote: [...] > You need to escape "*" and "#+" at the beginning of line inside code > blocks using comma: ",*", ",#+". Hi Ihor, Thanks for getting back to me! I see, and yes, the documentation is pretty clear in that regard, you're right. Escaping le

Re: Allowed characters/formatting in Org text blocks

2022-06-25 Thread Ihor Radchenko
Fabio Natali writes: > Now consider a slight variation where "Hello world" is formatted as a > Org heading. The 'org-babel-goto-named-src-block' function is no longer > able to identify the text block. Executing the Emacs Lisp block results > in the error message below. > > #+name: bar > #+begin_

Allowed characters/formatting in Org text blocks

2022-06-25 Thread Fabio Natali
Hello, I seem to be having problems when selecting an Org text block from an Emacs Lisp snippet. An MVE follows. Consider a buffer with the following blocks. In this first example, the Emacs Lisp block runs successfully. The block "foo" is identified correctly and the point gets moved accordingly