emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Colin Baxter <m43cap@yandex.com>
To: Tom Gillespie <tgbugs@gmail.com>
Cc: , emacs-orgmode <emacs-orgmode@gnu.org>
Subject: Re: execute elisp link without prompt
Date: Sat, 22 May 2021 07:02:43 +0100	[thread overview]
Message-ID: <87wnrrz4os.fsf@yandex.com> (raw)
In-Reply-To: <CA+G3_PPVSwC7hC+rGQW6q-M4BApHW9ijE3B1BPyQ+K3seaQ97Q@mail.gmail.com> (Tom Gillespie's message of "Fri, 21 May 2021 15:01:03 -0700")

>>>>> Tom Gillespie <tgbugs@gmail.com> writes:

    >> In the end I've set as to nil as a local variable
    > If you want something a bit more secure you could use a function
    > that checks the block name ("some-block" in this example). Best!
    > Tom

    > (lambda (_lang _body) (not (string= "some-block" (plist-get (cadr
    > (org-element-at-point)) :name))))

    > #+begin_src elisp (setq-local org-confirm-babel-evaluate (lambda
    > (_lang _body) (not (string= "some-block" (plist-get (cadr
    > (org-element-at-point)) :name))))) #+end_src

    > #+name: some-block #+begin_src elisp

    > (message "yay!")  #+end_src

    > #+RESULTS: some-block : yay!

    > #+name: some-other-block #+begin_src elisp

    > (message "I ask to run") #+end_src

    > #+RESULTS: some-other-block : I ask to run

Thanks Tom. I'll try this.

Best wishes,

Colin Baxter.

      reply	other threads:[~2021-05-22  6:03 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-05-21 16:11 execute elisp link without prompt Colin Baxter
2021-05-21 16:28 ` Nicolas Goaziou
2021-05-21 19:17   ` Colin Baxter
2021-05-21 22:01     ` Tom Gillespie
2021-05-22  6:02       ` Colin Baxter [this message]

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:

  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=87wnrrz4os.fsf@yandex.com \
    --to=m43cap@yandex.com \
    --cc=emacs-orgmode@gnu.org \
    --cc=tgbugs@gmail.com \


* 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


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).