From: Wolfgang Schuster <schuster.wolfgang@googlemail.com>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: Example markup
Date: Fri, 12 Feb 2010 19:15:07 +0100 [thread overview]
Message-ID: <4B759AAB.6040303@googlemail.com> (raw)
In-Reply-To: <D70BFD31-44A5-40F5-9891-6BCCF12580A0@gmail.com>
Am 12.02.10 18:59, schrieb Bernhard Rosensteiner:
> maybe you mean something like that:
>
> \define[1]\example{\tfx#1\tfa}
>
brr, when you want to define it in this way you should use grouping, e.g.
\define[1]\example{{\tfx#1}}
a better solution is
\define\example{\groupedcommand{\tfx}{}}
because you can now write
\example{...} and {\example ...}
The best way is to use \definealternativestyle, e.g.
\definealternativestyle [example] [\tfx] [\tfx]
the command takes three arguments because you can set with
the third argument a different behaviour in titles etc.
A third way is \definestartstop, e.g.
\definestartstop[example][style=\tfx]
this creates not only the command \example but also a example
environment where you get a smaller font.
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 prev parent reply other threads:[~2010-02-12 18:15 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <mailman.270.1265959988.26807.ntg-context@ntg.nl>
2010-02-12 12:56 ` tabs in Lilypond Vyatcheslav Yatskovsky
2010-02-12 16:55 ` Example markup Vyatcheslav Yatskovsky
2010-02-12 17:59 ` Bernhard Rosensteiner
2010-02-12 18:15 ` Wolfgang Schuster [this message]
2010-02-12 18:28 ` Bernhard Rosensteiner
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=4B759AAB.6040303@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).