ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Hans Hagen <pragma@wxs.nl>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: LuaTeX error <main ctx instance>:1:	'<name>'	expected near '\'.
Date: Tue, 23 Feb 2010 18:13:33 +0100	[thread overview]
Message-ID: <4B840CBD.3080802@wxs.nl> (raw)
In-Reply-To: <20100218164611.GA29687@gaston.couberia.bzh>

On 18-2-2010 17:46, Peter Münster wrote:
> On Thu, Feb 18 2010, Hans Hagen wrote:
>
>> so, indeed we need a small example
>
> Hello Hans,
>
> Finally it took me less time. Here is it:
>
> \usemodule[pre-stepwise]
> \def\startC{%
>    \bgroup
>    \whitespace
>    \obeylines
>    \activatespacehandler{yes}%
>    \strut}
> \def\stopC{\egroup}
> \setupinteraction[state=start]
> \setuppapersize[S6][S6]
> \setupwhitespace[big]
> \starttext
> \startcolumns\placelist[chapter]\stopcolumns
> \startC
> bla
> bla
> bla
> bla
> bla
> bla
> bla
> bla
> bla
> bla
> bla
> bla
> bla
> bla
> bla
> \stopC
> \stoptext

the problem, is that the catcodes are changes in the main vector and 
that influences code handled in the output routine

there is no easy way around this (apart from not switching catcodes)

so, after figuring out that in this case the prooblem is in delayed 
expansion of

\definereference [CheckStepper]  [JS(CheckStepper{\StepCounter})]

i decided to add a push/popper, which works like this

\def\startC
   {\bgroup
    \pushcatcodes
    \whitespace
    \obeylines
    \activatespacehandler{yes}%
    \strut}

\def\stopC
   {\popcatcodes
    \egroup}

of course this is only needed when changes to catcodes are made that 
bleed into the page builder (happens seldom)

Hans


-----------------------------------------------------------------
                                           Hans Hagen | PRAGMA ADE
               Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
      tel: 038 477 53 69 | fax: 038 477 53 74 | www.pragma-ade.com
                                              | www.pragma-pod.nl
-----------------------------------------------------------------
___________________________________________________________________________________
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
___________________________________________________________________________________


      reply	other threads:[~2010-02-23 17:13 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-02-18 12:05 Peter Münster
2010-02-18 12:13 ` Hans Hagen
2010-02-18 16:46   ` Peter Münster
2010-02-23 17:13     ` Hans Hagen [this message]

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=4B840CBD.3080802@wxs.nl \
    --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).