you can escape those by putting a , in front of them. You may have to type
C-q , to get it put in if you see strange messages about user-error:
Priority must be between ‘A’ and ‘C’.

In fact org-mode will do that for you if you are in special edit mode when
you exit it. You may not be able to use C-c ' to get into this mode though
with the * in the block until you put , in front of them.

John

-----------------------------------
Professor John Kitchin
Doherty Hall A207F
Department of Chemical Engineering
Carnegie Mellon University
Pittsburgh, PA 15213
412-268-7803
@johnkitchin
http://kitchingroup.cheme.cmu.edu



On Thu, Feb 14, 2019 at 3:15 PM Galen Menzel <galen.men...@utexas.edu>
wrote:

> Hi all,
>
> I’m finding that org source blocks are getting confused if their text
> contains org syntax. For example, in the text below, org considers all the
> lines beginning with asterisks in the text below to be org headers, and
> will fold them accordingly:
>
> #+BEGIN_SRC text
> This source block folds just fine
> #+END_SRC
>
> #+BEGIN_SRC text
> This source block doesn't fold properly because it contains an org headline
> * See?
> #+END_SRC
>
> #+BEGIN_SRC emacs-lisp
> (surely this problem doesnt apply in emacs-lisp mode)
> * Does it?
> ** Sadly it does
>  #+END_SRC
>
>  #+BEGIN_QUOTE
>  The problem also pertains to quotes
> * as you can see
> #+END_QUOTE
>
> #+BEGIN_EXAMPLE
> And examples are no exception
> * As you can see again
> #+END_EXAMPLE
>
> Since all these “headlines” occur inside source, quote, or example blocks,
> they shouldn’t be considered org headlines. In addition, the blocks that
> contain lines beginning with asterisks won’t fold properly.
>
> I’m seeing this behavior in both 9.2.1 and 9.1.9. Are others seeing this?
> Please let me know if I can provide any further information!
>
> Best,
>
> Galen
>

Reply via email to