On Sun, Oct 20, 2013 at 6:21 PM, wrote:
> Ok, reading stderr output is working.
> Never knew that couldn't be redirected with pipe?
>
No idea about Windows, but everywhere else stderr can be redirected just
like stdout:
myapp 2> stderr.out
or redirected to stdout, effectively combining the two
Ok, reading stderr output is working.
Never knew that couldn't be redirected with pipe?
On Sat, Oct 19, 2013 at 7:01 PM, wrote:
> Hi, I'm also attempting more and more automation of fossil cmd's dear to
> me.
> At this point, I'd like to limit my code to parsing fossil.exe output
> until I have
Hi, I'm also attempting more and more automation of fossil cmd's dear to me.
At this point, I'd like to limit my code to parsing fossil.exe output until
I have more time to invest in the fossil.lib.
Using Windows 7 x86 admin console and fossil v1.28 [feef]:
For a purposely failed commit:
c:\tryfos
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-use
, 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, inste
On Fri, Jun 7, 2013 at 1:00 PM, Gilles wrote:
> Does someone know of a way to catch errors, if any, instead of parsing
> the output returned by the application to figure it out?
>
Try to do so opens up a huge box of worms - we have no standards on how the
output looks and it might be changed out
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.
_
7 matches
Mail list logo
