ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Pablo Rodriguez <oinos@gmx.es>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: \doifelse not working, \doiftextelse breaking
Date: Fri, 9 Oct 2020 15:58:31 +0200	[thread overview]
Message-ID: <ce5d3ac5-cf88-5f2c-c1e0-41aa4b65dd65@gmx.es> (raw)

Dear list,

I have the following sample:

    \starttext
    \startluacode
    function document.starts_with(str, start)
      if str:sub(1, #start) == start then
        context(start)
      end
    end
    \stopluacode

    \unexpanded\def\startswith[#1][#2]
        {\cldcontext{document.starts_with("#1", "#2")}}

    \startswith[getjobid764572121][getjobid]

    yes:
    \doifelse{\startswith[getjobid764572121][getjobid]}{getjobid}
        {yes}{no}

    no:
    \doifelse{\startswith[getjobid764572121][getjobid]}{}
        {yes}{no}

    %% \doiftextelse{\startswith[getjobid764572121][getjobid]}
        % {yes}{no}
    \stoptext

I don’t know why comparing doesn’t work with \doifelse.

I’m surprised that \doiftextelse breaks when \startswidth if inside.

How could i make \startswith work inside \doiftext?

Or how could I catch positives when command contents start with a given
string?

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-09 13:58 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-10-09 13:58 Pablo Rodriguez [this message]
2020-10-09 14:08 ` Wolfgang Schuster
2020-10-09 14:31   ` Pablo Rodriguez
2020-10-09 15:10     ` Wolfgang Schuster
2020-10-09 19:24       ` 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=ce5d3ac5-cf88-5f2c-c1e0-41aa4b65dd65@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).