Re: [dev-context] audit of commands
2010/5/6 Idris Samawi Hamid ادريس سماوي حامد isha...@colostate.edu: Dear gangsters, I'm interested in an audit of all current mid-to-high-level mkiv commands, including experimental or undocumented ones. I'm trying to come up with, as much as possible, a set of context commands which is mutually exclusive jointly exhaustive. By 'mutually exlcusive' in this context I mean that I want to identify, for redundant commands, the deprecated commands and use only the current. No point teaching old methods. By 'jointly exhaustive' I mean that i don't want to leave anything out, at least not yet. Some of, eg, the bidi and otf control is undocumented, and I can dig those up. OTOH there are lots of other areas where there may be some commands of interest that only get brought up on the list occasionally... by mid-level I mean commands like \define or other user-friendly non-plain commands that may be used to create mkiv macros etc. Aside from core developers Hans and Taco: Luigi, Wolfgang and Mojca seem to have extensive knowledge of the internals... any ideas how we can do this in an efficient manner? My idea is to organize this list in interesting ways for pedagogical purposes, for the current book project. Again, ONLY MKIV is under consideration; as far as this book project is concerned, only mkiv exists ;-) Any help is greatly appreciated! I remember a tally variable in pdftex that governs the lenght of line used in trace commands 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. -- luigi ___ dev-context mailing list dev-context@ntg.nl http://www.ntg.nl/mailman/listinfo/dev-context
Re: [dev-context] audit of commands
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 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 - ___ dev-context mailing list dev-context@ntg.nl http://www.ntg.nl/mailman/listinfo/dev-context
Re: [dev-context] audit of commands
On 7-5-2010 10:07, luigi scarso wrote: 2010/5/7 Hans Hagenpra...@wxs.nl: 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 (with --dumphash you get the macros + some statistics) 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 - ___ dev-context mailing list dev-context@ntg.nl http://www.ntg.nl/mailman/listinfo/dev-context
Re: [dev-context] audit of commands
Hans Hagen wrote: On 7-5-2010 10:07, luigi scarso wrote: 2010/5/7 Hans Hagenpra...@wxs.nl: 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 ___ dev-context mailing list dev-context@ntg.nl http://www.ntg.nl/mailman/listinfo/dev-context
Re: [dev-context] audit of commands
if you have problems http://www.logosrl.it/luatex/cont-en.log.bz2 -- luigi ___ dev-context mailing list dev-context@ntg.nl http://www.ntg.nl/mailman/listinfo/dev-context
Re: [dev-context] audit of commands
Idris, maybe this is what you are looking for: http://www.pragma-ade.com/general/qrcs/setup-en.pdf And at the same time I have a question. Does this list of commands is the most recent? Is it generated automaticaly? 2010/5/7 Idris Samawi Hamid ادريس سماوي حامد isha...@colostate.edu: Hi Luigi, On Fri, 07 May 2010 01:41:09 -0600, luigi scarso luigi.sca...@gmail.com wrote: Again, ONLY MKIV is under consideration; as far as this book project is concerned, only mkiv exists ;-) Any help is greatly appreciated! I remember a tally variable in pdftex that governs the lenght of line used in trace commands 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. I don't pretend to 100% understand you ;-) but I greatly appreciate this. I guess is should also be simple enough to ignore the dedicated mkii files where there are two versions of the macros. How and when can I see that list? Or maybe better: post the list on yours or the main wiki page and then we can all contribute/discuss to make sure it's complete, identify and tag the deprecated/obsolete/redundant commands, etc... Peace Idris -- Professor Idris Samawi Hamid, Editor-in-Chief International Journal of Shi`i Studies Department of Philosophy Colorado State University Fort Collins, CO 80523 ___ dev-context mailing list dev-context@ntg.nl http://www.ntg.nl/mailman/listinfo/dev-context ___ dev-context mailing list dev-context@ntg.nl http://www.ntg.nl/mailman/listinfo/dev-context
Re: [dev-context] audit of commands
Hi, On Fri, 07 May 2010 08:04:06 -0600, Marius mariau...@gmail.com wrote: Idris, maybe this is what you are looking for: http://www.pragma-ade.com/general/qrcs/setup-en.pdf That list is not complete. For example, in open type we have a lot of fontfeature commands in mkiv only. The sourse is also full of useful goodies -- some very old even -- that often don't get documented or may even be forgotten. It always amazes me how Wolfgang pops up with one of these every now and then... In other areas Hans may have developed a number of other experimental or other commands as well particular to the interests of another set of users. Hence the idea for an audit of mkiv commands. Best wishes Idris And at the same time I have a question. Does this list of commands is the most recent? Is it generated automaticaly? -- Professor Idris Samawi Hamid, Editor-in-Chief International Journal of Shi`i Studies Department of Philosophy Colorado State University Fort Collins, CO 80523 ___ dev-context mailing list dev-context@ntg.nl http://www.ntg.nl/mailman/listinfo/dev-context
Re: [dev-context] audit of commands
On Fri, May 7, 2010 at 4:05 PM, Marius mariau...@gmail.com wrote: Idris, maybe this is what you are looking for: http://www.pragma-ade.com/general/qrcs/setup-en.pdf And at the same time I have a question. Does this list of commands is the most recent? Is it generated automaticaly? If I remember well the sources are here minimals/tex/texmf-context/tex/context/interface -- luigi ___ dev-context mailing list dev-context@ntg.nl http://www.ntg.nl/mailman/listinfo/dev-context
Re: [dev-context] audit of commands
On 7-5-2010 4:05, Marius wrote: the most recent? Is it generated automaticaly? yes - 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 - ___ dev-context mailing list dev-context@ntg.nl http://www.ntg.nl/mailman/listinfo/dev-context
