ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Henning Hraban Ramm <texml@fiee.net>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: [NTG-context] defining macros
Date: Fri, 10 Jan 2025 12:55:49 +0100	[thread overview]
Message-ID: <d48d5348-490d-440a-b629-15f3e3888c50@fiee.net> (raw)

Hi, I just recognized that I’m not sure how to define a macro with 
optional and mandatory arguments the best way.

E.g. (oldfashioned)

\def\doMyMacro[#1]#2%
{Do something ... \iffirstargument #1\fi #2}

\def\MyMacro%
{\dosingleargument\doMyMacro}


Is this still the way to do it?
Does it also work with \define?

I have more questions like that:

 From Wolfgang’s presentation (article in progress…) I know all the cool 
stuff for modules (namespaces, setup helpers…), I also know the Lua way 
of interface.implement, but how to combine those?

When should I use brackets or other characters in a definition, when not?

Which docs should I read?


Hraban
___________________________________________________________________________________
If your question is of interest to others as well, please add an entry to the Wiki!

maillist : ntg-context@ntg.nl / https://mailman.ntg.nl/mailman3/lists/ntg-context.ntg.nl
webpage  : https://www.pragma-ade.nl / https://context.aanhet.net (mirror)
archive  : https://github.com/contextgarden/context
wiki     : https://wiki.contextgarden.net
___________________________________________________________________________________

             reply	other threads:[~2025-01-10 11:56 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-01-10 11:55 Henning Hraban Ramm [this message]
2025-01-10 18:45 ` [NTG-context] " Hans Hagen via ntg-context
2025-01-10 22:04   ` Henning Hraban Ramm
2025-01-10 23:19     ` Hans Hagen
2025-01-11  9:21       ` Henning Hraban Ramm
2025-01-11 11:30         ` Hans Hagen via ntg-context
2025-01-14 17:50           ` Henning Hraban Ramm
2025-01-14 18:27             ` Hans Hagen

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=d48d5348-490d-440a-b629-15f3e3888c50@fiee.net \
    --to=texml@fiee.net \
    --cc=ntg-context@ntg.nl \
    /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.
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 NNTP newsgroup(s).