From: "Wolfgang Werners-Lucchini" <wwl@musensturm.de>
To: ntg-context@ntg.nl
Subject: Re: defining commands
Date: Sat, 06 Feb 2010 16:29:39 +0100 [thread overview]
Message-ID: <4B6D98F3.28475.14AA38E@wwl.musensturm.de> (raw)
In-Reply-To: <mailman.170.1265412781.26807.ntg-context@ntg.nl>
Hallo,
> >> btw, i'm sure that you've seen
> >>
> >> \starttexdefinition blabla #1 #2
> >>
> >> which like setups ignores spaces so one can have readable
> macros
> > i was the one who requested the parameterless version
> >
> > \starttexdefinition commandonly
I experimented a little with this:
----------------------------------------
\starttexdefinition BIS #1 #2
[#1 \ldots\ #2]
\stoptexdefinition
\starttext
\BIS1 23
\BIS{10}{20}30
\BIS {10}{20}30
\BIS{10} {20}30
\BIS{10}{20} 30
\BIS {10} {20}30
\BIS{10} {20} 30
\BIS {10} {20} 30
\stoptext
----------------------------------------
and get this:
----------------------------------------
[1 ... 2]3
[102030 ...
][102030 ...
][10 ... 20]30
[1020 ... 3]0
[10 ... 20]30
[10 ... 20] 30
[10 ... 20] 30
----------------------------------------
So it seems, that the first blank between command and #1 is optional.
But the second between #1 and #2 is NEEDED. A last blank after #2 is
not needed and not eaten.
Wolfgang
___________________________________________________________________________________
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 parent reply other threads:[~2010-02-06 15:29 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <mailman.170.1265412781.26807.ntg-context@ntg.nl>
2010-02-06 15:29 ` Wolfgang Werners-Lucchini [this message]
2010-02-05 8:03 Marius
2010-02-05 9:29 ` Wolfgang Schuster
2010-02-05 13:57 ` Marius
2010-02-05 17:36 ` Hans Hagen
2010-02-05 17:53 ` Hans Hagen
2010-02-05 18:08 ` Wolfgang Schuster
2010-02-05 18:19 ` Hans Hagen
2010-02-05 18:21 ` Wolfgang Schuster
2010-02-05 18:29 ` Hans Hagen
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=4B6D98F3.28475.14AA38E@wwl.musensturm.de \
--to=wwl@musensturm.de \
--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).