From: Hans Hagen <pragma@wxs.nl>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: How to find the source code/documentation for a specific command
Date: Wed, 17 Apr 2013 15:19:32 +0200 [thread overview]
Message-ID: <516EA164.1060900@wxs.nl> (raw)
In-Reply-To: <20130416205320.469EF94016C@smtp1-g21.free.fr>
On 4/16/2013 10:34 PM, contact@thomas-corbiere.name wrote:
> Hi Hans,
> I searched for the files you reffered to and found them in the path
> “context\tex\texmf-context\tex\context”. Can I assume most (all?)
> commands are defined here?
indeed, all the core commands are defined in:
tex/context/base
> From what you said, do you mean that the code for a single command
> may be split into multiple files?
normally it's done in one file, unless we're dealing with a combination
of functionality
> I found the test files. What a great collection of examples! This sure
> will help.
Hans
-----------------------------------------------------------------
Hans Hagen | PRAGMA ADE
Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
tel: 038 477 53 69 | voip: 087 875 68 74 | www.pragma-ade.com
| www.pragma-pod.nl
-----------------------------------------------------------------
___________________________________________________________________________________
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
___________________________________________________________________________________
prev parent reply other threads:[~2013-04-17 13:19 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-16 16:07 contact
2013-04-16 16:25 ` Hans Hagen
2013-04-16 20:34 ` contact
2013-04-17 13:19 ` 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=516EA164.1060900@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).