Hi Hans,
> quite some commands are generated so we would still miss a lot
For any now-or-future documentation project, it will be useful to have
a list of macros that generate (user-facing) macros.
* We could use it to modify these macros so that they report to a
table the macros they create.
* We could use it to simply find the places these factory macros are
used, when constructing our list of commands
* We could use it when looking for the source of an indirectly-defined
command --- useful when writing options documentation.
So, for starters: below is a tab-separated list of various
\install*handler commands (and their frequency in the *.mk* sources).
I hope gmail doesn't mangle the formatting too badly.
Could you note, for each one,
* whether it is a top-level macro or simply a helper routine
* If it is a top-level macro, whether it creates user-facing commands
always, sometimes, or never?
(Working definition of top-level macros vs helper routines: macros
that you yourself call directly when writing functionality, versus
routines that you once split off to structure the code, and that only
gets called by some other macro.)
Kind regards,
Sietse
ii iv vi command
-- 2 -- \installactionhandler
-- 3 -- \installautocommandhandler
-- 3 -- \installautosetuphandler
-- 1 -- \installbasicautosetuphandler
-- 6 -- \installbasicparameterhandler
12 1 -- \installcolumnbreakhandler
2 61 24 \installcommandhandler
3 5 -- \installdefinehandler
-- 15 5 \installdirectcommandhandler
-- 3 -- \installdirectparameterhandler
-- 3 -- \installdirectparametersethandler
-- 3 -- \installdirectsetuphandler
-- 2 -- \installdirectstyleandcolorhandler
34 -- -- \installfloathandler
-- 1 -- \installfontandcolorhandler
-- 1 1 \installframedautocommandhandler
-- 10 11 \installframedcommandhandler
5 -- -- \installmarginlinehandler
16 -- -- \installmathmatrixhandler
26 1 -- \installpagebreakhandler
2 1 -- \installpagehandler
3 4 4 \installparameterhandler
2 2 -- \installparameterhashhandler
-- 2 -- \installparametersethandler
87 -- -- \installprettyhandler
1 1 -- \installregisterpagehandler
-- 2 -- \installrootparameterhandler
3 5 4 \installsetuphandler
-- 13 4 \installsetuponlycommandhandler
-- 10 17 \installsimplecommandhandler
-- 3 -- \installsimpleframedcommandhandler
5 -- -- \installspacehandler
-- 6 -- \installstyleandcolorhandler
-- 3 2 \installswitchcommandhandler
-- 2 -- \installswitchsetuphandler
--
Sietse Brouwer -- sbbrou...@gmail.com -- +31 6 13.456.848
Verlengde Wassenaarseweg 4a -- 2342 BG Oegstgeest -- the Netherlands
MSN: sie...@gawab.com -- ICQ: 341232104
On Tue, Sep 18, 2012 at 7:52 PM, Hans Hagen <pra...@wxs.nl> wrote:
> On 18-9-2012 18:44, Sietse Brouwer wrote:
>>
>> Michael K Rogers wrote:
>>>>
>>>> … tex/texmf-context/tex/context/interface/cont-en.xml
>>
>>
>> Hans wrote:
>>>
>>> indeed it needs updating (some time ago wolfgang started with it but it's
>>> a tedious job)
>>
>>
>> Hans, have you ever thought about creating a command
>> \defpublic[#commandname]{...} that works pretty much like
>> \def\commandname{...}, but also registers the name of the command it
>> defines to a table somewhere?
>
>
> yes but it does not help much unless the whole argument spec is included;
> also, quite some commands are generated so we would still miss a lot
>
> 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
___________________________________________________________________________________
