From: "Meer, Hans van der" <H.vanderMeer@uva.nl>
To: NTG ConTeXt <ntg-context@ntg.nl>
Subject: Re: doifnextcharelse
Date: Sun, 24 Jan 2016 14:58:06 +0000 [thread overview]
Message-ID: <7BBE743F-DD78-44AF-B4FA-8D71A833C918@uva.nl> (raw)
In-Reply-To: <56A4DC0B.6050408@gmx.es>
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.
Hans van der Meer
met vriendelijke groet
Hans van der Meer
> On 24 Jan 2016, at 15:13, Pablo Rodriguez <oinos@gmx.es> wrote:
>
> On 01/24/2016 02:30 PM, dr. Hans van der Meer wrote:
>> I would like to differentiate on the following character being one of X or not X.
>> But cannot get it right in \doifnextcharelse.
>>
>> For example
>> \def\mynextchar{\doifnextcharelse{X}{\def\Next{Y}}{\def\Next{Z}}\Next} delivers: ZX ZQ
>> then input: \mynextchar X \mynextchar Q
>> I hoped for YX ZQ, but it looks as if X tested false against X.
>>
>> How to?
>
> Hans,
>
> the basic \def\mynextchar{\doifnextcharelse{x}{y}{z}} works.
>
> With your sample:
>
> \def\mynextchar{
> \doifnextcharelse{X}
> {\def\Next{Y}\Next}
> {\def\Next{Z}\Next}}
>
> I hope it helps,
>
>
> 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://tex.aanhet.net
archive : http://foundry.supelec.fr/projects/contextrev/
wiki : http://contextgarden.net
___________________________________________________________________________________
next prev parent reply other threads:[~2016-01-24 14:58 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 ` Meer, Hans van der [this message]
2016-01-24 18:15 ` doifnextcharelse Meer, Hans van der
2016-01-24 18:21 ` doifnextcharelse Wolfgang Schuster
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=7BBE743F-DD78-44AF-B4FA-8D71A833C918@uva.nl \
--to=h.vandermeer@uva.nl \
--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).