On 2/13/2013 9:28 AM, Stephan Beal wrote:
On Wed, Feb 13, 2013 at 6:11 PM, Pirate Fibonacci <[email protected] <mailto:[email protected]>> wrote:.... I don't get the ADDED, and EDITED files. Also EXTRAS doesn't appear to be implemented. i.e. fossil extras.... a) The JSON API is centered on remote use, and remote use does not (typically) have a checked-out copy immediately available to it. None of the existing JSON commands know how to deal with a local check-out.
While true that you primarily use JSON in CLI mode as a debugging aid, it is a good tool for scripting fossil due to the much easier to parse output. Extending JSON to cover some capabilities that require a checkout would not harm the normal use of JSON as a remote API, and could aid those trying to tame some of the more unruly human-readable output of the natural fossil CLI interface.
.... Since you're apparently(?) using it from the CLI/shell script, how about grepping the output of (fossil status)? You might also want to look at (fossil all changes), but that probably isn't what you're looking for in this case.
The "fossil changes" command provides a nice simple list of changes not yet checked in. That would include the obvious edited files, along with pending renames, deletes, and uncommitted merges. If you also require a check for new files not yet added, "fossil extras" will be a starting point, but it can take quite a bit of effort tuning the ignore-glob setting to tame that output.
I do like Richard's recent hint about running "fossil all changes" occasionally to discover dangling work in progress that is the natural result of distractions. I knew about "fossil all" but hadn't noticed that changes was one of the commands it was willing to apply.
-- Ross Berteig [email protected] Cheshire Engineering Corp. http://www.CheshireEng.com/ _______________________________________________ fossil-users mailing list [email protected] http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
