From: Eric Schulte <schulte.eric@gmail.com>
To: Rainer M Krug <r.m.krug@gmail.com>
Cc: emacs-orgmode <emacs-orgmode@gnu.org>
Subject: Re: [babel] set post tangle hook on per file basis - evalu
Date: Tue, 09 Aug 2011 08:33:14 -0400 [thread overview]
Message-ID: <87ipq6hhxt.fsf@gmail.com> (raw)
In-Reply-To: CAGhLh6G5kqhQt0xDZWTdsSWrnah8v0nBoxJ=EvU7us3U7FcK7Q@mail.gmail.com
Rainer M Krug <r.m.krug@gmail.com> writes:
> Hi
>
> for different files, I put different things in the post-tangle hook. At tha
> moment, I have an emacs-lisp code block, which I evaluate before I tangle,
> but I forget this sometimes - so y question: is it possible (and think to
> remember that it is, but I can't find how) to evaluate a source code block
> upon opening of the file, or set the org-babel-post-tangle-hook in a
> different way upon opening of the org file?
>
> The code block I am using at the moment is:
>
> ** Evaluate to run post tangle script
> #+begin_src emacs-lisp :results silent :tangle no :exports none
> (add-hook 'org-babel-post-tangle-hook
> (
> lambda ()
> (call-process-shell-command "./postTangleScript.sh" nil
> 0 nil)
> )
> )
> #+end_src
>
Hi Rainer,
I like to use file local variables [1] to do per-file Org-mode
configuration and customization this is an easy way to set the local
value of a variable every time the file is opened.
I think you could use file local variables to evaluate arbitrary elisp
when a file is opened in which case you could evaluate a named code
block with something like `(sbe code-block-name)'.
Best -- Eric
Footnotes:
[1] [[info:emacs#Specifying%20File%20Variables][info:emacs#Specifying File Variables]]
--
Eric Schulte
http://cs.unm.edu/~eschulte/
next prev parent reply other threads:[~2011-08-09 13:40 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-08 8:12 [babel] set post tangle hook on per file basis - evalu Rainer M Krug
2011-08-09 12:33 ` Eric Schulte [this message]
2011-08-09 13:49 ` Rainer M Krug
2011-08-09 17:14 ` Eric Schulte
2011-08-10 7:33 ` Rainer M Krug
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=87ipq6hhxt.fsf@gmail.com \
--to=schulte.eric@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).