emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Ken Mankoff <mankoff@gmail.com>
To: Lawrence Bottorff <borgauf@gmail.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: Babel language "org"?
Date: Sat, 04 Apr 2015 11:47:21 -0400	[thread overview]
Message-ID: <m21tjz3ng6.fsf@gmail.com> (raw)
In-Reply-To: <CAFAhFSV7W=x5mvACyG8O8WjXAMTB-7mxXMEjuVQLv=r6_d1L4Q@mail.gmail.com>

If it weren't wrapped, it would be exported and not show up in the document text.


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
> . . . 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

  reply	other threads:[~2015-04-04 15:47 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 [this message]
2015-04-04 16:40   ` Lawrence Bottorff

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:

  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=m21tjz3ng6.fsf@gmail.com \
    --to=mankoff@gmail.com \
    --cc=borgauf@gmail.com \
    --cc=emacs-orgmode@gnu.org \


* 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


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).