From: "Galen Menzel" <galen.menzel@utexas.edu>
To: John Kitchin <jkitchin@andrew.cmu.edu>
Cc: Org Mode List <emacs-orgmode@gnu.org>
Subject: Re: Source blocks confused by Org syntax
Date: Thu, 14 Feb 2019 12:55:26 -0800 [thread overview]
Message-ID: <56A99DA2-9E21-4B65-AF3E-4344D8D1C9A8@utexas.edu> (raw)
In-Reply-To: <CAJ51ETrSmde6r7STPh6Ys75n-Js8eP1PvKcj9cEGT6XYz1xb9A@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 2193 bytes --]
Ah, thanks — using C-c ' is a functional work around for most of my
needs.
Still, is there no way to create a proper verbatim text block in org?
Galen
On 14 Feb 2019, at 12:37, John Kitchin wrote:
> 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.menzel@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
>>
[-- Attachment #2: Type: text/html, Size: 4972 bytes --]
next prev parent reply other threads:[~2019-02-14 21:05 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-14 20:14 Source blocks confused by Org syntax Galen Menzel
2019-02-14 20:37 ` John Kitchin
2019-02-14 20:55 ` Galen Menzel [this message]
2019-02-14 20:57 ` John Kitchin
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
List information: https://www.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=56A99DA2-9E21-4B65-AF3E-4344D8D1C9A8@utexas.edu \
--to=galen.menzel@utexas.edu \
--cc=emacs-orgmode@gnu.org \
--cc=jkitchin@andrew.cmu.edu \
/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 public inbox
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).