emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Lawrence Bottorff <borgauf@gmail.com>
To: emacs-orgmode@gnu.org
Subject: Re: Babel language "org"?
Date: Sat, 4 Apr 2015 12:40:06 -0400	[thread overview]
Message-ID: <CAFAhFSVoOdDyico2LRfdTpakLMKBqJy8DKW8+qufyaX=ZWV_fw@mail.gmail.com> (raw)
In-Reply-To: <m21tjz3ng6.fsf@gmail.com>

[-- Attachment #1: Type: text/plain, Size: 2270 bytes --]

Yes, it's being used as a sort of escape backslash, sort of like when you
do \" to have the quotation mark actually show up, or like the <pre> tag in
html. That's what I thought at first too, i.e., so the #+TITLE: etc. won't
be taken literally by org-mode. But I guess I meant to ask, Is this
orgmode's "official escape backslash" mechanism? What about #+BEGIN_EXAMPLE
... #+END_EXAMPLE or #+BEGIN_QUOTE ... #+END_QUOTE?  It seems like putting
org-mode "code" inside of babel code wrapper would be something about
writing a(n eventual) second, "external" org file while still the first org
file. Or, simpler, I might create a library, i.e., an org file with useful
org-mode templates etc. and have them accessible a la "linked data," the
unique key being the #+NAME: field. But again, I'm very curious, what
exactly is babel's relationship to "org code"? What qualifies as "org
code," as far as babel is concerned?

On Sat, Apr 4, 2015 at 11:47 AM, Ken Mankoff <mankoff@gmail.com> wrote:

>
> If it weren't wrapped, it would be exported and not show up in the
> document text.
>
>   -k.
>
> On 2015-04-04 at 11:41, Lawrence Bottorff <borgauf@gmail.com> wrote:
> > I'm taking a closer look at Eric Neilsen's "Emacs org-mode examples and
> > cookbook," specifically the org file Eric sent me. And right off the bat
> I
> > see something interesting:
> >
> > ** General metadata
> >
> > An initial group sets the metadata used in any title pages, headers,
> > footers, etc. used by the various exporters:
> >
> > #+NAME: orgmode-header-metadata
> > #+BEGIN_SRC org
> > #+TITLE:     Emacs org-mode examples
> > #+AUTHOR:    Eric H. Neilsen, Jr.
> > #+EMAIL:     neilsen@fnal.gov
> > #+END_SRC
> >
> > . . . which shows up in the final html version as just
> >
> > #+TITLE:     Emacs org-mode examples
> > #+AUTHOR:    Eric H. Neilsen, Jr.
> > #+EMAIL:     neilsen@fnal.gov
> >
> > Why did he use what looks like babel source formatting? What is gained
> from
> > having org "code" as literate programming? Any docs talking specifically
> > about this, best practices? My first guess is he's just using this as an
> > org-to-html formatting convention, but, again, how much of "org code"
> > (whatever we call "org code") can I put in babel source containers?
> >
> > LB
>
>

[-- Attachment #2: Type: text/html, Size: 3187 bytes --]

      reply	other threads:[~2015-04-04 16:40 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-04-04 15:41 Babel language "org"? Lawrence Bottorff
2015-04-04 15:47 ` Ken Mankoff
2015-04-04 16:40   ` Lawrence Bottorff [this message]

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='CAFAhFSVoOdDyico2LRfdTpakLMKBqJy8DKW8+qufyaX=ZWV_fw@mail.gmail.com' \
    --to=borgauf@gmail.com \
    --cc=emacs-orgmode@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 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).