ahmadawais / hyperterm-cobalt3-theme

Cobalt3 for Hyperterm

Cobalt3 for Hyperterm Cobalt3 theme for Hyperterm — purple colored fork of Cobalt2.
A FOSS (Free & Open Source Software) project. Maintained by @AhmadAwais.

Cobalt3 for Hyperterm

This is a purple color fork of Cobalt2 hyperterm theme by my friend Wes Bos.

Installing

1. Open your ~/.hyperterm.js config file with something like subl ~/.hyperterm.js or vim ~/.hyperterm.js.

2. Add hyperterm-cobalt3-theme to your plugins array. Kinda like this:

   plugins: [
     'hyperterm-cobalt3-theme'
   ],

3. Enjoy your life

OPTOIONAL: If you have HPM installed then all you have to do is run hpm install hyperterm-cobalt3-theme

FAQ

Q: What font is that? I Love It!

A: Operator Mono. I wrote a bit of info here → http://wesbos.com/uses

Q: How do I get Powerline working with a non-patched font?

A: Use CSS to fall back to a different font when the character isn't supported:

fontFamily: '"Operator Mono", "Inconsolata for Powerline", monospace'

Q: I HATE THAT FONT SO MUCH, I HATE YOU AND I WANT YOU TO KNOW IT

A: k 😘

Q: How did you get the cool prompt?

A: This isn't part of iTerm or Hyperterm, it has to do with the shell that you are using. I'm using ZSH along with Cobalt 2 for ZSH. I've got a whole free video series on this if you are interested: http://CommandLinePowerUser.com

Q: Can I make edits?

A: Yes please! Still working on this. I might not accept your edits, but I probably will.

You might also like

🔥 Cobalt3 for iTerm

🔥 Cobalt2 for Sublime Text

🔥 Cobalt2 for Atom

🔥 Cobalt 2 for ZSH

🔥 Cobalt 2 for iTerm

🔥 Cobalt 2 for Alfred

🔥 Cobalt 2 for Slack

---

🙌 WPCOUPLE PARTNERS:

This open source project is maintained by the help of awesome businesses listed below. What? Read more about it →

hyperterm-cobalt3-theme's Issues

Action required: Greenkeeper could not be activated 🚨

🚨 You need to enable Continuous Integration on all branches of this repository. 🚨

To enable Greenkeeper, you need to make sure that a commit status is reported on all branches. This is required by Greenkeeper because it uses your CI build statuses to figure out when to notify you about breaking changes.

Since we didn’t receive a CI status on the greenkeeper/initial branch, it’s possible that you don’t have CI set up yet. We recommend using Travis CI, but Greenkeeper will work with every other CI service as well.

If you have already set up a CI for this repository, you might need to check how it’s configured. Make sure it is set to run on all new branches. If you don’t want it to run on absolutely every branch, you can whitelist branches starting with greenkeeper/.

Once you have installed and configured CI on this repository correctly, you’ll need to re-trigger Greenkeeper’s initial pull request. To do this, please delete the greenkeeper/initial branch in this repository, and then remove and re-add this repository to the Greenkeeper App’s white list on Github. You'll find this list on your repo or organization’s settings page, under Installed GitHub Apps.