ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Otared Kavian <otared@gmail.com>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: Bug in symb-ini.mkiv?
Date: Sun, 15 Jan 2012 17:07:42 +0100	[thread overview]
Message-ID: <65F06243-12E1-40DF-A16E-5EF444F71046@gmail.com> (raw)
In-Reply-To: <769B3812-D542-4118-9CE4-37998C81F874@googlemail.com>

Hi Wolfgang,

Thanks for your response: right now I am not with my computer at home (writing you from another place). I'll do what you suggest this evening.

Best regards: OK

On 15 janv. 2012, at 16:48, Wolfgang Schuster wrote:

> 
> Am 15.01.2012 um 16:39 schrieb Otared Kavian:
> 
>> Hi Hans,
>> 
>> With the latest beta (ConTeXt  ver: 2012.01.12 11:03 MKIV), typesetting a document which used to be typeset without problems I encounter an error which points to some commands defined in symb-ini.mkiv. However I can switch back to ConTeXt  ver: 2011.11.29 18:47 MKIV in order to teypeset my document.
>> Since the document is long and the macros I use are soemwhat complex (and maybe not very well written…), I cannot send you a minimal example which shows the problem. In any case, I wanted to let you know about the issue. The error message says:
>> 
>> <inserted text> 
>>               }
>> <to be read again> 
>>                  \endgroup 
>> \symb_place_retry ...name \symb_place_indeed {:#1}
>>                                                 \else #1\fi 
>> \symb_place_normal_c ...lace_retry \currentsymbol 
>>                                                 \fi 
>> \symb_place_normal_b ...else \symb_place_normal_c 
>>                                                 \fi 
>> <to be read again> 
>>                  \else 
>> and stops when an \item is encountered.
> 
> Send at least your log file and add “\tracingmacros1” before and “tracingmacros0” after the part where context fails (look at the line number from the error message).
> 
> 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
> ___________________________________________________________________________________

___________________________________________________________________________________
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-01-15 16:07 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-01-15 15:39 Otared Kavian
2012-01-15 15:48 ` Wolfgang Schuster
2012-01-15 16:07   ` Otared Kavian [this message]
2012-01-15 20:11   ` Otared Kavian
2012-01-16  9:14     ` Hans Hagen

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=65F06243-12E1-40DF-A16E-5EF444F71046@gmail.com \
    --to=otared@gmail.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).