emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Martin Steffen <msteffen@ifi.uio.no>
To: Org Mode List <emacs-orgmode@gnu.org>
Subject: Re: question about links, macros + org-publish and "parametrization"
Date: Thu, 30 May 2024 05:52:31 +0200	[thread overview]
Message-ID: <xk92mso83qio.fsf@afram.ifi.uio.no> (raw)
In-Reply-To: <877cfdovmb.fsf@ucl.ac.uk> (Eric Fraga's message of "Wed, 29 May 2024 08:44:36 +0000")

>>>>> "Fraga," == Fraga, Eric <e.fraga@ucl.ac.uk> writes:

    Fraga,> Hello,

    Fraga,> I'm not entirely sure if I am missing something but, in case

thanks, it was more that I was missing something. I tried to combine
links and macros in a naive ways (without much studying the manual), so
I thought perhaps nesting is not possible (or there is another way).

Your suggestion solves my "problem" and makes the set-up a bit more
"parametric" and easier to adapt, without that one forgets some bits,
which is very nice.

best, Martin



    Fraga,> it helps, macros can themselves invoke other macros and
    Fraga,> macros can make use of [[target][desc]] syntax directly.
    Fraga,> Can you not build up a hierarchy of macros that would
    Fraga,> achieve what you want, along these lines:

    Fraga,> #+macro: link [[file:t.org][$1]]

    Fraga,> #+macro: target {{{link($1)}}}

    Fraga,> This is some text where I can look at {{{target(blah)}}}

    Fraga,> HTH, eric

    Fraga,> -- : Eric S Fraga, with org release_9.6.19-1230-g407a55 in
    Fraga,> Emacs 30.0.50


  reply	other threads:[~2024-05-30  3:58 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-05-28 10:02 question about links, macros + org-publish and "parametrization" Martin Steffen
2024-05-29  8:44 ` Fraga, Eric
2024-05-30  3:52   ` Martin Steffen [this message]
2024-05-30  5:03     ` Martin Steffen
2024-05-30  8:40       ` Fraga, Eric
2024-05-30 11:25         ` Martin Steffen
2024-05-30 16:28       ` Max Nikulin
2024-05-30 16:33         ` Ihor Radchenko
2024-05-31 10:29           ` Max Nikulin
2024-05-29 13:35 ` Ihor Radchenko

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

  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=xk92mso83qio.fsf@afram.ifi.uio.no \
    --to=msteffen@ifi.uio.no \
    --cc=emacs-orgmode@gnu.org \
    /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 public inbox

	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

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