From: Henning Hraban Ramm <texml@fiee.net>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: caching buffers?
Date: Fri, 12 Apr 2019 23:35:32 +0200 [thread overview]
Message-ID: <8F4A7B13-DE67-4642-BA3B-6F7957A287C5@fiee.net> (raw)
In-Reply-To: <c9d84b6f-42cd-2637-bdd5-8fe2d5ada459@xs4all.nl>
Am 2019-04-12 um 23:13 schrieb Hans Hagen <j.hagen@xs4all.nl>:
> On 4/12/2019 11:00 PM, Henning Hraban Ramm wrote:
>> Ahoi,
>> in my book I use a lot of buffers for examples. These get typeset (compiled) anew on every tex run (i.e. several times per context run). This needs a lot of time and is quite annoying. Is this somehow cacheable, so that it compiles only once per context run or (even better) only if the buffer changed?
>> How does the filter module handle this? I know it uses some checksum.
>> Should I "outsource" my buffers via t-filter?
>> If you need a MWE for this, I’ll assemble one. My actual setup is quite complicated, maybe that’s the problem...
> \starttext
>
> \startbuffer[old-feature]
> % load the relevant environment if needed
> It works!
> \stopbuffer
>
> \typesetbuffer[old-feature][frame=on,width=4cm]
>
> \stoptext
>
> Only when buffers change they will be retypeset.
I used the same buffer name all the time.
Sorry for the noise.
Greetlings, Hraban
---
https://www.fiee.net
http://wiki.contextgarden.net
https://www.dreiviertelhaus.de
GPG Key ID 1C9B22FD
___________________________________________________________________________________
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://context.aanhet.net
archive : https://bitbucket.org/phg/context-mirror/commits/
wiki : http://contextgarden.net
___________________________________________________________________________________
prev parent reply other threads:[~2019-04-12 21:35 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-12 21:00 Henning Hraban Ramm
2019-04-12 21:13 ` Hans Hagen
2019-04-12 21:35 ` Henning Hraban Ramm [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=8F4A7B13-DE67-4642-BA3B-6F7957A287C5@fiee.net \
--to=texml@fiee.net \
--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).