From: Jano Kula <jano.kula@gmail.com>
To: Hans Hagen <j.hagen@xs4all.nl>
Cc: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: Setting and measuring boxes TeX/Lua
Date: Wed, 25 Nov 2020 22:28:52 +0100 [thread overview]
Message-ID: <CAPefzZ1u8GpH_r_xuNrQghhJxhKE9nRu9u99CLe41FAgXriYOA@mail.gmail.com> (raw)
In-Reply-To: <c5d37026-7daa-aa46-f336-b66f1aafafa7@xs4all.nl>
[-- Attachment #1.1: Type: text/plain, Size: 533 bytes --]
Hello Hans!
On Wed, 25 Nov 2020 at 21:25, Hans Hagen <j.hagen@xs4all.nl> wrote:
> \startluacode
> context.stepwise (function()
> context.step()
> end)
> \stopluacode
>
Thank you very much!
I was trying context.stepwise several times (and \dowithnextbox,
\nextboxht and
other things). I bet there was no example of empty context.step().
The usage was: stepping in TeX end with
context.step("\\texcommands\\with\\doubleslashes") without leaving Lua.
What is the purpose of empty context.step()? Knocking on TeX's door?
Jano
[-- Attachment #1.2: Type: text/html, Size: 1158 bytes --]
[-- Attachment #2: Type: text/plain, Size: 493 bytes --]
___________________________________________________________________________________
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
___________________________________________________________________________________
next prev parent reply other threads:[~2020-11-25 21:28 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-25 18:31 Jano Kula
2020-11-25 20:25 ` Hans Hagen
2020-11-25 21:28 ` Jano Kula [this message]
2020-11-26 8:18 ` Hans Hagen
2020-11-27 16:47 ` Jano Kula
2020-11-27 18:05 ` Hans Hagen
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=CAPefzZ1u8GpH_r_xuNrQghhJxhKE9nRu9u99CLe41FAgXriYOA@mail.gmail.com \
--to=jano.kula@gmail.com \
--cc=j.hagen@xs4all.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).