From: Hans Hagen via ntg-context <ntg-context@ntg.nl>
To: Denis Maier via ntg-context <ntg-context@ntg.nl>
Cc: Hans Hagen <j.hagen@xs4all.nl>
Subject: Re: What exactly is lpath?
Date: Wed, 3 Aug 2022 10:34:50 +0200 [thread overview]
Message-ID: <5238c57e-7e8f-ed80-f908-781ae0f6a251@xs4all.nl> (raw)
In-Reply-To: <7ab06ba1695942339167240f5af788a9@unibe.ch>
On 8/3/2022 9:46 AM, Denis Maier via ntg-context wrote:
> Hi everyone
> Just a question I've been thinking about from time to time: What exactly is lpath? Is that ConTeXt-specific? Or something more general from Lua? I've of course asked Google, but Lpath seems to a Python-inspired path library for Lua unrelated to XML...
it's a bit like xpath ... a way to access arbitrary nodes in a xml tree
with lokup and access 'patterns'
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
___________________________________________________________________________________
next prev parent reply other threads:[~2022-08-03 8:34 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-03 7:46 Denis Maier via ntg-context
2022-08-03 8:34 ` Hans Hagen via ntg-context [this message]
2022-08-03 14:39 ` Denis Maier via ntg-context
2022-08-03 15:05 ` Hans Hagen via ntg-context
2022-08-03 17:08 ` Pablo Rodriguez 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=5238c57e-7e8f-ed80-f908-781ae0f6a251@xs4all.nl \
--to=ntg-context@ntg.nl \
--cc=j.hagen@xs4all.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).