From: Hans Hagen <pragma@wxs.nl>
Cc: ntg-context@ntg.nl
Subject: Re: Re[2]: Broken catcodes
Date: Mon, 27 May 2002 18:44:05 +0200 [thread overview]
Message-ID: <5.1.0.14.1.20020527183828.02d4a338@server-1> (raw)
In-Reply-To: <200205271544.RAA15353@lps.univ-lille1.fr>
At 05:44 PM 5/27/2002 +0200, you wrote:
>Thanks, it works again now
>(it worked before the change without \unprotect ... \protect though).
then that was a bug (probably a forgotten \protect
>Where can I read about \protect \unprotect in ConTeXt? the mechanism
>looks very different from the \protect I know in LaTeX, I did not try
>to understand this bit of ConTeXt (and many other ;-) up to now...
ah, in context \protect does something like \makeatletter in latex (only in
context ! and ? are also used for protection purposes)
[afaik in latex there is a \protect that has to do with preventing
expansion in toc entries; context does not need this since normally toc
entries are not expand them at all; in context expansion only can be
problematic in tests, which is why some commands are defined with
\unexpanded\def, which actually in etex is equivalent to \protected \def,
which clashes with my own \protected, and (lucky me) \unexpanded is also an
etex primitive with a complete different meaning; lesson: don't confuse
\protect with latex \protect and don't mix up \unexpanded with etex's
\protected]
anyhow, not something for users to bother about
Hans
-------------------------------------------------------------------------
Hans Hagen | PRAGMA ADE | pragma@wxs.nl
Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
tel: +31 (0)38 477 53 69 | fax: +31 (0)38 477 53 74 | www.pragma-ade.com
-------------------------------------------------------------------------
information: http://www.pragma-ade.com/roadmap.pdf
documentation: http://www.pragma-ade.com/showcase.pdf
-------------------------------------------------------------------------
next parent reply other threads:[~2002-05-27 16:44 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <Your message of "Mon, 27 May 2002 17:32:51 +0200." <5.1.0.14.1.20020527173210.03bb2ea8@server-1>
[not found] ` <200205271544.RAA15353@lps.univ-lille1.fr>
2002-05-27 16:44 ` Hans Hagen [this message]
2002-05-25 20:17 Hans Hagen
2002-05-25 21:46 ` Re[2]: " Giuseppe Bilotta
2002-05-26 17:39 ` Hans Hagen
[not found] ` <pragma@wxs.nl>
2002-05-27 15:27 ` Daniel Flipo
2002-05-27 15:32 ` 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=5.1.0.14.1.20020527183828.02d4a338@server-1 \
--to=pragma@wxs.nl \
--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).