From: Rik Kabel via ntg-context <ntg-context@ntg.nl>
To: ntg-context@ntg.nl
Cc: Rik Kabel <ConTeXt@rik.users.panix.com>
Subject: Re: can typesetbuffer use the same engine?
Date: Fri, 5 Nov 2021 11:57:42 -0400 [thread overview]
Message-ID: <31c2cd74-fb89-e6e4-faf7-a6c601069b41@rik.users.panix.com> (raw)
In-Reply-To: <9e0f60f8-8d48-fa29-ef60-a512e0b1d069@xs4all.nl>
On 11/5/2021 11:18, Hans Hagen via ntg-context wrote:
> On 11/5/2021 3:19 PM, Rik Kabel via ntg-context wrote:
>> Hello brain trust,
>>
>> How can \typesetbuffer be instructed to use the same engine as the
>> document which contains it?
>>
>> With the following example:
>>
>>
>> \startbuffer[Buffer]
>> \startTEXpage \contextmark \stopTEXpage
>> \stopbuffer
>> \starttext
>> \contextmark\
>> \typesetbuffer[Buffer]
>> \stoptext
>>
>> I get "MKIV LMTX" when it is processed with context --luatex. I want
>> the buffer to be processed as MkIV.
> Does patching line 691 in buff-ini.lua
>
> template = (jit and "--jit --engine=luajittex" or
> "--engine=luatex") .. " --purgeall %?path: --path=%path% ?% %filename%",
>
> work okay? Run "context --make" after patching.
>
> Hans
>
Yes, that seems to do it. context --make and context --make --luatex
were needed, I think.
--
Rik
___________________________________________________________________________________
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:[~2021-11-05 15:57 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-05 14:19 Rik Kabel via ntg-context
2021-11-05 15:18 ` Hans Hagen via ntg-context
2021-11-05 15:57 ` Rik Kabel via ntg-context [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=31c2cd74-fb89-e6e4-faf7-a6c601069b41@rik.users.panix.com \
--to=ntg-context@ntg.nl \
--cc=ConTeXt@rik.users.panix.com \
/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).