From: Hans Hagen via ntg-context <ntg-context@ntg.nl>
To: Joey McCollum via ntg-context <ntg-context@ntg.nl>
Cc: Hans Hagen <j.hagen@xs4all.nl>
Subject: Re: Checking for a macro in a string without expanding it
Date: Tue, 16 Nov 2021 22:04:17 +0100 [thread overview]
Message-ID: <fce7507d-b816-1727-7a37-010bce8c3998@xs4all.nl> (raw)
In-Reply-To: <CAGxRUG9bP=SX79OF8dAZyeF2zcwd-=4O73yWxfeHOOxNrWd14A@mail.gmail.com>
On 11/16/2021 8:22 PM, Joey McCollum via ntg-context wrote:
> As the subject of this question suggests, this is really more of a
> question about expansion control (a topic that is still a bit obscure to
> me). Suppose I have a macro \inner that expects a single argument or an
> assignment of parameters in brackets. For my purposes, I don't want this
> macro to do anything when it is typeset, so I'll just define it as empty:
>
> ```
> \def\inner[#1]\empty
> ```
>
> Now suppose I have another macro \outer that invokes this macro with
> some specific input and sets some plain text after it:
>
> ```
> \def\outer{\inner[123] etc.}
> ```
>
> What I'd like to do is parse the argument of \inner in \outer. I was
> hoping that a string search in Lua would work, but I'm not having any
> luck. A minimal (non)-working example is included below:
>
> ```
>
> \def\inner[#1]\empty
>
> \def\outer{\inner[123] etc.}
>
>
> \startluacode
>
> local userdata = userdata or {}
>
> function userdata.parseinner(str)
>
> local innerparams = ""
>
> if string.find(str, "\\inner(%b[])") then
>
> i, j = string.find(str, "\\inner(%b[])")
>
> innerparams = string.sub(str, i+1, j-1) -- we just want the
> content inside the brackets
>
> end
>
> context(innerparams)
>
> return
>
> end
>
> \stopluacode
>
> \def\parseinner#1{\ctxlua{userdata.parseinner([==[#1]==])}}
>
>
> \starttext
>
> Testing:\blank
>
> \parseinner{\outer}
>
> \stoptext
>
> ```
>
> My problem is that when I pass \outer to the \parseinner macro, it gets
> fully expanded, so there isn't anything left to match "\\inner%b[]". Is
> there a way to expand \outer when I pass it to the \parseinner macro
> without also expanding the \inner macro inside it? Or is there some
> other preferred way of doing this?
One can always abuse native tex:
\starttext
\def\MyOuter#1%
{\beginlocalcontrol % hides the next
\let\Indeed\empty
\def\MyInner[##1]{\gdef\Indeed{##1}}%
\setbox\scratchbox\hpack{#1}%
\endlocalcontrol % but only if needed
\Indeed}
whatever: \MyOuter{\MyInner[oeps]}%
\edef\ItWorks{\MyOuter{\MyInner[oeps]}}
whatever: \meaningless\ItWorks
\stoptext
--
-----------------------------------------------------------------
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
___________________________________________________________________________________
prev parent reply other threads:[~2021-11-16 21:04 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-16 19:22 Joey McCollum via ntg-context
2021-11-16 20:09 ` Jairo A. del Rio via ntg-context
2021-11-16 21:18 ` Hans Hagen via ntg-context
2021-11-16 22:15 ` Joey McCollum via ntg-context
2021-11-17 8:02 ` Hans Hagen via ntg-context
2021-11-17 11:36 ` Henning Hraban Ramm via ntg-context
2021-11-17 12:37 ` Hans Hagen via ntg-context
2021-11-16 21:04 ` Hans Hagen via ntg-context [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=fce7507d-b816-1727-7a37-010bce8c3998@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).