On Thu, Jan 20, 2022 at 11:12 AM John Kitchin
wrote:
> It depends on what the src things look like. You might be able to just
> call ffap or some variant of it. Here is an example of the follow part that
> works for a file and url for me.
>
> #+BEGIN_SRC emacs-lisp
> (org-link-set-parameters
>
It depends on what the src things look like. You might be able to just call
ffap or some variant of it. Here is an example of the follow part that
works for a file and url for me.
#+BEGIN_SRC emacs-lisp
(org-link-set-parameters
"rstack"
:follow (lambda (path)
(ffap (or (ffap-url-at-point)
On Wed, Jan 19, 2022 at 12:18 PM John Kitchin
wrote:
> I am not sure this is quite what you are looking for. You could use a
> macro like this.
>
>
>
> {{{r-stack(((src1 . fade-out) (src2 . fade-in) (src3 . fade-out)))}}}
>
> * code :noexport:
>
> #+macro: r-stack (eval (r-stack $1))
>
>
On Wed, Jan 19, 2022 at 3:56 PM Berry, Charles
wrote:
> Matt,
>
> > On Jan 19, 2022, at 5:52 AM, Matt Price wrote:
> >
> > However, I'd really like to add a less verbose syntax, like this:
> >
> > #+begin_r-stack :frag (appear appear)
> > [[imglink1]]
> > [[imglink2]]
> > #+end_r-stack
> >
> >
Matt,
> On Jan 19, 2022, at 5:52 AM, Matt Price wrote:
>
> However, I'd really like to add a less verbose syntax, like this:
>
> #+begin_r-stack :frag (appear appear)
> [[imglink1]]
> [[imglink2]]
> #+end_r-stack
>
> My question is: will the exporter preserve information from these
I am not sure this is quite what you are looking for. You could use a macro
like this.
{{{r-stack(((src1 . fade-out) (src2 . fade-in) (src3 . fade-out)))}}}
* code :noexport:
#+macro: r-stack (eval (r-stack $1))
#+BEGIN_SRC emacs-lisp
(defun r-stack (src-alist)
"SRC-alist will be a string
