From: "Eric Schulte" <schulte.eric@gmail.com>
To: Chris Maier <christopher.maier@gmail.com>
Cc: emacs-orgmode@gnu.org, "Charles C. Berry" <cberry@tajo.ucsd.edu>,
Rainer M Krug <r.m.krug@gmail.com>
Subject: Re: [BABEL] Tangling to a hierarchy of files?
Date: Wed, 19 Jan 2011 20:37:16 -0700 [thread overview]
Message-ID: <87bp3c1c0e.fsf@gmail.com> (raw)
In-Reply-To: AANLkTi=DJsosp-PSTRn7KycP8DJoOF7YjHEgOFGu8tC1@mail.gmail.com
>
> A customization variable would be fantastic. Could it be done such
> that it could be applied (or not applied, according to taste) to a
> sub-tree of your Org file? That way you could have it disabled on
> whatever code you might be currently working on so you still see the
> error messages if you mistype. Then, when you're satisfied with all
> your tangle paths, you could flip the switch on that sub-tree and have
> Org do everything for you.
>
This has now been added as a new :mkdirp code block header argument, so
it can be set on the block, subtree, file, language, or global level
(see http://orgmode.org/manual/Using-header-arguments.html).
#+begin_src language :mkdirp yes :tangle nested/directories/target.ext
code body
#+end_src
Cheers -- Eric
next prev parent reply other threads:[~2011-01-20 3:37 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-19 4:02 [BABEL] Tangling to a hierarchy of files? Christopher Maier
2011-01-19 6:45 ` Charles C. Berry
2011-01-19 7:22 ` Eric Schulte
2011-01-19 10:05 ` Rainer M Krug
2011-01-19 11:59 ` Chris Maier
2011-01-19 12:06 ` Rainer M Krug
2011-01-19 16:20 ` Charles C. Berry
2011-01-19 16:27 ` Chris Maier
2011-01-19 17:41 ` Eric Schulte
2011-01-19 18:18 ` Chris Maier
2011-01-20 3:37 ` Eric Schulte [this message]
2011-01-20 10:06 ` Rainer M Krug
2011-01-21 2:11 ` Chris Maier
2011-01-20 9:09 ` Christopher Witte
2011-01-20 16:11 ` Eric Schulte
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=87bp3c1c0e.fsf@gmail.com \
--to=schulte.eric@gmail.com \
--cc=cberry@tajo.ucsd.edu \
--cc=christopher.maier@gmail.com \
--cc=emacs-orgmode@gnu.org \
--cc=r.m.krug@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).