From: Sylvain Hubert <champignoom@gmail.com>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: context.delayed as parameter of setuphead[before=...]
Date: Wed, 4 Nov 2020 16:53:54 +0100 [thread overview]
Message-ID: <CACNy3NAifW2A0b2wmcVyMyr37fKREfFicikayHJm51fpQdzNbA@mail.gmail.com> (raw)
In-Reply-To: <ce41debc-fac2-de23-63da-15961f07e2a0@xs4all.nl>
[-- Attachment #1.1: Type: text/plain, Size: 1517 bytes --]
% Hans, sorry for having replied on the wrong channel before.
On Tue, 3 Nov 2020 at 09:03, Hans Hagen <j.hagen@xs4all.nl> wrote:
> On 11/3/2020 4:05 AM, Sylvain Hubert wrote:
> > > as tables like those in setuphead({somehead}, {somesettings}) are
> > actual Lua tables and follow Lua, not TeX, rules
> > But there are lua apis that support delayed TeX like
> > `context.chapter(context.delayed'text')`.
> > Whether or not the function is stored in a table should be theoretically
> > irrelevant.
> > I guess there should be a switch somewhere that let the command
> > recognized delayed function.
> all is possible but not all is reasonable to support .. adding layer
> upon layed doesn't make it more pretty
>
Indeed, but still it would be nice to have a complete and consistent
interface between tex and lua unless it would harm the functionality.
>
> anyway, chapter (section) titles go tinto a toc table and storing lua
> delayed function definitions there makes not much sense
>
> It might be helpful in cases like alternative coloring. Writing
"function() local x=1; return function() x=1-x; return ({'black',
'gray'})[x] end end"
can be way much easier for lua speakers than digging up a bunch of
documentations to figure out whether it's implemented, or how it can be
implemented in a language like TeX, or both which is worse. In such cases,
it would also be much natural to write 'before=function()..' than
'before=\ctxlua{function()...}` unless, again, the former harms the
functionality.
Sylvain
[-- Attachment #1.2: Type: text/html, Size: 2380 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-04 15:53 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-03 2:09 Sylvain Hubert
2020-11-03 2:28 ` Jairo A. del Rio
2020-11-03 3:05 ` Sylvain Hubert
2020-11-03 4:03 ` Jairo A. del Rio
2020-11-03 8:03 ` Hans Hagen
2020-11-04 15:53 ` Sylvain Hubert [this message]
2020-11-04 16:35 ` Hans Hagen
2020-11-04 17:17 ` Sylvain Hubert
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=CACNy3NAifW2A0b2wmcVyMyr37fKREfFicikayHJm51fpQdzNbA@mail.gmail.com \
--to=champignoom@gmail.com \
--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).