On Sun, Sep 9, 2018 at 4:47 PM Markus Neteler <[email protected]> wrote: > > > > That gives little too much information, so perhaps: > > > > FILE="`./bin.x86_64-pc-linux-gnu/grass77 --tmp-location XY --exec which r.mask`" > > grass --tmp-location XY --exec python -m trace --trace $FILE -r | grep `basename $FILE` > > > > Or do you want GRASS parser to print every module being executed? > > Yes, just the sequence of commands along with the parameter/flags > used. Like "shell history" style. This would help for a quick > orientation in long Python scripts with functions etc.
This sounds like a good enhancement for the parser. Ticket?
_______________________________________________ grass-dev mailing list [email protected] https://lists.osgeo.org/mailman/listinfo/grass-dev
