There's a command-line tool named `unicode` that I use for that. It's in Debian; don't know offhand what/if the upstream is.
It's both sad and hilarious that the easiest way for me to answer "wtf is that unicode character" is to put it in a @rustlang file and read the compiler error
-
-
-
Ah yes, I found the upstream alias unicode = echo "fn main() { let $* = (); }" > /tmp/foo.rs && rustc /tmp/foo.rs
- 1 more reply
New conversation -
-
-
Sounds like you don't have unic-cli installed. Try: $ cargo install unic-cli And then: $ unic-inspect <paste-your-chars>
-
Y'all keep replying with CLI tools thinking I have the ability to remember one of these better than "I can go to the Rust Playground and answer this"
End of conversation
New conversation -
-
-
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
For more info (but with slightly more delay), teeweet it to
@ManishEarth -
(Yes I saw the typo but it sounded funny and I wanted to keep it)
End of conversation
New conversation -
-
-
http://codepoints.net/
has been my go-to for some time. Best part is it displays low-level Unicode code point characteristics. Unfortunately it only knows Unicode 8.0, so anything newish like https://codepoints.net/ 
doesn't work. I dunno if that'll be fixed. @CodepointsNet -
Bah, mangled URL. Trying again: https://codepoints.net/
Basically tack any code point as the path component of the URL after the slash and you get a data page on that code point. The https://codepoints.net/U+01F94F flavor works too. - 4 more replies
New conversation -
-
-
Not M-x describe-char?
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.