From: Hans Hagen <j.hagen@xs4all.nl>
To: denis.maier@unibe.ch,
mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: [NTG-context] Re: xmldoif: checking for contents of attribute
Date: Fri, 25 Aug 2023 14:48:10 +0200 [thread overview]
Message-ID: <6af7f29e-37bd-6eec-8a21-df9316770338@xs4all.nl> (raw)
In-Reply-To: <ZRAP278MB049538A9D25956C209893EC183E3A@ZRAP278MB0495.CHEP278.PROD.OUTLOOK.COM>
On 8/25/2023 1:45 PM, denis.maier@unibe.ch wrote:
>> -----Ursprüngliche Nachricht-----
>> Von: Hans Hagen <j.hagen@xs4all.nl>
>> Gesendet: Freitag, 25. August 2023 09:06
>> An: Maier, Denis Christian (UB) <denis.maier@unibe.ch>; mailing list for
>> ConTeXt users <ntg-context@ntg.nl>
>> Betreff: Re: [NTG-context] Re: xmldoif: checking for contents of attribute
>>
>> On 8/25/2023 8:22 AM, denis.maier@unibe.ch wrote:
>>
>>> Thanks for your help. I can use that, but why is this sort of double-checking
>> necessary here?
>>
>> because containsa in a function that has checking while find is just the lua find
>> .. so i've added a check in that one too now but no upload
>>
>
> So, that would mean that the double checking is only necessary for find, not for contains. And indeed the example below works.
> Is that correct or are there any unwanted side-effects?
correct and in the next upload i'll also catch the find
-----------------------------------------------------------------
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
___________________________________________________________________________________
prev parent reply other threads:[~2023-08-25 12:49 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-24 14:11 [NTG-context] " denis.maier
2023-08-24 14:34 ` [NTG-context] " Thomas A. Schmitz
2023-08-25 6:25 ` denis.maier
2023-08-24 14:54 ` Hans Hagen
2023-08-25 6:22 ` denis.maier
2023-08-25 7:05 ` Hans Hagen
2023-08-25 11:45 ` denis.maier
2023-08-25 12:48 ` Hans Hagen [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=6af7f29e-37bd-6eec-8a21-df9316770338@xs4all.nl \
--to=j.hagen@xs4all.nl \
--cc=denis.maier@unibe.ch \
--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).