From: Hans Hagen <pragma@wxs.nl>
To: ntg-context@ntg.nl
Subject: Re: Overwriting buffer causes LuaTeX error
Date: Fri, 20 Sep 2013 00:35:52 +0200 [thread overview]
Message-ID: <523B7C48.4060006@wxs.nl> (raw)
In-Reply-To: <20130919213836.GA6757@homerow>
On 9/19/2013 11:38 PM, Marco Patzer wrote:
> Hi,
>
> the following example causes
>
> 1) strange message: “invalid \starttext ... \stoptext structure” and
>
> 2) !LuaTeX error: PDF inclusion: file has changed 'Hga-typeset-buffer-001.pdf'
> ==> Fatal error occurred, no output PDF file produced!
>
> \starttext
> \startbuffer [foo]
> foo
> \stopbuffer
> \typesetbuffer [foo]
>
> \startbuffer [foo]
> foo
> \stopbuffer
> \typesetbuffer [foo]
> \stoptext
i uploaded a fix (some additional checking on redefining such buffers)
.. the backend keeps the file open (which is where the message comes from)
\starttext
\startbuffer [foo]
\startTEXpage
\input tufte
\stopTEXpage
\stopbuffer
\dorecurse{20} {
\typesetbuffer [foo] [width=\textwidth] \blank
}
\startbuffer [foo]
\startTEXpage
\input ward
\stopTEXpage
\stopbuffer
\dorecurse{20} {
\typesetbuffer [foo] [width=\textwidth] \blank
}
\stoptext
-----------------------------------------------------------------
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
___________________________________________________________________________________
prev parent reply other threads:[~2013-09-19 22:35 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-19 21:38 Marco Patzer
2013-09-19 22:35 ` Hans Hagen [this message]
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=523B7C48.4060006@wxs.nl \
--to=pragma@wxs.nl \
--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).