ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Wolfgang Schuster <schuster.wolfgang@gmail.com>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: Check the character after a macro
Date: Fri, 1 May 2015 21:10:38 +0200	[thread overview]
Message-ID: <115C960A-A7EF-41E2-B256-13AB07178F41@gmail.com> (raw)
In-Reply-To: <20150501184108.GA17861@amnay.crous.lan>


[-- Attachment #1.1: Type: text/plain, Size: 1837 bytes --]


> Am 01.05.2015 um 20:41 schrieb Sam Ḥilluc <shilluc@gmx.com>:
> 
> On 2015-05-01 19:38, Otared Kavian wrote:
>> Hi,
>> 
>> You have several commands in ConTeXt doing what you are seeking to do: please look at the examples below:
>> 
>> %%% begin do-if-inset.tex
>> \starttext
>> \type{\doifinset{A}{A,B,C}{should go}:} \doifinset{A}{A,B,C}{should go}
>> 
>> \type{\doifinset{D}{A,B,C}{should go}:}  \doifinset{D}{A,B,C}{should participate}
>> 
>> 
>> \type{\doifnotinset{}{A,B,C}{not in the set}:} \doifnotinset{}{A,B,C}{not in the set}
>> 
>> \type{\doifnotinset{D}{A,B,C}{not in the set}:} \doifnotinset{D}{A,B,C}{not in the set}
>> 
>> \doifinsetelse{D}{A,B,C}{it is in the set}{it is not in the set}
>> 
>> \define\test{B}
>> 
>> \type{\doifinsetelse{\test}{A,B,C}{\test\ is in the set}{\test\ is not in the set}}
>> 
>> \doifinsetelse{\test}{A,B,C}{\test\ is in the set}{\test\ is not in the set}
>> \stoptext
>> %%% end do-if-inset.tex
>> 
>> Best regards: OK
> 
> This works for testing if a given character is in a set, but how can I retrieve
> that character just after the defined macro.
> 
> To give an example, a macro that adds a dot if the next character is not a
> comma.
> 
>    \MyMacro{text1} text2     ->      text1. text2
>    \MyMacro{text1}, text2    ->      text1, text2


You can use the \doifelsenextchar command to check the character after your command.

\define[1]\MyMacro
  {\doifelsenextchar{,}
     {#1}
     {#1. }}

\starttext

\MyMacro{left} right

\MyMacro{left}, right

\stoptext


The limitation of this method is that you check only for one character at a time
and when want to check for more you have to use multiple \doifelsenextchar lines.

\doifelsenextchar{,}
  {...}
  {\doifelsenextchar{.}
     {...}
     {...}}

Wolfgang

[-- Attachment #1.2: Type: text/html, Size: 9625 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
___________________________________________________________________________________

  reply	other threads:[~2015-05-01 19:10 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-05-01 16:56 Sam Ḥilluc
2015-05-01 17:38 ` Otared Kavian
2015-05-01 18:41   ` Sam Ḥilluc
2015-05-01 19:10     ` Wolfgang Schuster [this message]
2015-05-01 21:53       ` Sam Ḥilluc

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=115C960A-A7EF-41E2-B256-13AB07178F41@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).