Join GitHub today
GitHub is home to over 28 million developers working together to host and review code, manage projects, and build software together.Sign up
Don't compile ansi_term on Windows #1155
However, this color re-write will be implemented in v3 (which actively being worked again after a stagnant period) and can be tracked via the overall v3 tracking issue #1037
I've implemented a feature freeze for v2 so I can actually get v3 out the door. So it shouldn't be long before v3-alpha1 is out.
I'm going to close this so comments can be consolidated in one place. I appreciate the suggestions @SergioBenitez and if
changed the title from
Move away from using ansi_term.
Don't compile ansi_term on Windows
Jan 31, 2018
For those compiling only to windows, not using the
I'm going to close this for now, and re-address once cargo supports per-target deps. I'll also keep this in mind during the great color redux in v3.
@retep998 I meant them somewhat interchangeably. The issue being the
What I'd like to happen is per-target features (so that on everything but Windows the
If this is already possible, I may have misunderstood the state of things.