Re: [dev-context] audit of commands

Hans Hagen wrote:

On 7-5-2010 10:07, luigi scarso wrote:

...

2010/5/7 Hans Hagen:

...

On 7-5-2010 9:41, luigi scarso wrote:

...

Starting from it, and modifying the pdftew.web, I've produced the lists of all macros and their meaning simple put something like \tracingmacros3 etc at the beginning of context.tex and then rebuild the format. I can revisit it now for luatex: this should still work for TeX macros but not for Lua functions, I believe.

already there for a while:

context --dumphash yourfile context --dumpdelta yourfile

of course undocumented apart from context --help --expert yes, but what I meant was something like \tracingall \starttext

\stoptext and then parsing the log extracting macro& their meaning

even their meaning? that would be huge

You could use the --dumphash output to get a list of meanings (with a bit of lua processing to run \meaning\<csname>), but in general the meanings are not always that useful, because a lot of macros expand into \dosingleempty c.s. Best wishes, Taco