From: Hans Hagen <pragma@wxs.nl>
Subject: Re: About \defineshortcut
Date: Wed, 21 Dec 2005 10:06:12 +0100 [thread overview]
Message-ID: <43A91B04.3040207@wxs.nl> (raw)
In-Reply-To: <43A909FE.6020501@mail.ru>
Radhelorn wrote:
> It is a pity that such useful command (setups) remains undocumented.
> As far as I understand inside setups can be any commands and
> environment changes are fully restored after their execution. Right?
> And \setups command can replace any single command (in arguments and
> such).
catcode changes are always tricky; if you make a style that uses them
you also need to make sure that they will not clash with other changes
(e.g. in the otr); nowadays, an active < is not that much of a problem
since this is what the xml parser does anyway and context knows how to
deal with that
>
> If this is OK, then I will try to collect some more examples and post
> them on the WIKI later this week.
>
ok, or maybe a myway document ...
Hans
prev parent reply other threads:[~2005-12-21 9:06 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-12-15 21:31 Radhelorn
2005-12-16 19:18 ` Taco Hoekwater
2005-12-17 12:38 ` Radhelorn
2005-12-17 13:49 ` Taco Hoekwater
2005-12-20 21:37 ` Radhelorn
2005-12-20 22:28 ` Hans Hagen
2005-12-21 7:53 ` Radhelorn
2005-12-21 9:06 ` Hans Hagen [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=43A91B04.3040207@wxs.nl \
--to=pragma@wxs.nl \
--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).