Skip to content

Latest commit

 

History

History
80 lines (50 loc) · 2.56 KB

README.md

File metadata and controls

80 lines (50 loc) · 2.56 KB
Raw

Emo

npm version

Convert human unfriendly strings to emoji in your terminal

What? Why?

There are a lot of human unfriendly strings out there, for instance, UUIDs and SHA1s.

When you have to work with a couple of these strings, it's manageable; most programmers I know see f985dab7704a and remember that as "the one that starts with f9." And tab completion helps.

But when you start to have tens or hundreds of these strings, it starts to get messy, and we lose the ability to quickly look at some output and see what node/commit/container/image is being referenced.

Installation

emo requires nodejs. Once you've installed node (which now comes bundled with npm) you can install emo by running

npm install -g emo2

Usage

You can pipe stdout to emo, and emo will replace human unfriendly strings with emoji, and store that data to ~/.emo.

git log | emo
docker ps | emo

Then you can look stuff up in either direction, like so:

emo f985dab7704a
emo 🐤
docker kill $(emo 👾)

gif

Options

When piping, you can add -s to have emo add spacing equivalent to the length of the string being replaced.

gitlg | emo -s

When you see an emoji and want to know what the hell it's called, you can get node-emoji's name for it with the -i option

emo 📠 -i

There's also a sample mode, which just returns random emoji, which you can "use" like so:

emo sample 10

Caveats

  • Unique to you, each emoji is assigned randomly. It'd be cool if they were computed/encoded from the string, but I couldn't figure out a good way to do that without needing to make the replacement many emoji long.
  • Some emoji look very similar
  • My regex for detecting "human unfriendly strings" leaves a lot to be desired
  • You probably shouldn't use this for anything serious, though I'm having a hard time thinking how one even would
  • Only tested on a Mac