From: Henning Hraban Ramm <texml@fiee.net>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: [NTG-context] Re: defining macros
Date: Fri, 10 Jan 2025 23:04:27 +0100 [thread overview]
Message-ID: <64e13e2e-7142-4580-95de-c27ef5a94a6c@fiee.net> (raw)
In-Reply-To: <ce185701-7719-4a1b-bbed-4c67010e382b@freedom.nl>
Am 10.01.25 um 19:45 schrieb Hans Hagen:
> \tolerant\def\MyMacro[#1]#:#2%
> {\ifparameter#1\or
> (#1)
> \fi
> /#2/}
>
> \MyMacro[one]{two}
>
> \MyMacro{two}
Oops, another variant that I didn’t know.
I must unlearn my remaining MkII stuff…
>> When should I use brackets or other characters in a definition, when not?
> optionals normally have []
Yes, of course, but I’m often surprised by funny characters like #:
>> Which docs should I read?
>
> how about lowlevel-macros .. but haven't you read all of them by now ?
Apparently not diligently enough.
If at all. Can’t remember any more.
I’m not competent enough to rewrite e.g.
https://wiki.contextgarden.net/System_Macros/Handling_Arguments
Sigh.
HR
___________________________________________________________________________________
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
___________________________________________________________________________________
next prev parent reply other threads:[~2025-01-10 22:05 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-10 11:55 [NTG-context] " Henning Hraban Ramm
2025-01-10 18:45 ` [NTG-context] " Hans Hagen via ntg-context
2025-01-10 22:04 ` Henning Hraban Ramm [this message]
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=64e13e2e-7142-4580-95de-c27ef5a94a6c@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).