From: John Culleton <john@wexfordpress.com>
Subject: Internal documentation of Context modules.
Date: Mon, 19 Apr 2004 17:50:10 -1000 [thread overview]
Message-ID: <200404191750.10425.john@wexfordpress.com> (raw)
I have figured out that there is a way to print out the
internal documentation of the various Context modules in a
manner that makes some sense. I first use grep to extract
all the %D lines of a module into a separate file e.g.,
foo.tex. Then I eliminate the %D tag from all lines using
Vim. I add \starttext and \stoptext statements. Then I run
texexec --pdf foo.tex.
The result is imperfect but more or less intelligible. It
seems to me that there might be a script buried somewhare
in the system that does this better. If so, what is it
called?
--
John Culleton
Able Typesetters and Indexers
http://wexfordpress.com
next reply other threads:[~2004-04-20 3:50 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-04-20 3:50 John Culleton [this message]
2004-04-19 22:08 ` Nikolai Weibull
2004-05-01 19:46 ` behavior of counter - bug or feature? Thomas A.Schmitz
2004-05-04 15:56 ` Hans Hagen
2004-05-06 8:30 ` Thomas A.Schmitz
2004-04-20 8:52 ` Internal documentation of Context modules Tobias Burnus
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=200404191750.10425.john@wexfordpress.com \
--to=john@wexfordpress.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).