Re: Call code block via link?

2022-10-04 Thread Ihor Radchenko
Felix Dorner writes: >> [[elisp:(some elisp sexp)][Click here to do X]] >> >> Neat! When I open the link I always get a message each time, "Execute ... > as elisp?" Is there a way to get rid of that message? See https://orgmode.org/manual/Code-Evaluation-Security.html -- Ihor Radchenko, Org

Re: Call code block via link?

2022-10-04 Thread Felix Dorner
Eric, > > [[elisp:(some elisp sexp)][Click here to do X]] > > Neat! When I open the link I always get a message each time, "Execute ... as elisp?" Is there a way to get rid of that message? -- Linux. The choice of a GNU generation.

Re: Call code block via link?

2022-09-19 Thread Fraga, Eric
On Saturday, 10 Sep 2022 at 07:15, Felix Dorner wrote: > Clicking/following the link would execute the call and my password > ready to paste elsewhere. Feasible? I have links of the form [[elisp:(some elisp sexp)][Click here to do X]] -- : Eric S Fraga, with org release_9.5.4-768-g5bb699 in

Re: Call code block via link?

2022-09-10 Thread Ihor Radchenko
Felix Dorner writes: > I have a silenced codeblock, that I postprocess to push the result (a > password) onto the kill-ring, and then returns "Password copied" (showing > in the status line). This works very nicely. I'm now looking for the cherry > on the cake: I'd like to render the #+CALL as a

Call code block via link?

2022-09-09 Thread Felix Dorner
I have a silenced codeblock, that I postprocess to push the result (a password) onto the kill-ring, and then returns "Password copied" (showing in the status line). This works very nicely. I'm now looking for the cherry on the cake: I'd like to render the #+CALL as a link, e.g. something like,