execute elisp link without prompt

execute elisp link without prompt

[Colin Baxter]

Hello,

I have an elisp link of the form (without spaces, of course)
[ [elisp:(dired-other-window "/path/to/directory/") ][ Directory ] ].

The link works with the directory in appearing in dired window. However,
when I first click on the link, a dialog box is brought up asking me if
a I wish to execute the command. Of course, I do - and I click 'Yes'.

How can I go to link directly without being interrogated by the dialog
box?

Best wishes,

Colin Baxter.

Re: execute elisp link without prompt

[Nicolas Goaziou]

Hello,

Colin Baxter <m43cap@yandex.com> writes:

> I have an elisp link of the form (without spaces, of course)
> [ [elisp:(dired-other-window "/path/to/directory/") ][ Directory ] ].
>
> The link works with the directory in appearing in dired window. However,
> when I first click on the link, a dialog box is brought up asking me if
> a I wish to execute the command. Of course, I do - and I click 'Yes'.
>
> How can I go to link directly without being interrogated by the dialog
> box?

See org-link-elisp-confirm-function.

Regards,
-- 
Nicolas Goaziou

Re: execute elisp link without prompt

[Colin Baxter]

Dear Nicolas,

>>>>> Nicolas Goaziou <mail@nicolasgoaziou.fr> writes:

    > Hello, Colin Baxter <m43cap@yandex.com> writes:

    >> I have an elisp link of the form (without spaces, of course) [
    >> [elisp:(dired-other-window "/path/to/directory/") ][ Directory ]
    >> ].
    >> 
    >> The link works with the directory in appearing in dired
    >> window. However, when I first click on the link, a dialog box is
    >> brought up asking me if a I wish to execute the command. Of
    >> course, I do - and I click 'Yes'.
    >> 
    >> How can I go to link directly without being interrogated by the
    >> dialog box?

    > See org-link-elisp-confirm-function.

Thank you. I tried setting 'org-link-elisp-confirm-function' to y-or-n-p
as suggested by ol.el, but it gave me a dialog box, as before, which I
had to click. In the end I've set as to nil as a local variable:

#+begin_src elisp
eval: (set (make-local-variable 'org-link-elisp-confirm-function) nil)
#+end_src

The doc-string says it's risky when used as a local variable, but it
seems to work. The variable returns to the global default 'yes-or-no-p'
when the buffer is killed.

Best wishes,

Re: execute elisp link without prompt

[Tom Gillespie]

> 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

Re: execute elisp link without prompt

[Colin Baxter]

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