ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Alan BRASLAU <alan.braslau@cea.fr>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Cc: pragma@wxs.nl, "Thomas A. Schmitz" <thomas.schmitz@uni-bonn.de>
Subject: Re: the difference between \def and \define
Date: Tue, 16 Apr 2013 13:14:11 +0200	[thread overview]
Message-ID: <20130416131411.026762a9@iram-hb-003386.extra.cea.fr> (raw)
In-Reply-To: <516D2948.1040404@wxs.nl>

Since the question has been raised about understanding \define, etc.
indeed some use remains a bit unclear (to me).

On Tue, 16 Apr 2013 12:34:48 +0200
Hans Hagen <pragma@wxs.nl> wrote:

> there is a commented blob that implements thinsg like this
> 
> \starttext
>      \define[2]\whatevera{#1+#2}
>      \whatevera{A}{B}
>      \define[me][too][2]\whateverb{#1+#2+#3+#4}
>      \whateverb[A]{B}{C}
>      \whateverb[A][B]{C}{D}
>      \define[alpha][beta][gamma][delta]\whateverc{#1+#2+#3+#4}
>      \whateverc[P][Q]
> \stoptext
> 
> but it's just an old idea.

I am perhaps a bit bewildered today... but I do not understand the
above. It gets too tricky for me!

In fact, I do not understand well the handling of arguments,
especially optional variants.
For example,
	\define[1]\Index{\index{#1}#1}
can be handy. But let's say that I want to be able to use a variant:
	\Index[alpha]{$\alpha$}
(\index[alpha]{$\alpha$}$\alpha$)

Or, maybe, I might like to handle authors:
	\define[2]\Author{\index{#2, #1}#1 #2}
	\Author{Thomas A.}{Schmitz}
But what if I were to type \Author{Aristotle}?

Alan

P.S. I indeed like the idea of the suggestion:

\define[one,two,three]\whatever{first: #one second: #two third: #three}

On 4/16/2013 11:10 AM, Thomas A. Schmitz wrote:
> It certainly isn't an urgent need, but having
>
> \define[one,two,three]
>
> wouldn't be absurd, now would it?
___________________________________________________________________________________
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:[~2013-04-16 11:14 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-04-15 13:47 Tim Li
2013-04-15 14:04 ` Wolfgang Schuster
2013-04-15 14:07 ` Marco Patzer
2013-04-15 14:12   ` Hans Hagen
2013-04-15 14:21     ` Wolfgang Schuster
2013-04-16  8:42       ` Hans Hagen
2013-04-16  9:05         ` Marco Patzer
2013-04-16  9:10           ` Thomas A. Schmitz
2013-04-16 10:11             ` Marco Patzer
2013-04-16 16:03               ` Hans Hagen
2013-04-16 10:34             ` Hans Hagen
2013-04-16 11:14               ` Alan BRASLAU [this message]
2013-04-16 12:01                 ` Hans Hagen
2013-04-15 14:26     ` Marco Patzer

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=20130416131411.026762a9@iram-hb-003386.extra.cea.fr \
    --to=alan.braslau@cea.fr \
    --cc=ntg-context@ntg.nl \
    --cc=pragma@wxs.nl \
    --cc=thomas.schmitz@uni-bonn.de \
    /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).