From: "Charles C. Berry" <ccberry@ucsd.edu>
To: Jiajie Chen <jiegec@qq.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: Bug: Feature Request: add 'org-babel-before-execute-hook' [8.3.4 (8.3.4-99-ga8e4a3-elpa @ /Users/macbookair/.emacs.d/elpa/org-20160704/)]
Date: Fri, 8 Jul 2016 09:09:55 -0700 [thread overview]
Message-ID: <alpine.OSX.2.20.1607080837390.623@charles-berrys-macbook.local> (raw)
In-Reply-To: <m2vb0gtn31.fsf@MacBookAirs-MacBook-Air.local>
On Fri, 8 Jul 2016, Jiajie Chen wrote:
[snip]
> Now there exists 'org-babel-after-execute-hook'. I want to implement
> this functionality: Check whether the path specified in `:file' exists
> in file system and throw an error if that does not exists. If there is
> `org-babel-before-execute-hook', we can do that instead of using
> advice. I love symmetry :)
>
Not a bug, of course.
You can check on things like file existence in a number of ways.
First, you can put emacs-lisp in header args, for example:
This evaluates when there is a file called "elisp" in the default
directory:
#+header: :eval (or (file-exists-p "elisp") "no")
#+BEGIN_SRC emacs-lisp :eval (file-exists-p "elisp")
"got it!"
#+END_SRC
and this does not (when there is no 'eeeelisp'):
#+header: :eval (or (file-exists-p "eeeelisp") "no")
#+BEGIN_SRC emacs-lisp
"got it!"
#+END_SRC
I've illustrated here with `:eval', but `:file' will also take such an
elisp snippet.
Alternatively, you can define a function for `org-confirm-babel-evaluate'
that will block evaluation.
Chuck
next prev parent reply other threads:[~2016-07-08 16:10 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-08 10:56 Bug: Feature Request: add 'org-babel-before-execute-hook' [8.3.4 (8.3.4-99-ga8e4a3-elpa @ /Users/macbookair/.emacs.d/elpa/org-20160704/)] Jiajie Chen
2016-07-08 16:09 ` Charles C. Berry [this message]
2016-07-08 23:43 ` Jiegec
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=alpine.OSX.2.20.1607080837390.623@charles-berrys-macbook.local \
--to=ccberry@ucsd.edu \
--cc=emacs-orgmode@gnu.org \
--cc=jiegec@qq.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 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.