Developer mode

[Steven Smith]

This would be very helpful.

I often have to rerun failed build commands by hand to troubleshoot problems.

Also, I’d note the following comments about the use of color to provide visual context for quickly parsing output. Both git and brew use color effectively.

Adding a feature, say, to color errors in red, would allow developers to quickly pinpoint problems, rather than scanning for the word “error,” which can be nontrivial if one is using tools over a mobile device or through a VNC connection. Or using color to visually highlight different port phases.

https://saagarjha.com/blog/2019/04/26/thoughts-on-macos-package-managers/
> Homebrew aims to be simple and easy to use, and in general this is true. While I’m neutral on the use of beer-related terminology and emoji, the judicious use of color is quite helpful, as is the well-formatted output. Most common usecases are straightforward, though occasionally commands can end up doing surprising things if you use them in strange ways.
> 
> MacPorts, on the other hand, is by no means unusable, but it’s not as polished as Homebrew is. The lack of color, as well as somewhat more cluttered and less relevant output, makes it a bit less pleasant to work with
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.macports.org/pipermail/macports-dev/attachments/20191201/c08aadda/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 3898 bytes
Desc: not available
URL: <http://lists.macports.org/pipermail/macports-dev/attachments/20191201/c08aadda/attachment.bin>