emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Martin Steffen <msteffen@ifi.uio.no>
To: emacs-orgmode@gnu.org
Subject: question about links, macros + org-publish and "parametrization"
Date: Tue, 28 May 2024 12:02:56 +0200	[thread overview]
Message-ID: <xk92plt69ru7.fsf@galneryus.ifi.uio.no> (raw)



Hi,

I got a question whether the following is possible, when using
org-publish. Concretely I generate with org-publish markdown-files (that
ultimately are turned to HTML), but I guess the question is not specific
for this choice of a ``publication-process''.'


The whole content consists of quite a number of files, and in particular
has quite many html-links, and the links change (each year, each
semester) and they change in ``systematic ways''


What has been  for instance

   https://www.gitpages.io/somelecture/fall23/exercises

will have to be changed for the next round to

   https://www.gitpages.io/somelecture/fall24/exercises

(and there are links for many things beside exercises, and also they
have to be changed analogously).


The way I make that smooth is I define

#LINK: exercises-web https://www.gitpages.io/somelecture/fall23/exercises


and then, When the semester comes, replace all occurrences of fall23 to
fall24. Even if there are quite a number of such link definitions (for
all kind of information), it's straightforward. It's systematically
organized, and if all the link definitions are centralized in some file
collectionoflinks.org or similar that is #INCLUDE:-ed into all the
other files that work with this links, then ``porting'' of the whole
set-up to a new semester is quite easy and robust.

So I am happy with that, but I wonder if I could make it even more
parametrized. Like


      combining macros with links


like that "fall23" is an argument to a macros, which then builds up a
link. But that does not to work in a naive way, like


#+MACRO: semester fall24
#+LINK: https://www.gitpages.io/somelecture/{{{semester}}}/exercises


since macros do replacement in "text" (not in those #+-"meta-commands").

I tried parametrized macros_

#+MACRO: parametricexercizes  https://www.gitpages.io/somelecture/$1/exercises


and that half-way works. I.e., if I do

               parametricexercizes(fall24)  (*)

it works in that it results in a page with a correct link, but that's
not quite what I want, for 2 reasons. Really useful would the
parametrization if one could do

  parametricexercizes(semester)

where semester is a macro, not a literal "fall24". The second reason is
that the use as in (*) is not really useful, what I am  really after is
something like

       [[parametricexercizes(fall24)][the exercises are here]]

and the combination of macros inside [[ .... ]] does not work either.



Maybe there are other ways to achieve ``parametrization'' (or maybe not,
I have not worked much with macros in Org), any ideas?

best, Martin













             reply	other threads:[~2024-05-28 10:04 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-05-28 10:02 Martin Steffen [this message]
2024-05-29  8:44 ` question about links, macros + org-publish and "parametrization" Fraga, Eric
2024-05-30  3:52   ` Martin Steffen
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=xk92plt69ru7.fsf@galneryus.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).