From: Femke Snelting <snelting@collectifs.net>
To: ntg-context@ntg.nl
Subject: Re: one entry, multiple registers
Date: Fri, 20 Feb 2009 09:15:16 +0100 [thread overview]
Message-ID: <499E6694.4020605@collectifs.net> (raw)
In-Reply-To: <499D659F.2070200@wxs.nl>
> there is no such sharing built in (for context mkiv i will probably
> provide a merge registers features)
>
> \def\VegetableAndOrange#1%
> {\Vegetable{#1}\Orange{#1}#1}
Thanks for your quick answer and we're looking forward to the merge
register features
groet,
Femke
___________________________________________________________________________________
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 : https://foundry.supelec.fr/projects/contextrev/
wiki : http://contextgarden.net
___________________________________________________________________________________
prev parent reply other threads:[~2009-02-20 8:15 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-19 13:21 Femke Snelting
2009-02-19 13:58 ` Hans Hagen
2009-02-20 8:15 ` Femke Snelting [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=499E6694.4020605@collectifs.net \
--to=snelting@collectifs.net \
--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).