ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Sietse Brouwer <sbbrouwer@gmail.com>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: \define a command with square-bracket arguments
Date: Fri, 28 Sep 2012 14:41:39 +0200	[thread overview]
Message-ID: <CAF=dkzxRaet7y4vye+Qc7a8zKeHW8KX27OT6GuNrkBDs-_7oyg@mail.gmail.com> (raw)
In-Reply-To: <BFDDBE81-10DA-4262-ACA7-5DFD1761A36D@gmail.com>

>> 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.
>
> In MkIV Hans didn’t add this check and in MkII he disabled is for command
> with three or less argument but even then you get only a message in the log
> when your command has no argument (i.e. a command with four argument
> complains only when it has zero argument but doesn’t complain when it
> has one to four arguments).

Wikified: http://wiki.contextgarden.net/Command/dodoubleempty
(I've been meaning to document that command for a while now. As a
complement to the existing explanation at
http://wiki.contextgarden.net/Commands_with_optional_arguments, I mean.)

--Sietse
___________________________________________________________________________________
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
___________________________________________________________________________________

  reply	other threads:[~2012-09-28 12:41 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
2012-09-27 16:23   ` Sietse Brouwer
2012-09-27 16:55   ` Wolfgang Schuster
2012-09-28 12:41     ` Sietse Brouwer [this message]
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='CAF=dkzxRaet7y4vye+Qc7a8zKeHW8KX27OT6GuNrkBDs-_7oyg@mail.gmail.com' \
    --to=sbbrouwer@gmail.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).