| Okay, this is still eluding me after spending several hours reading | through the source and I thought I'd double check that I have it | right. For some reason, shell snippets I include in the testsuite.at | file do no appear in the final output and I still can't figure out | why, much less how to change it. Am I doing something wrong? For | example: | | AT_TESTED([cvs]) | AT_INIT | for remote in false :; do | m4_include([init.at]) | m4_include([tests.at]) | done | | Runs the tests in init.at and tests.at but fails to run them twice, | once with remote set to true and once with it set to false. The shell | commands (the lines with the `for...do' and `done' on them don't even | appear in the final output.
Per design. | Any help is appreciated. My grasp of m4 and the autom4te program is | still coming back up to speed. I might be able to hack the fix with a | little help if this is a bug. The point is precisely that the tested code must be visible to the M4 machinery. That is why contrary to Autoconf, code not put into AT_ macros will not be issued.
