From: Wolfgang Schuster <schuster.wolfgang@googlemail.com>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: inaccessible control sequence
Date: Tue, 14 Apr 2009 15:53:37 +0200 [thread overview]
Message-ID: <19EDA121-6358-4E4B-BD13-418DD47E0344@gmail.com> (raw)
In-Reply-To: <fe8d59da0904140547h49fd01fdl5bfae4d7d5b2cac5@mail.gmail.com>
Am 14.04.2009 um 14:47 schrieb luigi scarso:
> On Fri, Apr 10, 2009 at 12:56 PM, Hans Hagen <pragma@wxs.nl> wrote:
> luigi scarso wrote:
> \def\@@FOO{FOO}
> \starttext
> \@@FOO
> \stoptext
>
> works in mkiv minimals ,
> but not in an old mkii context of mine
> (inaccessible control sequence) .
>
> I suppose that it's ok .
>
> no, it means that we have a missing \protect .. upto you to figure
> out where so that we can fix it
>
>
> This compiles ok in luatex
>
> %%%%test-inaccesible-luatex.tex
> \immediate\write16{===>catcode of @ is:\the\numexpr\catcode`@\relax}
> \def\@@FOO{FOO}
> \@@FOO
> \bye
Can you also explain why it did work and also why this is a very bad
idea!
Wolfgang
___________________________________________________________________________________
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 : https://foundry.supelec.fr/projects/contextrev/
wiki : http://contextgarden.net
___________________________________________________________________________________
next prev parent reply other threads:[~2009-04-14 13:53 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-10 10:02 luigi scarso
2009-04-10 10:44 ` Wolfgang Schuster
2009-04-10 10:56 ` Hans Hagen
2009-04-10 12:23 ` luigi scarso
2009-04-14 12:47 ` luigi scarso
2009-04-14 13:53 ` Wolfgang Schuster [this message]
2009-04-14 14:11 ` luigi scarso
2009-04-14 14:26 ` Wolfgang Schuster
2009-04-14 14:31 ` Hans Hagen
2009-04-14 14:54 ` luigi scarso
2009-04-14 16:10 ` luigi scarso
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=19EDA121-6358-4E4B-BD13-418DD47E0344@gmail.com \
--to=schuster.wolfgang@googlemail.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).