From: Wolfgang Schuster <schuster.wolfgang@gmail.com>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: doifnextcharelse
Date: Sun, 24 Jan 2016 19:21:45 +0100 [thread overview]
Message-ID: <56A51639.1070203@gmail.com> (raw)
In-Reply-To: <7BBE743F-DD78-44AF-B4FA-8D71A833C918@uva.nl>
[-- Attachment #1.1: Type: text/plain, Size: 757 bytes --]
> Meer, Hans van der <mailto:H.vanderMeer@uva.nl>
> 24. Januar 2016 um 15:58
> Yes this works. But alas, the ultimate goal is to test against several
> characters and that seems impossible to do with standard ConTeXt
> api-macros.Let alone when these characters are . or . or ) etc.
\startluacode
function checknextstring(str)
if str == "a" then
context("A")
elseif str == "b" then
context("B")
else
context("??")
end
end
interfaces.implement { name = "readnextstring", actions =
checknextstring, arguments = "string" }
\stopluacode
\unprotect
\let\readnextstring\clf_readnextstring
\protect
\starttext
\readnextstring c
\readnextstring b
\readnextstring a
\readnextstring {xx}
\stoptext
Wolfgang
[-- Attachment #1.2: Type: text/html, Size: 1915 bytes --]
[-- Attachment #2: Type: text/plain, Size: 485 bytes --]
___________________________________________________________________________________
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://tex.aanhet.net
archive : http://foundry.supelec.fr/projects/contextrev/
wiki : http://contextgarden.net
___________________________________________________________________________________
prev parent reply other threads:[~2016-01-24 18:21 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-24 13:30 doifnextcharelse dr. Hans van der Meer
2016-01-24 14:13 ` doifnextcharelse Pablo Rodriguez
2016-01-24 14:58 ` doifnextcharelse Meer, Hans van der
2016-01-24 18:15 ` doifnextcharelse Meer, Hans van der
2016-01-24 18:21 ` Wolfgang Schuster [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=56A51639.1070203@gmail.com \
--to=schuster.wolfgang@gmail.com \
--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).