From: Marco Patzer <homerow@lavabit.com>
To: ntg-context@ntg.nl
Subject: Re: \define a command with square-bracket arguments
Date: Thu, 27 Sep 2012 18:16:51 +0200 [thread overview]
Message-ID: <20120927181651.0fbd2251@homerow> (raw)
In-Reply-To: <CAF=dkzyYuZxVdj0HGXdoF4EfdP2duZiAL08cv7K=hs5dNg9Odw@mail.gmail.com>
2012-09-27 Sietse Brouwer <sbbrouwer@gmail.com>:
Hi Sietse,
> As I understand it, \define[2] is preferred over \def#1#2 because it
> refuses to overwrite existing commands.
\define overwrites existing commands with pleasure. In contrast to
\def it prints a message to the log file: “\mycommand is already
defined”.
> Can I use \define, or a related command, to define a command that
> takes square-bracket arguments, like so:
> \mycommand[...][...]
\def\mycommand
{\dodoubleempty\domycommand}
\def\domycommand [#1][#2]
{first: #1, second: #2}
\mycommand [foo] [bar]
\mycommand [foo][bar]
\mycommand [foo]
Question for the others: What's the difference of \dodoubleargument
and \dodoubleempty? I expected \dodoubleargument to throw an error
since the arguments are supposed to be mandatory.
Marco
___________________________________________________________________________________
If your question is of interest to others as well, please add an entry to the Wiki!
maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context
webpage : http://www.pragma-ade.nl / http://tex.aanhet.net
archive : http://foundry.supelec.fr/projects/contextrev/
wiki : http://contextgarden.net
___________________________________________________________________________________
next prev parent reply other threads:[~2012-09-27 16:16 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-27 15:45 Sietse Brouwer
2012-09-27 15:59 ` Thomas A. Schmitz
2012-09-27 16:16 ` Marco Patzer [this message]
2012-09-27 16:23 ` Sietse Brouwer
2012-09-27 16:55 ` Wolfgang Schuster
2012-09-28 12:41 ` Sietse Brouwer
2012-09-28 13:41 ` 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=20120927181651.0fbd2251@homerow \
--to=homerow@lavabit.com \
--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).