ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Wolfgang Schuster <schuster.wolfgang@googlemail.com>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: Strange error message
Date: Sun, 11 Mar 2012 09:55:17 +0100	[thread overview]
Message-ID: <EE65F441-3E72-417D-BE0B-040478E23817@googlemail.com> (raw)
In-Reply-To: <C86126A3-D6CE-457C-8CD2-8A6D333F42A2@gmail.com>


Am 10.03.2012 um 22:10 schrieb Otared Kavian:

> Hi all,
> 
> Has anyone encountered the following situation with the betas from last January until today?
> I have a document some 100 pages (each page being an \input), which is correctly typeset with ConTeXt version 2011.11.29 mkiv, but gives me the following error with the recent mkiv betas: the message is
> 
> <to be read again> 
>                   }
> <inserted text> ...onstructionparameter \c!level }
>                                                  \setevalue {\??constructio...
> \define_construction ... \everydefineconstruction 
>                                                  \let \currentconstruction ...
> <inserted text> ...r =\v!description ,\c!level =1]
>                                                  \else \defineconstruction ...
> \define_description ...he \everydefinedescription 
>                                                  \let \currentdescription \...
> <to be read again> 
>                   \startpacked 
> …
> 
> In order to localize the error I have tried to add little by little my \input files, and everything works when I have about 20 pages… 
> I am reporting this issue just for debugging reasons, since for the real project I still use the 2011.11.29 version.
> Indeed I should apologize since I am not able to submit a minimal example, my project itself being somewhat complex (at least from my perspective… not for a guru!).
> 
> Also, I should say that in recent previous betas the error message was different, but I have not anymore those versions to report what the exact message was.

Thats’t to less information to tell what’s the problem but I can say it is generated from \definedescription.

Do you use \definedescription somewhere in your document in combination with \startpacked, e.g. \definedescription[before=\startpacked] or \defindescription[packed] etc.

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  : http://foundry.supelec.fr/projects/contextrev/
wiki     : http://contextgarden.net
___________________________________________________________________________________


  reply	other threads:[~2012-03-11  8:55 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-03-10 21:10 Otared Kavian
2012-03-11  8:55 ` Wolfgang Schuster [this message]
2012-03-11 13:30   ` Otared Kavian
  -- strict thread matches above, loose matches on Subject: below --
2000-10-17 18:36 Willi Egger

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=EE65F441-3E72-417D-BE0B-040478E23817@googlemail.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).