ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Pablo Rodriguez <oinos@gmx.es>
To: ntg-context@ntg.nl
Subject: Re: need help comparing strings
Date: Tue, 13 Oct 2020 19:38:56 +0200	[thread overview]
Message-ID: <eac65ece-0476-de93-b1f0-e364b2463ee4@gmx.es> (raw)
In-Reply-To: <0ba2a375-9ceb-2371-8c73-141b2f7a21dd@gmail.com>

On 10/13/20 7:14 PM, Wolfgang Schuster wrote:
> Pablo Rodriguez schrieb am 13.10.2020 um 19:06:
>> [...]
>> In any case, I cannot compare to a number:
>>
>>    \startluacode
>>      userdata = userdata or {}
>>      function userdata.numbersfname(name)
>>          return string.match(name, "%d+")
>>      end
>>    \stopluacode
>>
>>    \define[1]\numbersfname
>>        {\cldcontext{userdata.numbersfname([==[#1]==])}}
>
> Untested:
>
> \defineexpandable[1]\numbersfname
>    {\cldcontext{userdata.numbersfname([==[#1]==])}}

I’m afraid it doesn’t work.

  \startluacode
    userdata = userdata or {}
    function userdata.numbersfname(name)
        return string.match(name, "%d+")
    end
  \stopluacode

  \defineexpandable[1]\numbersfname
    {\cldcontext{userdata.numbersfname([==[#1]==])}}

  \starttext
  \numbersfname{abc123}

  \numbersfname{\env{fname}}
  \doifelse{\numbersfname{\env{fname}}}{123}{yes}{no}
  \stoptext

Just curious about what the difference might be.

Many thanks for your help,

Pablo
--
http://www.ousia.tk
___________________________________________________________________________________
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
___________________________________________________________________________________

  reply	other threads:[~2020-10-13 17:38 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-10-13 15:33 Pablo Rodriguez
2020-10-13 15:54 ` Aditya Mahajan
2020-10-13 17:06   ` Pablo Rodriguez
2020-10-13 17:14     ` Wolfgang Schuster
2020-10-13 17:38       ` Pablo Rodriguez [this message]
2020-10-13 16:14 ` Wolfgang Schuster
2020-10-13 17:09   ` Pablo Rodriguez
2020-10-13 17:16 ` Pablo Rodriguez

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=eac65ece-0476-de93-b1f0-e364b2463ee4@gmx.es \
    --to=oinos@gmx.es \
    --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).