Okay, so you’re wondering what the hell I’m talking about. Fair enough.
I’ve got this problem, see, where sometimes I don’t know what status code with which my bash utilities exit. Say I’m trying to add an SSL certificate to
openssl and it’s the first time I’ve ever run any
openssl commands. I run the command to add a cert, and it has no output. That’s a good thing, right? I successfully just trusted a new OpenSSL certificate, so I can scrape that insecure website now, right?
The certificate wasn’t added. It returned a non-zero status code of 255, but I’d never know that, because my shell prompt didn’t let me know that. And I’d go on trying to debug
openssl further because I didn’t see any error output!
Well, then I saw the light, and I let the emojis guide my
Here is what our
PS1 looks like at on my workstation (the idea was actually complements of indirect, so thank you, André)
We show a happy, healthy, loving heart for anything that exits with a status code of zero. We show a broken, horribly pained heart for anything that exits non-zero (see the grep command).
Now, keep in mind we have a two-line prompt, and we use bash-it with our shell prompt. The two-line prompt is because emojis do not have monospaced compatible fonts. An emoji sometimes will take the width of two characters, sometimes one, and anywhere in between. So it will inevitably look like shit.
So, when you’re having fun with emojis in your shell prompts make sure you do so responsibly. Put it on another line than the one you type.
Here’s a link to our bash-it theme, if you wanna use it. Enjoy!