Several years ago, while being logged into and working on several remote Linux servers simultaneously, I rebooted the wrong one. I realized it approximately .002 milliseconds after pressing (after "shutdown -r now") but it was too late. Since then, I use one style of prompt on my personal machines and other non-critical hosts. On production/critical machines, I use a different style of prompt that stands out quite a…
in Your System Prompt
11–18 of 18 posts
Re: in Your System Prompt
#12Re: in Your System Prompt
#13Re: in Your System Prompt
#14Yes, and you can have “💩” in your prompt. Wait, you won't believe it, but you can even have “$” in your prompt! It is worth a blog post (in first page of HN)?
Re: in Your System Prompt
#15Yes, and you can have “💩” in your prompt. Wait, you won't believe it, but you can even have “$” in your prompt! It is worth a blog post (in first page of HN)?
Apple's fucking emoticons. I had to jailbreak and install a whitelist specifically because of the emoticon SMS spam.
Re: in Your System Prompt
#16Earlier quoted context omitted.
Apple's fucking emoticons. I had to jailbreak and install a whitelist specifically because of the emoticon SMS spam.
They've been in Unicode since 6.0. And they are not much Apple's in the first place.
Re: in Your System Prompt
#17http://notes.torrez.org/2013/04/put-a-burger-in-your-shell.h...
Re: in Your System Prompt
#18You can also tell iTerm to report its terminal type as something specific, then do something like this in your bashrc to setup a different prompt if you're not on OSX:
if [ $TERM = "xterm-256color" ]; then