In which we handle some escape codes, or rather have someone else handle them.
So first we write the other three tests to complete the
RequireMakeRecallReagent tests: We need
the reagent but don’t have it, we don’t need it but do have it, and we do need it and do have it.
Not too difficult.
A truly sad path:
270 271 272 273
1 2 3
Process that output
Paging through the debug output from some of these tests, it’s clear that I need to start handling the ANSI escape codes.
1 2 3 4 5 6 7 8 9 10 11 12 13 14
Ruby gems to the rescue: turns out there’s an
that handles the escape codes. With the latest version being published in 2007, I wondered if it
would actually work with modern Ruby; and in fact it did not. But I found a more modern fork
which did work when I downloaded and installed it.
A dog ~~~~~~~~~~~~ ~~. . . . . ~~. v . . . ~~. . . . . ~~. . . A . ~~. . . . . Your spellbook explodes! -> R Hits : 20/36 Hits Taken : 16 L Experience : 4996 Magic Points: 4 Stamina : 10
With a small amount of tweaking, not too bad for embedding in blog posts and/or html test results. I’ll have to figure out how to fold it into my test process in a portable way. Tomorrow.
- Sublime Text 3 docs for build systems
- Sublime Text package for Git
- rspec expectations
- ANSI escape sequences
- ansi-sys gem current fork