Nathan, I've checked your latest fix on this, but sass does not behave idempotent on failed updates, i.e. the first call now correctly returns an error code, but any further still returns 0.
--bb On Aug 13, 7:04 pm, Nathan Weizenbaum <[email protected]> wrote: > This is not intentional so much as just not considered. I'll add an exit > code as part of the push this weekend. > > > > > > > > On Fri, Aug 13, 2010 at 1:57 AM, bitbowl <[email protected]> wrote: > > Hi, > > > when updating a tree via > > > sass --scss --update in:out > > > sass returns a 0 as exit code even in case of compilation errors. > > Anybody knows if this is intended or could be customized (to return an > > error code like 1)? > > > thanks, > > --bb > > > -- > > You received this message because you are subscribed to the Google Groups > > "Haml" group. > > To post to this group, send email to [email protected]. > > To unsubscribe from this group, send email to > > [email protected] <haml%[email protected]>. > > For more options, visit this group at > >http://groups.google.com/group/haml?hl=en. -- You received this message because you are subscribed to the Google Groups "Haml" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/haml?hl=en.
