From: Brooks Moses <bmoses@stanford.edu>
Subject: Re: LaTeX \newcommands in ConTeXt.
Date: Mon, 25 Jul 2005 18:03:23 -0700 [thread overview]
Message-ID: <4.3.1.2.20050725173054.02ab1a98@cits1.stanford.edu> (raw)
In-Reply-To: <42E575B0.3040900@wxs.nl>
At 04:28 PM 7/25/2005, you wrote:
>Brooks Moses wrote:
>>I'd particularly appreciate any comments on the \newcommand and counters
>>implementations -- those are in the t-ltcmds and t-ltcnts modules, though
>>\newcommand also depends on t-lterrs and t-ltbase.
>
>i just took a quick look at the code; if you run into tricky definitions,
>let me know, often there are either already low level macros that do the
>job, or i can add some stuff;
Thanks! I'll probably have lots of questions as I go along -- this is
certainly becoming a tour of the internals of both systems.
>btw, i renamed the internal \end macro so that you can get away from
>stoptext refinitions (too messy)
Yeah, the \stoptext redefinition was one of the first pieces I wrote,
nearly a year ago. The reason I was doing the \stoptext redefinition
wasn't the internal \end macro (which didn't exist then, I think) -- it was
that the ConTeXt version I used then didn't have an \everystoptext
hook. But now that it exists, I can just use it.
One other question I have right now: what's a good way to duplicate LaTeX's
\vspace macro (which is effectively a \vskip inside), without causing the
problems that the ConTeXt manual warns about if we use \vskip?
- Brooks
next prev parent reply other threads:[~2005-07-26 1:03 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-25 6:15 Brooks Moses
2005-07-25 23:28 ` Hans Hagen
2005-07-26 1:03 ` Brooks Moses [this message]
2005-07-26 7:08 ` Hans Hagen
2005-09-23 17:01 ` Patrick Gundlach
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=4.3.1.2.20050725173054.02ab1a98@cits1.stanford.edu \
--to=bmoses@stanford.edu \
--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).