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 18:17:06 +0100 [thread overview]
Message-ID: <CACNy3NDB5hMDWED0AZWXWhiyzju7ZuMmEJJZk1p0OR0S4sYRPQ@mail.gmail.com> (raw)
In-Reply-To: <78fa20a9-8332-29cb-0269-510116964a6c@xs4all.nl>
[-- Attachment #1.1: Type: text/plain, Size: 1188 bytes --]
again, sorry for replying on the wrong channel.
On Wed, 4 Nov 2020 at 17:35, Hans Hagen <j.hagen@xs4all.nl> wrote:
>
> it would harm performance because it involves parsing all values and
> also ways around cases where the title is "function" (lieral text).
>
I'm not sure I understand what you mean by literal text "function" here,
but in any case isn't it a one-off <1ms cost to parse a function?
> "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.
> Really? I have no clue what that function makec clearer than tex. And
> one still needs some documentation that explains what it does.
>
> Often there often is a pretty clean way to do it with less code.
>
For an experienced tex speaker, indeed.
But for an average user who just wants to typeset a bit of fancy stuff,
programming in tex is probably not the most pleasant thing to do and
arguably not the most reasonable either in light of any modern language
like lua.
Sylvain
[-- Attachment #1.2: Type: text/html, Size: 1889 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
___________________________________________________________________________________
prev parent reply other threads:[~2020-11-04 17:17 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
2020-11-04 16:35 ` Hans Hagen
2020-11-04 17:17 ` Sylvain Hubert [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=CACNy3NDB5hMDWED0AZWXWhiyzju7ZuMmEJJZk1p0OR0S4sYRPQ@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).