From: moritz braun <moritz.braun@gmail.com>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: Strange Behaviour / Strange Memory effect when creating pdf charts with the chart module in context
Date: Thu, 21 Jan 2010 09:40:24 +0200 [thread overview]
Message-ID: <db8e958c1001202340u1dd4036at797c86cd4e8f88f7@mail.gmail.com> (raw)
In-Reply-To: <4B57FE96.2010505@elvenkind.com>
Hi there
this is not really my experience
Even when deleting all the many files that context creates, There is a
strange memory effect!!!
On Thu, Jan 21, 2010 at 9:13 AM, Taco Hoekwater <taco@elvenkind.com> wrote:
> moritz braun wrote:
>>
>> Dear All
>>
>> I am experiencing a strange problem with the chart module using
>> context on ubuntu.
>> this module allows for the creating of nice flow charts!
>> however
>> when creating the flow chart from the source code with
>> texexec --pdf chart.tex
>> the resultiong pdf file sometimes shows information that is not in the tex
>> file
>> but was in a previous version of it, i.e. some kind of a wierd memoery
>> effect is present
>> I am wondering, where does context keep its cache.
>> In order to debug this problem I installed context on another ubuntu box
>> and
>> when freshly installed , i.e. for the first call of texexec the result
>> was fine. however
>> any subsequent call will again create unpredictable effects.
>> I have written some documentation using context and the chart module
>> and today is may last day in the project and I need to hand this over!
>
> Yes, this sometimes happens. Context stores is transitional data
> in \jobname.tuo for 'texexec' (\jobname.tuc for 'context') and
> if you use the chart module, I know for a fact that at least the .tuo
> tends to lag behind a bit.
>
> The solution is to run 'texexec' (or 'context', but I suspect the
> problem is with 'texexec' ) once more without doing any edits.
>
> Best wishes,
> Taco
> ___________________________________________________________________________________
> 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
> ___________________________________________________________________________________
>
--
Prof M Braun Tel.:27-12-4298006/8027
Physics Department Fax.: 27-12-4293643
University of South Africa (UNISA)
moritz.braun@gmail.com
P.O. Box 392
0003
UNISA
South Africa
___________________________________________________________________________________
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
___________________________________________________________________________________
next prev parent reply other threads:[~2010-01-21 7:40 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-20 8:53 moritz braun
2010-01-21 7:13 ` Taco Hoekwater
2010-01-21 7:40 ` moritz braun [this message]
2010-01-21 8:19 ` luigi scarso
2010-01-21 16:34 ` Aditya Mahajan
2010-01-22 4:48 ` moritz braun
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=db8e958c1001202340u1dd4036at797c86cd4e8f88f7@mail.gmail.com \
--to=moritz.braun@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).