Tommy Pettersson wrote: > Maybe the script writing part could be eased if darcs is given a very > simple query command that prints the absolute path to the repo root > directory? > > d=$(darcs query root) for f in $(darcs what | extract); do process > $d/$f; done
In my opinion this is a good idea. "darcs info" could output some information about the repository, such as path information about the current and the root path, in colon delimited "key: value" pairs, whereas "darcs info key" could output the key's value for easy scripting (read: quote strings with double quotes if they contain spaces, and so on). I really do not want to see break darcs break the semantics of directory specification virtually on every known operating system, so I would vote for not taking the darcs root directory into account when evaluating paths. So "darcs whatsnew ." will show you all files new in the current subdir, with paths starting at the current subdir, as well as "darcs whatsnew". For displaying changes repo wide (cf Tommy's example above) darcs whatsnew `darcs info root` should do. (Reason: When typing "ls" you also don't expect that to be aliased to "ls $HOME" or similar.) Thomas -- Thomas Prokosch Tact is the art of making a point without making an enemy. _______________________________________________ darcs-users mailing list [email protected] http://www.abridgegame.org/mailman/listinfo/darcs-users
