From: Hans Hagen <j.hagen@xs4all.nl>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>,
Henri Menke <henrimenke@gmail.com>
Subject: Re: roadmap
Date: Wed, 16 May 2018 09:28:42 +0200 [thread overview]
Message-ID: <85e1cf7e-31e4-7b49-4d94-65816f18c00d@xs4all.nl> (raw)
In-Reply-To: <63d9d108-e7b2-4aab-0783-8734cd394853@gmail.com>
On 5/16/2018 7:38 AM, Henri Menke wrote:
> I just thought of another thing.
>
> Could you expose _all_ the subtypes of _all_ the different node types
> similar to node.id? (currently this is only enabled for whatsits) As of
> now I always have to go to texnodes.w, find the array and count to find
> out which number a subtype has. It would be much easier if we could
luatex 1.10 will have that (as it take s bit of effort to enter al the
data which i'm doing as part of some other cleanups)
anyway, you can do:
local n = node.new("noad") n.subtype = node.subtypes("noad").bin print(n)
local n = node.new("noad") n.subtype = node.subtypes("noad").rel print(n)
there was never a need to look into a 'w' file, also because sometimes
subtypes get added we provided this list
> node.new("noad", "bin")
>
> instead of
>
> node.new("noad", 4)
>
> and I would also like to see
>
> node.subtype("noad", "bin") -- return 4
node.subtypes("noad").bin
returns a number
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 / 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:[~2018-05-16 7:28 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-14 15:17 roadmap Hans Hagen
2018-05-14 19:36 ` roadmap Henning Hraban Ramm
2018-05-14 21:26 ` roadmap Hans Hagen
2018-05-15 9:01 ` roadmap MF
2018-05-14 22:52 ` roadmap Henri Menke
2018-05-14 23:34 ` roadmap Hans Hagen
2018-05-16 5:38 ` roadmap Henri Menke
2018-05-16 6:24 ` roadmap Joseph Canedo
2018-05-16 7:28 ` Hans Hagen [this message]
2018-05-14 23:41 ` roadmap luigi scarso
2018-05-15 19:17 ` roadmap Pablo Rodriguez
2018-05-15 21:26 ` roadmap Hans Hagen
2018-05-16 15:18 ` roadmap Pablo Rodriguez
2018-05-16 19:14 ` roadmap Fabrice L
2018-05-17 13:06 ` roadmap Hans Hagen
2018-05-17 14:24 ` roadmap Mohammad Hossein Bateni
2018-05-17 15:47 ` roadmap Otared Kavian
2018-05-17 16:50 ` roadmap Hans Hagen
2018-05-15 6:15 roadmap Christoph Reller
2018-05-15 6:23 ` roadmap luigi scarso
2018-05-15 6:36 ` roadmap Hans Hagen
2018-05-15 14:46 roadmap Christoph Reller
2018-05-15 14:51 ` roadmap luigi scarso
2018-05-18 9:54 roadmap Christoph Reller
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=85e1cf7e-31e4-7b49-4d94-65816f18c00d@xs4all.nl \
--to=j.hagen@xs4all.nl \
--cc=henrimenke@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).