Will do, having granularity like that would be mighty handy. I'll ping off
an email in a sec.
A.
ps. the return status 0 i was getting in my original post was due to a
pipe'd command and forgetting to execute "exit ${PIPESTATUS[0]}" in my nuke
wrapper.
On 31 March 2011 14:55, Sebastian Elsner <[email protected]> wrote:
> I have recently logged a feature request for different exit codes. For
> example when there is no write activated return 2 instead of 1. afaik 1 is
> returned in all error cases right now. The request is: #17486. If this is
> important to you please write to the support so they may up the priority :).
>
>
> On 03/31/2011 03:46 PM, Andrew Bunday wrote:
>
>> Hi,
>>
>> Is there a list available of any exit status' which Nuke will return
>> with in the event of an error? I'm most interested since it seems that
>> if I fluff up a command line option such as "-F 1-100-x", that whilst
>> nuke will exit immediately it returns with zero.
>>
>> I'd have thought that should warrant a non-zero code of kind.
>>
>> Cheers,
>>
>> Andy
>>
>> --
>> Andrew Bunday
>>
>> BASEBLACK
>> London
>> baseblack.com <http://baseblack.com/>
>>
>>
>>
>>
>> _______________________________________________
>> Nuke-dev mailing list
>> [email protected]
>> http://support.thefoundry.co.uk/cgi-bin/mailman/listinfo/nuke-dev
>>
>
> --
> Sebastian Elsner - Pipeline TD - r i s e | fx
>
> t: +49 30 201 803 00 [email protected]
> c: +49 175 336 5739 7548 www.risefx.com
>
> r i s e | fx GmbH
> Schlesische Strasse 28, Aufgang B 10997 Berlin
> Richard-Byrd-Strasse 12, 50829 Cologne
> Geschaeftsfuehrer: Sven Pannicke, Robert Pinnow
> Handelsregister Berlin HRB 106667 B
> _______________________________________________
> Nuke-dev mailing list
> [email protected]
> http://support.thefoundry.co.uk/cgi-bin/mailman/listinfo/nuke-dev
>
--
Andrew Bunday
BASEBLACK
London
baseblack.com
_______________________________________________
Nuke-dev mailing list
[email protected]
http://support.thefoundry.co.uk/cgi-bin/mailman/listinfo/nuke-dev
