On 06/07/2017 09:02 PM, Idris Samawi Hamid ادريس سماوي حامد wrote: > [...] > As a matter of workflow, I would just check each \input when editing it, > don't see the need to check them all over and over - but maybe you have > some huge collaborative project with lots of \inputs frequently changing..
My project isn’t collaborative (I’m the only one who writes code there) and it is by no means huge. It is probably too complex for such simple mind as mine 😉. \inputs don’t change too frequently. But the code I wrote a month ago is totally forgotten to me. I mean, I read and I understand what I wrote, but I may not remember why I did something in that particular way. I don’t need external examination to see that the code is unnecessarily complex in many ways. But I’m neither a ConTeXt or programming expert. The most common problem is that we have different conditions that weren’t considered when writing the original code. And these code additions may cause trouble. Because they need to be implemented in the shortest period of time and in the not the quietest working environment. At least for me, this is the perfect scenario to forget to close something I opened before. That being said, "mtxrunjit --autogenerate --script check" is the perfect tool to spot those stupid errors. Many thanks for your help, Pablo -- http://www.ousia.tk ___________________________________________________________________________________ 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://context.aanhet.net archive : https://bitbucket.org/phg/context-mirror/commits/ wiki : http://contextgarden.net ___________________________________________________________________________________
