From: Hans Hagen via ntg-context <ntg-context@ntg.nl>
To: Joey McCollum <jmccollum20140511@gmail.com>,
mailing list for ConTeXt users <ntg-context@ntg.nl>
Cc: Hans Hagen <j.hagen@xs4all.nl>
Subject: Re: Checking for a Unicode prefix of a Unicode string
Date: Sat, 27 Nov 2021 19:44:43 +0100 [thread overview]
Message-ID: <29046f7f-f861-f1d4-ba22-331a2301e2b6@xs4all.nl> (raw)
In-Reply-To: <CAGxRUG89_N-ODreF_No=wioW5ZcFmn1EnS9qJ3d2urxqZP5B7g@mail.gmail.com>
On 11/27/2021 6:13 PM, Joey McCollum wrote:
> All right, I think I've solved the expansion problem I described before:
> to ensure that the first input is expanded when it is passed to Lua, I
> have to pass it as [==[#1]==], not "#1". But the updated MWE below still
> does not seem to work, as the \DoIfPrefixElse macro is printing "NOP"
> instead of "YES":
>
> ```
>
> \starttexdefinition loc [#1]
>
> \doifassignmentelse{#1} {
>
> % if an assignment, then parse and format accordingly
>
> \getparameters[loc][#1]
>
> % Was a section number specified?
>
> \doifdefined{locsec} {
>
> § \locsec
>
> }
>
> } {
>
> % otherwise, just print the input as-is
>
> #1
>
> }
>
> \stoptexdefinition
>
>
> \def\DoIfPrefixElse#1#2{\ctxlua{commands.doifelse(string.find([==[#2]==],"^"..[==[#1]==]))}}
>
>
> \def\currentbtxloctext{\loc[sec=31]}
>
>
> \starttext
>
> \currentbtxloctext\blank
>
> \DoIfPrefixElse{§}{\currentbtxloctext}{YES}{NOP}
>
> \stoptext
>
> ```
>
> Indeed, if I add a simple \doifelse equality check, it looks like the
> value I expect is not the same as what the macro produces, even though
> they look identical:
>
> ```
>
> \starttexdefinition loc [#1]
> \doifassignmentelse{#1} {
> % if an assignment, then parse and format accordingly
> \getparameters[loc][#1]
> % Was a section number specified?
> \doifdefined{locsec} {
> § \locsec
> }
> } {
> % otherwise, just print the input as-is
> #1
> }
> \stoptexdefinition
>
> \def\DoIfPrefixElse#1#2{\ctxlua{commands.doifelse(string.find([==[#2]==],"^"..[==[#1]==]))}}
>
> \def\currentbtxloctext{\loc[sec=31]}
>
> \starttext
> § 31\blank%the raw text we expect
> \currentbtxloctext\blank%the text as produced by the macro
> \doifelse{\currentbtxloctext}{§ 31}{YES}{NOP}\blank% should output
> YES, but doesn't
> \DoIfPrefixElse{§}{\currentbtxloctext}{YES}{NOP}\blank% should
> output YES, but doesn't
> \stoptext
>
> ```
>
> What am I missing here?
Expansion hell ... and i fear that you draw yourself into more and more
trouble with this approach (which is why you don't find that kind of
hackery in the core unless we're real desperate) so maybe try to explain
what the real problem is that needs to be solved. Parsing tex is seldom
a solution (at least not in context).
You can add:
\edef\Whatever{\currentbtxloctext}\meaning\Whatever
\doifelse{\currentbtxloctext}{§ 31}{YES}{NOP}\blank
and see what comes back. Now, as always in tex, there's of course a
solution because after all it's a programming language too (and at some
point these solutions start looking so complex that one enters guru state)
\starttexdefinition loc [#1]
\beginlocalcontrol
\doifassignmentelse{#1} {
\getparameters[loc][#1]
\doifdefinedelse{locsec} {
\endlocalcontrol
§ \locsec
} {
\endlocalcontrol
}
} {
\endlocalcontrol
#1
}
\stoptexdefinition
a curious mix between a fully expanded result, using protected macros
and hiding what tex does but hard to explain
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:[~2021-11-27 18:44 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-26 6:42 Joey McCollum via ntg-context
2021-11-26 8:45 ` Hans Hagen via ntg-context
2021-11-26 16:57 ` Joey McCollum via ntg-context
2021-11-27 17:13 ` Joey McCollum via ntg-context
2021-11-27 18:44 ` Hans Hagen via ntg-context [this message]
2021-11-28 1:39 ` Joey McCollum via ntg-context
2021-11-28 10:39 ` Hans Hagen via ntg-context
2021-11-29 17:11 ` Joey McCollum via ntg-context
2021-11-29 20:13 ` Joey McCollum 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=29046f7f-f861-f1d4-ba22-331a2301e2b6@xs4all.nl \
--to=ntg-context@ntg.nl \
--cc=j.hagen@xs4all.nl \
--cc=jmccollum20140511@gmail.com \
/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).