From: Wolfgang Schuster <schuster.wolfgang@googlemail.com>
To: ntg-context@ntg.nl
Subject: creating environments
Date: Mon, 29 Jan 2007 13:21:12 +0100 [thread overview]
Message-ID: <20070129132113.06a4e2ba.schuster.wolfgang@googlemail.com> (raw)
Hi all,
I have a module with a envrionment defined in the following way:
\def\startFOO#1\stopFOO{...#1...}
I try currently to write a command \defineFOO[MYFOO] that expands to my
already created environment.
\startMYFOO#1\stopMYFOO -> \startFOO#1\stopFOO
I know it is possible to make this in the following way:
\def\startMYFOO#1\stopMYFOO{\startFOO#1\stopFOO}
but this not what I want.
Wolfgang
next reply other threads:[~2007-01-29 12:21 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-29 12:21 Wolfgang Schuster [this message]
2007-01-29 15:15 ` Aditya Mahajan
2007-01-30 13:01 ` Wolfgang Schuster
2007-01-30 15:05 ` Aditya Mahajan
2007-01-31 10:15 ` Wolfgang Schuster
2007-01-31 10:59 ` Hans Hagen
2007-01-31 16:24 ` Wolfgang Schuster
2007-02-05 13:01 ` 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=20070129132113.06a4e2ba.schuster.wolfgang@googlemail.com \
--to=schuster.wolfgang@googlemail.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).