From: Wolfgang Schuster <schuster.wolfgang@gmail.com>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: the difference between \def and \define
Date: Mon, 15 Apr 2013 16:04:10 +0200 [thread overview]
Message-ID: <A9D8C1C4-F0D7-49F7-9228-675BDD1FF81C@gmail.com> (raw)
In-Reply-To: <BLU152-W503A6F239F4CD7B4FF5C69A9CC0@phx.gbl>
[-- Attachment #1.1: Type: text/plain, Size: 717 bytes --]
Am 15.04.2013 um 15:47 schrieb Tim Li <timli2013@outlook.com>:
> In plain TeX, we always use \def for creating a new macro, but in ConTeXt, sometimes it won't work, especially when making own chapter titles. The \def can produce the error message like this : "Argument of \... has an extra }". \define in ConTeXt can solve this problem.
>
> What's the difference between \def and \define? Can I use \define to replace all \def?
The \define command is a short form for \unexpanded\def which prevents commands to be expanded when used inside \edef or when passed to Lua.
Most of the high level commands are created to be unexpanded and expandable commands are used for internal functions.
Wolfgang
[-- Attachment #1.2: Type: text/html, Size: 1557 bytes --]
[-- Attachment #2: Type: text/plain, Size: 485 bytes --]
___________________________________________________________________________________
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:[~2013-04-15 14:04 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 [this message]
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
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=A9D8C1C4-F0D7-49F7-9228-675BDD1FF81C@gmail.com \
--to=schuster.wolfgang@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).