all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
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
Date: Tue, 17 Nov 2020 17:30:04 +0100	[thread overview]
Message-ID: <87ima4c5f7.fsf@gmail.com> (raw)
In-Reply-To: <trinity-88adad9c-a466-42e5-b561-9037476c49c8-1605629487055@3c-app-mailcom-bs03> (Christopher Dimech's message of "Tue, 17 Nov 2020 17:11:27 +0100")

Christopher Dimech <dimech@gmx.com> writes:

> How can I write text which is not interpreted by Org
>
> Because in the following code, Org interprets * as a heading.
>
> -------- Gunga-Din.org --------
>
> #+begin_src text
> * [/] [%] Heading
> #+end_src

From (info "(org) Literal Examples")

    12.6 Literal Examples
    =====================

    You can include literal examples that should not be subjected to markup.
    Such examples are typeset in monospace, so this is well suited for
    source code and similar examples.

         #+BEGIN_EXAMPLE
           Some example from a text file.
         #+END_EXAMPLE

       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



  reply	other threads:[~2020-11-17 16:30 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-11-17 16:11 Writing text which is not interpreted by Org Christopher Dimech
2020-11-17 16:30 ` Robert Pluim [this message]
2020-11-17 16:42   ` Christopher Dimech
2020-11-17 16:59     ` Robert Pluim
2020-11-17 17:07       ` Christopher Dimech

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87ima4c5f7.fsf@gmail.com \
    --to=rpluim@gmail.com \
    --cc=dimech@gmx.com \
    --cc=help-gnu-emacs@gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.