Yann Chemin wrote: > Just wanted to keep exact track of the processing leading to a new layer. > > 1 - would it be feasible to store the whole processing line with > parameters (i.e. r.something -a input=file_in output-file_out etc...) > as metadata in the output file of a module ?
G_command_history() already does this, i.e. it appends the result of G_recreate_command() to the history. > 2 - would it be interesting to make a scripts/ place inside a mapset > where scripts would get automatically saved with something like: > YYYYMMMDDHHHHH_MODULE_NAME.sh or the like? I'm not sure what you're suggesting here. GRASS (the libraries and modules) only knows which commands are run; it doesn't know *how* they are run, e.g. if they are part a script, if they were typed into the shell, executed by the GUI, etc. -- Glynn Clements <[EMAIL PROTECTED]> _______________________________________________ grass-dev mailing list grass-dev@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/grass-dev
