From: Jaroslav Hajtmar <hajtmar@gyza.cz>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: Problem with macro with optional parameter
Date: Tue, 27 Jun 2017 11:25:24 +0000 [thread overview]
Message-ID: <17154863-B53F-4758-BD94-A9206CE72ED7@gyza.cz> (raw)
In-Reply-To: <1498561531.23973.11.camel@gmail.com>
Thanx Henri for answer.
Maybe I have been explaining wrong my problem. I would need a variant without a parameter and concurrently without braces. Command without braces swallows the break of the paragraph.
\def\Command#1%
{\expdoifelse{#1}{}{100}{#1}}
\starttext
1. \Command{5} % OK
2. \Command % OK
3. As You see, Command without braces swallows the break of the paragraph.
1. \dorecurse{\Command{5}}{\recurselevel\crlf} % not working
2. \dorecurse{\Command{}}{\recurselevel\crlf} % not working
\stoptext
Jaroslav Hajtmar
Dne 27.06.17 13:05, ntg-context za uživatele Henri Menke <ntg-context-bounces@ntg.nl za uživatele henrimenke@gmail.com> napsal(a):
On Tue, 2017-06-27 at 08:58 +0000, Jaroslav Hajtmar wrote:
> Hello ConTeXist.
> I'm not able to solve a macros problem with one optional argument. I need the macro to return a
> value that can be used as a dorecurse loop parameter.
> Is there possibility create macro with optional parameter and parameter is concurrently inside in
> braces? (in nonsquare brackets)?
> I've tried to experiment with examples from the wiki, but I'm not clear about it.
>
> Thanx for help.
> Jaroslav Hajtmar
>
> Here is minimal example:
>
> \def\DoCommand[#1]%
> {\iffirstargument#1\else100\fi}
>
> \def\Command%
> {\dosingleargument\DoCommand}
>
> %\def\DoAnotherCommand{#1}%
> % {\iffirstargument#1\else100\fi}
>
> %\def\AnotherCommand%
> % {\dosingleargument\DoAnotherCommand}
>
> \starttext
>
> 1. \Command[5] % OK
>
> 2. \Command % OK
>
>
>
>
> %1. \dorecurse{\Command[5]}{\recurselevel\crlf} % not working
>
> %2. \dorecurse{\Command}{\recurselevel\crlf} % not working
The first argument to \dorecurse has to expand to a number. Therefore it has to be fully-
expandable. Scanning for optional brackets is never expandable. You have to do it this way:
\def\Command#1%
{\expdoifelse{#1}{}{100}{#1}}
\starttext
1. \Command{5} % OK
2. \Command{} % OK
1. \dorecurse{\Command{5}}{\recurselevel\crlf} % not working
2. \dorecurse{\Command{}}{\recurselevel\crlf} % not working
\stoptext
> \stoptext
> ___________________________________________________________________________________
> 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
> ___________________________________________________________________________________
___________________________________________________________________________________
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
___________________________________________________________________________________
___________________________________________________________________________________
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
___________________________________________________________________________________
prev parent reply other threads:[~2017-06-27 11:25 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-27 8:58 Jaroslav Hajtmar
2017-06-27 11:05 ` Henri Menke
2017-06-27 11:25 ` Jaroslav Hajtmar [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=17154863-B53F-4758-BD94-A9206CE72ED7@gyza.cz \
--to=hajtmar@gyza.cz \
--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).