From: Tim Li <timli2013@outlook.com>
To: "ntg-context@ntg.nl" <ntg-context@ntg.nl>
Subject: the difference between \def and \define
Date: Mon, 15 Apr 2013 13:47:09 +0000 [thread overview]
Message-ID: <BLU152-W503A6F239F4CD7B4FF5C69A9CC0@phx.gbl> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 370 bytes --]
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?
[-- Attachment #1.2: Type: text/html, Size: 604 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 reply other threads:[~2013-04-15 13:47 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-15 13:47 Tim Li [this message]
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
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=BLU152-W503A6F239F4CD7B4FF5C69A9CC0@phx.gbl \
--to=timli2013@outlook.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).