ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Jaroslav Hajtmar <hajtmar@gyza.cz>
To: Hans Hagen <pragma@wxs.nl>,
	mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: Problem with last version of ConTeXt
Date: Sun, 19 Oct 2014 23:45:38 +0200	[thread overview]
Message-ID: <54443102.1000506@gyza.cz> (raw)
In-Reply-To: <54437B04.5070905@wxs.nl>

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.

Thanks very much for your help and assistance. I'm not sure if this 
irregularities those revelations this somehow help you. It is at least 
strange that ConTeXt version of TeXLive 2014 the code untroubled eat 
...: -) ...

Thanks again and have a lot of energy ...

Jaroslav Hajtmar


PS: Just to explain the code of \VART macro (probably irrelevant to You):

\def\random#1#2{
\startluacode
local cislo=math.random(10)
if cislo > 3 then
         context('\\getvariable{#1}{#2}')
     else
         context('\\fakenwords{1}{'..math.random(10,15)..'}')
end
\stopluacode
}


\def\VART#1#2{%
         \doifmodeelse{koncept}%
             {
                 \doifmodeelse{security}%
                 {\random{#1}{#2}}
                 {%
                 \expdoifelse{\getvariable{#1}{#2}}{}{{\ERRORSCOLOR 
#1.#2 ERROR}}{{\VARSCOLOR\getvariable{#1}{#2}}}%\removeunwantedspaces}
                 }%
             }
             {%
             \expdoifelse{\getvariable{#1}{#2}}{}{{\ERRORSCOLOR #1.#2 
ERROR}}{{\VARSCOLOR\getvariable{#1}{#2}}}%\removeunwantedspaces
           }%
}%







Dne 19.10.2014 10:49, Hans Hagen napsal(a):
> On 10/18/2014 9:20 PM, Jaroslav Hajtmar wrote:
>> Thanx Hans for reply.
>> A few hours I was looking for a problem in my source file and library
>> that load at the beginning of my file. It seems that the problem has
>> nothing to do with the error message means that it has not nothing to
>> do with the itemize environment nor setupitemize (nothing like this in
>> the file does not resp. when sections of code to comment out these
>> environments, so nothing changes). The problem probably is related to
>> some a side effect, because in older versions of ConTeXt Standalone not
>> appear (and does not appear in Context, which is included in the latest
>> distribution TeXLive 2014).
>>
>> In my library are very old pieces of code that I used many years ago in
>> plainTEX in combination with ConTeXtovým code (including frequent use
>> \setvariables). Unfortunately I was despite my great efforts failed to
>> create a "reasonable" minimal example, so I'll probably have to wait
>> some time until someone else runs into a similar problem and will be
>> able to describe properly document and create a minimum sample example
>> (already with me it happened several times and each time it finally was
>> resolved).
>
> just put a \tracingall someplace ... (bottom up) then you can see 
> where it stops
>
> -----------------------------------------------------------------
>                                           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-19 21:45 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 [this message]
2014-10-20  7:16         ` Hans Hagen
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=54443102.1000506@gyza.cz \
    --to=hajtmar@gyza.cz \
    --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).