ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Hans Hagen via ntg-context <ntg-context@ntg.nl>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Cc: Hans Hagen <j.hagen@freedom.nl>, Max Chernoff <mseven@telus.net>
Subject: Re: Accessing inserts from Lua in LuaMetaTeX
Date: Mon, 15 Aug 2022 16:24:20 +0200	[thread overview]
Message-ID: <4624e963-8c5d-5ea3-e7f9-afebd55a30d7@freedom.nl> (raw)
In-Reply-To: <7f95f02c30da08b771b063440945115b93435d71.camel@telus.net>

On 8/15/2022 8:18 AM, Max Chernoff via ntg-context wrote:
> Hi all,
> 
> I'm trying to manipulate some inserts from Lua in LuaMetaTeX, and I'm
> having some problems that I'm not having with LuaTeX.
> 
> First, how do I get an insert's class/type from the "insert" nodes on
> the page? With LuaTeX, the insert's class/type is the same as the
> subtype of the "ins" nodes, but the subtype of the "insert" nodes is
> always zero in LuaMetaTeX, so I'm not sure how to get the class/type.

Indeed, we don't use these boxes and registers because we run in 
\insertmode=2. This gives us more state info (i kept the old method 
around for now).

> Second, how do I get the head of the insert box from Lua? With LuaTeX,
> from TeX you would use "\box<class>" and from Lua you can use
> "tex.box[<class>]". With LuaMetaTeX, you use "\insertbox<class>" from
> TeX, but I'm not sure how to get at the insert box from Lua.

tex.getinsertdistance
tex.getinsertmultiplier
tex.getinsertlimit
tex.getinsertheight
tex.getinsertdepth
tex.getinsertwidth
tex.getinsertcontent
tex.setinsertdistance
tex.setinsertmultiplier
tex.setinsertlimit
tex.setinsertcontent

> The context for both of these is that my module lua-widow-control
> sometimes moves a line containing footnotes to the next page, so I need
> to do some surgery to make sure that the "footnote marks" stay with the
> "footnote text". This is tricky but doable with LuaTeX, but I can't seem
> to get it to work with the new inserts in LuaMetaTeX, hence the above
> questions.
The insert (etc) handler is more clever and flexible. So, for instance 
we can bubble up inserts. I think you do a preroll so in that case you 
can set the migrations related parameter to not bubble up.

\starttext

\holdingmigrations\numexpr1+2+4\relax

\setbox0\hbox{test \footnote{test} test}

\setbox2\vbox{\unhcopy0}

\holdingmigrations0

\setbox4\vbox{\unhcopy0}

\unhbox0

\unvbox2

\unvbox4

\stoptext

But I have no clue how all that will work out with (lua) code that 
manipulates these things. In list nodes you can consult the pre and post 
fields to what got migrated.

Hans

-----------------------------------------------------------------
                                           Hans Hagen | PRAGMA ADE
               Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
        tel: 038 477 53 69 | www.pragma-ade.nl | 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 / https://www.ntg.nl/mailman/listinfo/ntg-context
webpage  : https://www.pragma-ade.nl / http://context.aanhet.net
archive  : https://bitbucket.org/phg/context-mirror/commits/
wiki     : https://contextgarden.net
___________________________________________________________________________________

  reply	other threads:[~2022-08-15 14:24 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-15  6:18 Max Chernoff via ntg-context
2022-08-15 14:24 ` Hans Hagen via ntg-context [this message]
2022-08-16  1:56 Max Chernoff via ntg-context

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=4624e963-8c5d-5ea3-e7f9-afebd55a30d7@freedom.nl \
    --to=ntg-context@ntg.nl \
    --cc=j.hagen@freedom.nl \
    --cc=mseven@telus.net \
    /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).