ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Pablo Rodriguez <oinos@gmx.es>
To: ntg-context@ntg.nl
Subject: Re: \doifelse not working, \doiftextelse breaking
Date: Fri, 9 Oct 2020 16:31:20 +0200	[thread overview]
Message-ID: <73ddf63a-0d36-aa25-6e0d-b589199c93a6@gmx.es> (raw)
In-Reply-To: <bbad4b8c-e1b7-0992-1ac8-0467ac73b853@gmail.com>

On 10/9/20 4:08 PM, Wolfgang Schuster wrote:
> [..]
> You need a % at the end of the definition, otherwise TeX expects a space
> after the second argument to end the command.
>
> \unexpanded\def\startswith[#1][#2]%
>    {...}

Many thanks for your ultra-fast reply, Wolfgang.

Now I see muy mistake. In my previous command definitions with two
arguments, the opening brace was right after the second argument.

> To improve your command and allow a space between both arguments you can use
>
> \unexpanded\def\startswith
>    {\dodoubleargument\dostartswith}
>
> \def\dostartswith[#1][#2]%
>    {...}

Now I see with \dosingleargument, \dodoubleargument and
\dotripleargument are there.

Which are the improvements to the command added by \do*argument?

> or just add a dummy parameter and use #1 and #3 to pass the arguments
>
> \unexpanded\def\startswith[#1]#2[#3]%
>    {...}

This is shorter, but it looks to creepy (even for my code).

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 14:31 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-10-09 13:58 Pablo Rodriguez
2020-10-09 14:08 ` Wolfgang Schuster
2020-10-09 14:31   ` Pablo Rodriguez [this message]
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=73ddf63a-0d36-aa25-6e0d-b589199c93a6@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).