[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Writing text which is not interpreted by Org
From: |
Christopher Dimech |
Subject: |
Re: Writing text which is not interpreted by Org |
Date: |
Tue, 17 Nov 2020 18:07:21 +0100 |
Space solved the problem.
---------------------
Christopher Dimech
General Administrator - Naiad Informatics - GNU Project (Geocomputation)
- Geophysical Simulation
- Geological Subsurface Mapping
- Disaster Preparedness and Mitigation
- Natural Resource Exploration and Production
- Free Software Advocacy
> Sent: Tuesday, November 17, 2020 at 5:59 PM
> From: "Robert Pluim" <rpluim@gmail.com>
> To: "Christopher Dimech" <dimech@gmx.com>
> Cc: "Help Gnu Emacs" <help-gnu-emacs@gnu.org>
> Subject: Re: Writing text which is not interpreted by Org
>
> Christopher Dimech <dimech@gmx.com> writes:
>
> >> There is one limitation, however. You must insert a comma right
> >> before lines starting with either ‘*’, ‘,*’, ‘#+’ or ‘,#+’, as those
> >> may
> >> be interpreted as outlines nodes or some other special syntax. Org
> >> transparently strips these additional commas whenever it accesses the
> >> contents of the block.
> >>
> >> #+BEGIN_EXAMPLE
> >> ,* I am no real headline
> >> #+END_EXAMPLE
> >
> > That's what I discussed, without any caveat such as comma before '*'.
> > As I just want to show what the contents of an org file would be.
>
> You could put a space instead of the comma. Note that the org manual
> itself uses the comma method.
>
> Robert
>