From: "Sébastien Vauban" <wxhgmqzgwmuf-geNee64TY+gS+FvcfC7Uqw@public.gmane.org>
To: emacs-orgmode-mXXj517/zsQ@public.gmane.org
Subject: Re: Limited #+INCLUDE ?
Date: Mon, 26 Apr 2010 10:32:30 +0200 [thread overview]
Message-ID: <87k4ruy5pd.fsf@mundaneum.com> (raw)
In-Reply-To: 874oj2v2a6.fsf@tandberg.com
Hi Giles,
Giles Chamberlin wrote:
> I've been using org-mode for some course work: "write an essay about
> your software including the interesting bits, add all source code in an
> appendix".
>
> #+INCLUDE solves the inclusion of source code files very nicely - I'm
> guaranteed that my document includes the latest versions, type set as I
> wish.
>
> Unfortunately at the moment I'm cutting and pasting the snippets of
> "interesting" code into the body of the essay. What I'd like to do is
> be able to label interesting regions of code in the source file and then
> import the labelled blocks into my essay. Is there a way of doing this?
Have a look at Org-Babel.
Though, it means your source code would be *inside* your Org document, and you
would have to "tangle" it (generate it) from there.
Seb
--
Sébastien Vauban
_______________________________________________
Emacs-orgmode mailing list
Please use `Reply All' to send replies to the list.
Emacs-orgmode-mXXj517/zsQ@public.gmane.org
http://lists.gnu.org/mailman/listinfo/emacs-orgmode
next prev parent reply other threads:[~2010-04-26 8:32 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-23 11:25 Limited #+INCLUDE ? Giles Chamberlin
2010-04-26 8:32 ` Sébastien Vauban [this message]
2010-04-26 19:40 ` Dan Davison
2010-04-27 0:34 ` Mark Elston
2010-04-27 2:19 ` Dan Davison
2010-04-28 0:52 ` Mark Elston
2010-04-27 8:27 ` Eric S Fraga
2010-04-27 10:25 ` Darlan Cavalcante Moreira
2010-04-27 15:12 ` Eric Schulte
2010-04-27 17:26 ` Dan Davison
2010-04-27 17:58 ` Eric Schulte
2010-04-27 18:27 ` Giles Chamberlin
2010-04-27 17:52 ` Samuel Wales
2010-04-27 19:19 ` Dan Davison
2010-04-27 21:56 ` Carsten Dominik
2010-04-29 23:14 ` Samuel Wales
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=87k4ruy5pd.fsf@mundaneum.com \
--to=wxhgmqzgwmuf-genee64ty+gs+fvcfc7uqw@public.gmane.org \
--cc=emacs-orgmode-mXXj517/zsQ@public.gmane.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.