I wrote a simple GUI for Fossil using .NET for myself. After reviewing the source code for the commands I used, I concluded that all errors were written to stderr. By redirecting and displaying stdout / stderr I was able to provide feedback as to the success or failure of a command.
Also, fossil.exe exits with zero if all is well, otherwise non-zero: fossil_exit(0); or fossil_exit(1); Tony Perovic Compumation, Inc. -----Original Message----- From: fossil-users-boun...@lists.fossil-scm.org [mailto:fossil-users-boun...@lists.fossil-scm.org] On Behalf Of Gilles Sent: Friday, June 07, 2013 6:00 AM To: fossil-users@lists.fossil-scm.org Subject: [fossil-users] Fossil.exe: Catching errors? Hello I'd like to write a GUI front-end for fossil.exe to avoid having to open a DOS box and type Fossil commands. Does someone know of a way to catch errors, if any, instead of parsing the output returned by the application to figure it out? Thank you. _______________________________________________ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users _______________________________________________ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
