Skip to main content

Seamless Error Highlighting

A lot of output can be generated when you compiling large projects. When it breaks, it can be difficult to identify the particular spot in the build-process where things when wrong. Highlighting the error messages can help them stand out from the rest of the output.

ANSI escape sequences can be used to modify how your terminal window displays its text. For example, outputting the sequence \033[41;37mHello World\033[0m would result in "Hello World" displayed in white text against a red background. Escape sequences begin with an escape character (ASCII 27, octal 033) and bracket. The control values are then given (multiple values are semicolon-separated) and the entire sequence closes with m.

You can highlight certain messages by routing the STDOUT and STDERR streams to sed and performing a replacement.
s,(.*error.*|.*fail.*|.*undef.*),\033[41;37m\1\033[0m,gi
The values you match are of course entirely up to your discretion.

The tricky part is quoting and escaping the expression correctly so various meta-characters aren't intercepted by the shell. And some implementations of sed won't correctly convert \033 to an escape character, so you may need to enter it directly by typing CTRL+V, CTRL+[. Depending on your terminal, an actual escape character may be displayed as ^[ or a special glyph like ESC when you enter it.
make install 2>&1 | sed -e \
's,\(.*error.*\|.*fail.*\|.*undef.*\),ESC[41;37m\1ESC[0m,gi'
If you find yourself using such highlighting often, you may want to define a function to save yourself some typing. For example, with bash you can add something like this to your .bashrc file:
function make() {
/usr/bin/make $@ 2>&1 | sed -e \
's,\(.*error.*\|.*fail.*\|.*undef.*\),ESC[41;37m\1ESC[0m,gi';
}
You can type make install at the prompt like you normally would. bash will call the new make() function, which in turn calls the actual make utility with any arguments (such as install) and colorizes the output. Error highlighting is now seamless and automatic!
Labels:

Comments

Post a Comment

Popular posts from this blog

Writing a Minimal PSR-0 Autoloader

An excellent overview of autoloading in PHP and the PSR-0 standard was written by Hari K T over at PHPMaster.com , and it's definitely worth the read. But maybe you don't like some of the bloated, heavier autoloader offerings provided by various PHP frameworks, or maybe you just like to roll your own solutions. Is it possible to roll your own minimal loader and still be compliant? First, let's look at what PSR-0 mandates, taken directly from the standards document on GitHub : A fully-qualified namespace and class must have the following structure \<Vendor Name>\(<Namespace>\)*<Class Name> Each namespace must have a top-level namespace ("Vendor Name"). Each namespace can have as many sub-namespaces as it wishes. Each namespace separator is converted to a DIRECTORY_SEPARATOR when loading from the file system. Each "_" character in the CLASS NAME is converted to a DIRECTORY_SEPARATOR . The "_" character has no special ...
6 comments
Read more

Composing Music with PHP

I’m not an expert on probability theory, artificial intelligence, and machine learning. And even my Music 201 class from years ago has been long forgotten. But if you’ll indulge me for the next 10 minutes, I think you’ll find that even just a little knowledge can yield impressive results if creatively woven together. I’d like to share with you how to teach PHP to compose music. Here’s an example: You’re looking at a melody generated by PHP. It’s not the most memorable, but it’s not unpleasant either. And surprisingly, the code to generate such sequences is rather brief. So what’s going on? The script calculates a probability map of melodic intervals and applies a Markov process to generate a new sequence. In friendlier terms, musical data is analyzed by a script to learn which intervals make up pleasing melodies. It then creates a new composition by selecting pitches based on the possibilities it’s observed. . Standing on Shoulders Composition doesn’t happen in a vacuum. Bach wa...
9 comments
Read more

Rent-free Thoughts

Some thoughts that have been living rent-free recently in my head about AI... We should be more precise when we talk about it. We’ve had "AI" for decades. Google Translate, Alexa and Siri, computer vision in video games, OCR in mail sorting, protein folding models all fall under artificial intelligence, but there’s no mass panic over these. The current progress is in generative AI, and that's where most of the public concern is. I’m guilty of the shorthand myself, saying "AI" when I mean "generative AI". People are afraid of generative AI, but the real problem is concentrated power and corporate greed. Someone wanting to sow disinformation could do so without generative AI models, and deep-pocket organizations of state could finance extreme actors if they wanted to. The tools evolved, but the risks aren’t new. The bigger problem that few are talking about is corporations who are aligning the technology for their own goals; they increasingly dicta...
Post a Comment
Read more