When TERM=dumb, rust build dies mysteriously

[pnkfelix]

% echo $TERM
dumb
% x86_64-apple-darwin/stage1/bin/rustc --cfg stage1  -O -Z no-debug-borrows --target=x86_64-apple-darwin   -o x86_64-apple-darwin/stage1/lib/rustc/x86_64-apple-darwin/lib/libsyntax.dylib /Users/fklock/Dev/Mozilla/rust.git/src/libsyntax/syntax.rs
/Users/fklock/Dev/Mozilla/rust.git/src/libsyntax/ext/pipes/proto.rs:148:9: 148:20 warning: error: % 

Discussion in #rust implies that this might have been injected by SHA: 0ae203a

[lilyball]

Looks like the problem is reset() calls unwrap() directly on the results of looking up op, which dumb doesn't support. This used to work because it used to only do this if color_supported, but with the removal of that boolean, it always tries to emit the op code.

This was a problem before, if you could find a terminfo that defined setaf, setab, and had colors >= 16, but did not define op.