From: "Eric Schulte" <schulte.eric@gmail.com>
To: Jeff Horn <jrhorn424@gmail.com>
Cc: Org-mode ml <emacs-orgmode@gnu.org>
Subject: Re: Commas in org source blocks
Date: Tue, 25 Jan 2011 12:36:05 -0700 [thread overview]
Message-ID: <8739og6aje.fsf@gmail.com> (raw)
In-Reply-To: <AANLkTin8mUuB+7nWZMmnXTPG5Z3sRA4ZTfdQxwVm7kWD@mail.gmail.com> (Jeff Horn's message of "Tue, 25 Jan 2011 13:52:06 -0500")
Jeff Horn <jrhorn424@gmail.com> writes:
> The manual doesn't make explicit mention of org as a Babel source
> language. Well, it isn't listed in the supported languages, and an
> "org mode org source block" site search via Google didn't turn up the
> info I'm looking for.
>
There is support for Org code blocks, evaluation will generally result
in returning a modified (possibly exported) version of the code block
body.
>
> Basically, I tried using example blocks for a table I wrote, but noted
> that the key commands for org tables didn't work in the indirect
> buffer. Of course, I switched the example block to a source block, and
> specified "org" as the language.
>
> After editing in the indirect buffer, there are commas prepended to
> each line in the orignal buffer. These are not in the indirect buffer.
> Is this the intended behavior? See screenshot for reference.
>
> http://cl.ly/4C7P
>
Yes, this is the intended behavior. The commas protect your enclosing
source file from markup embedded in the org code block, otherwise a
top-level headline in the body of a code block could break outline
folding for the containing org file.
Best -- Eric
>
> TIA
next prev parent reply other threads:[~2011-01-25 19:36 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-25 18:52 Commas in org source blocks Jeff Horn
2011-01-25 19:36 ` Eric Schulte [this message]
2011-01-25 20:39 ` Jeff Horn
2011-01-25 21:32 ` Eric Schulte
2011-01-25 22:00 ` Jeff Horn
2011-01-26 1:48 ` Eric Schulte
2011-01-26 2:21 ` Jeff Horn
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=8739og6aje.fsf@gmail.com \
--to=schulte.eric@gmail.com \
--cc=emacs-orgmode@gnu.org \
--cc=jrhorn424@gmail.com \
/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).