From: "Charles C. Berry" <cberry@tajo.ucsd.edu>
To: Chris Maier <christopher.maier@gmail.com>
Cc: emacs-orgmode@gnu.org, Rainer M Krug <r.m.krug@gmail.com>
Subject: Re: [BABEL] Tangling to a hierarchy of files?
Date: Wed, 19 Jan 2011 08:20:52 -0800 [thread overview]
Message-ID: <Pine.LNX.4.64.1101190818210.15631@tajo.ucsd.edu> (raw)
In-Reply-To: <AANLkTinvb9F2LGfpiy9RnPB8gBkEGQxL3RpkHXYcWkxs@mail.gmail.com>
[-- Attachment #1: Type: TEXT/PLAIN, Size: 1703 bytes --]
On Wed, 19 Jan 2011, Chris Maier wrote:
> On Wed, Jan 19, 2011 at 5:05 AM, Rainer M Krug <r.m.krug@gmail.com> wrote:
>> On 01/19/2011 08:22 AM, Eric Schulte wrote:
>>>
>>> In addition to the solution Charles posted, it is possible to put
>>> arbitrary elisp forms into header arguments, so the following
>>> alternative to your block above will create the directory (if it doesn't
>>> already exist) whenever the block is tangled or evaluated.
>>>
>>> #+begin_src clojure :tangle (prog1 "src/foo.clj" (make-directory "src" "."))
>>> (ns foo)
>>>
>>> (defn my-inc [x]
>>> (+ x 1))
>>> #+end_src
>
> This will do what I'm looking for, thanks!
>
> Is there a place where this and the eval-on-startup trick Charles
> posted are documented? If so, I missed it, and these are both really
> useful to know.
C-h i, then navigate to
(emacs)Top > Customization > Variables > File Variables > Specifying File
Variables
'eval' is a special kind of file variable.
Chuck
>
>> Would it be possible, to include this into tangling, i.e. if the folder
>> in which the source file should be created does not exist, create it?
>>
>> I remember vaguely a discussion along these lines some time ago, but I
>> don't remember the outcome?
>
> This would be a great feature to have. Eric's embedded Lisp code
> trick will do the job, but I can imagine that it would get cumbersome
> for more complex projects.
>
> Thanks for all the help, everyone!
>
> Chris
>
Charles C. Berry Dept of Family/Preventive Medicine
cberry@tajo.ucsd.edu UC San Diego
http://famprevmed.ucsd.edu/faculty/cberry/ La Jolla, San Diego 92093-0901
[-- Attachment #2: Type: text/plain, Size: 201 bytes --]
_______________________________________________
Emacs-orgmode mailing list
Please use `Reply All' to send replies to the list.
Emacs-orgmode@gnu.org
http://lists.gnu.org/mailman/listinfo/emacs-orgmode
next prev parent reply other threads:[~2011-01-19 16:20 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 [this message]
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
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=Pine.LNX.4.64.1101190818210.15631@tajo.ucsd.edu \
--to=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).