From: "Giuseppe Bilotta" <oblomov@freemail.it>
Cc: "ConTeXt" <ntg-context@ntg.nl>
Subject: Re: Wrong catcode?
Date: Wed, 3 Jan 2001 14:07:02 +0100 [thread overview]
Message-ID: <022f01c075db$1f2b6880$a3ccfea9@nuovo> (raw)
In-Reply-To: <3.0.6.32.20010102184011.0150fba0@pop.wxs.nl>
Hans Hagen wrote:
> At 12:42 PM 12/31/00 +0100, Giuseppe Bilotta wrote:
> >Hello, I'm using ConTeXt 2000.12.14
> >
> >It looks like some <protection> leaked through some macros, since ? has
> >catcode 11 instead of 12. It's not my document's fault, since
> >\showthe\catcode`? gives 11 even at the very top of the file. This means
> >that things like \type{\dots?} cannot be used anymore (that's what
happened
> >to me :->).
> >
> >I believe this is a "recent" problem, since the previous format I was
using
> >(2000.9.21) compiled the document flawlessly.
>
> Hm. Can you check cont-new.tex and cont-sys.tex for matching \protect ..
> \unprotect?
>
cont-sys has an unmatched unprotect at the beginning (there is a \protect in
a commented block);
cont-new has 11 unprotect and 7 protects;
do these figures mean something to you?
> \starttext
>
> \def\test{test} \test?
>
> \stoptext
>
> should work. When reading module etc files, protection is handled, so
maybe
> some \unprotect lacks, When exactly does this happen?
>
In the document; something as easy as
\starttext
Hello, World! This is \TeX!
\stoptext
shows the bug. Both ! and ? are of catcode letter rather than other.
Giuseppe Bilotta
next prev parent reply other threads:[~2001-01-03 13:07 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-01-02 17:40 Hans Hagen
2001-01-03 13:07 ` Giuseppe Bilotta [this message]
2001-01-04 10:11 ` Hans Hagen
2001-01-04 17:31 ` Giuseppe Bilotta
2001-01-04 22:38 ` George N. White III
2001-01-04 23:04 ` Giuseppe Bilotta
-- strict thread matches above, loose matches on Subject: below --
2000-12-31 11:42 Giuseppe Bilotta
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='022f01c075db$1f2b6880$a3ccfea9@nuovo' \
--to=oblomov@freemail.it \
--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).