ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Hans Hagen <pragma@wxs.nl>
To: hajtmar@gyza.cz, mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: Problem with last version of ConTeXt
Date: Mon, 20 Oct 2014 09:16:16 +0200	[thread overview]
Message-ID: <5444B6C0.3030009@wxs.nl> (raw)
In-Reply-To: <54443102.1000506@gyza.cz>

On 10/19/2014 11:45 PM, Jaroslav Hajtmar wrote:
> Hello....
> Thanx Hans for the advice - too me it could attack itself :-).
>
> When I use \tracingall, then I managed to figure out what the problem was.
> In fact, there was an error retrieving data from an external file (the
> library), and it while trying to load ConTeXt buffer command.
>
> The original content of this buffer was:
>
> \startbuffer[hlavička_kú]%
> {\bf Katastrálnímu úřadu pro \VART{SMLOUVA}{KU_kraj} kraj\br%
> \expdoifelse{\getvariable{SMLOUVA}{KU_sidlo}}{\empty}{}{se sídlem
> \VART{SMLOUVA}{KU_sidlo}\br}%
> Katastrálnímu pracovišti \VART{SMLOUVA}{KU_pracoviste}}%
> \stopbuffer%
>
> This content has caused the error in the latest version of ConTeXt
> standalone (but in past versions of ConTeXt or standalone version of
> TeXLive 2014, I did not noticed this error message).
>
>
> When I made ​​the following changes:
>
> \startbuffer[hlavička_kú]%
> \bgroup%
> \bf Katastrálnímu úřadu pro \VART{SMLOUVA}{KU_kraj} kraj\br%
> \expdoifelse{\getvariable{SMLOUVA}{KU_sidlo}}{\empty}{}{se sídlem
> \VART{SMLOUVA}{KU_sidlo}\br}%
> Katastrálnímu pracovišti \VART{SMLOUVA}{KU_pracoviste}%
> \egroup%
> \stopbuffer%
>
>
> then everything goes smoothly and everything is OK.

maybe some lookahead issue: you load a buffer and the preceding command 
sees the { which confuses it. Sometimes it hels to define macros as 
unexpanded:

\unexpanded\def\random#

\unexpanded\def\VART#1#2{%

-----------------------------------------------------------------
                                           Hans Hagen | PRAGMA ADE
               Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
     tel: 038 477 53 69 | voip: 087 875 68 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:[~2014-10-20  7:16 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-10-18  7:14 Jaroslav Hajtmar
2014-10-18  9:40 ` Hans Hagen
2014-10-18 19:20   ` Jaroslav Hajtmar
2014-10-19  8:49     ` Hans Hagen
2014-10-19 21:45       ` Jaroslav Hajtmar
2014-10-20  7:16         ` Hans Hagen [this message]
2014-10-20  8:27           ` Jaroslav Hajtmar

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=5444B6C0.3030009@wxs.nl \
    --to=pragma@wxs.nl \
    --cc=hajtmar@gyza.cz \
    --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).