ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: "George N. White III" <whiteg@dfo-mpo.gc.ca>
Cc: Hans Hagen <pragma@wxs.nl>, ConTeXt <ntg-context@ntg.nl>
Subject: Re: Wrong catcode?
Date: Thu, 4 Jan 2001 18:38:53 -0400	[thread overview]
Message-ID: <Pine.SGI.4.31.0101041836570.36994-100000@wendigo.bio.dfo.ca> (raw)
In-Reply-To: <000101c0769c$8be091a0$a3ccfea9@nuovo>

On Thu, 4 Jan 2001, Giuseppe Bilotta wrote:

> Hans Hagen wrote:
> > At 02:07 PM 1/3/01 +0100, Giuseppe Bilotta wrote:
> >
> > >cont-sys has an unmatched unprotect at the beginning (there is a \protect
> in
> > >a commented block);
> >
> > Every \unprotect should be matched by a \protect, unless in a macro def,
> so
> > you can probably uncomment the \protect.
>
> Adding a \protect at the beginning of my document solves the problem. So I
> guess that the problem is the "naked" \unprotect in cont-sys.
>
> I will change cont-sys and regenerate the formats, I will inform you of the
> result as soon as I do it.
>
> Giuseppe Bilotta

You shouldn't need to regenerate formats.  If you check a .log file
you will see that cont-sys is read each time context is run.  I have
already made the change on my system at work, and am about to do so
on my home system.

-- 
George N. White III <WhiteG@dfo-mpo.gc.ca>  tel: 902.426.8509
  Bedford Institute of Oceanography, Nova Scotia, Canada (TZ=AST4ADT)


  reply	other threads:[~2001-01-04 22:38 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
2001-01-04 10:11   ` Hans Hagen
2001-01-04 17:31     ` Giuseppe Bilotta
2001-01-04 22:38       ` George N. White III [this message]
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=Pine.SGI.4.31.0101041836570.36994-100000@wendigo.bio.dfo.ca \
    --to=whiteg@dfo-mpo.gc.ca \
    --cc=ntg-context@ntg.nl \
    --cc=pragma@wxs.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).