![](https://secure.gravatar.com/avatar/018bd5c575dea7380cf18968f26e5b07.jpg?s=120&d=mm&r=g)
That is a wonderful idea and one that would be very, very helpful, and much appreciated.
Best
Jonathan Barchi
Hi all,
I'm using the emacs package etexshow to provide a quick ConTeXt command reference in EMACS. This utility parses the interface file cont-en.xml (for english, in my case) and uses the contents to provide a basic dictionary of available commands.
In the documentation for etexshow, there is a reference to being able to generate a complete interface description (the aforementioned xml file) like so:
";; There is still an xml-file shipped with this code. Usually you would ;; generate the xml-file with 'texexec'ing the file setupe.tex. Then you ;; will get the cont-en.xml file that can (could) be used as an input for ;; this etexshow. But for now, this won't work. It will work rsn."
It is not clear whether that file (setupe.tex or setup.tex) is/was supposed to be shipped with etexshow or was supposed to be a part of context. I've searched and found a few references to this problem, but never a definitive answer, so if anyone knows the answer to these questions I would love to know!!
1. Is the referenced setup(e).tex a file that was previously shipped with ConTeXt - presumably mkii since the author refers to texexec - or would this be something the author would have included with etexshow itself?
2. Is the interface file, e.g. cont-en.xml, auto-generated from all of the defined macros in ConTeXt, or is that file hand-written as metadata to accompany the source-code definitions?
3. Since self-documentation is a goal of the project, is it possible to generate something akin to the interface file that presents a snapshot of all commands known to context at a given time, for use in things like etexshow or other tools? If so, is it possible to do this with modules loaded to see what they additionally define?
Thanks in advance for any help! I'm hoping to use any information I get to update etexshow, if possible, and maybe update the ConTeXt support in AUCTEX as well. I think it would be really cool if AUCTEX could reach out at compile or run time and pull in macro definitions from the installed environment, for example.
Best, Jon ___________________________________________________________________________________ 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 ___________________________________________________________________________________