Skip to content

Commit 8eae75b

Browse files
author
Matt Parrish
committed
Initial commit
0 parents  commit 8eae75b

File tree

12 files changed

+12076
-0
lines changed

12 files changed

+12076
-0
lines changed

‎.eslintcache‎

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1 @@
1+
{"/Users/matt.parrish/code/hyper-night-owl/index.js":{"size":4378,"mtime":1526762753530,"hashOfConfig":"1osjhwg","results":{"filePath":"/Users/matt.parrish/code/hyper-night-owl/index.js","messages":[],"errorCount":0,"warningCount":0,"fixableErrorCount":0,"fixableWarningCount":0}}}

‎.eslintignore‎

Whitespace-only changes.

‎.gitignore‎

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1 @@
1+
node_modules

‎.travis.yml‎

Lines changed: 13 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,13 @@
1+
sudo: false
2+
language: node_js
3+
cache:
4+
directories:
5+
- ~/.npm
6+
notifications:
7+
email: false
8+
node_js: '8'
9+
install: npm install
10+
script: npm run validate
11+
after_success: kcd-scripts travis-after-success
12+
branches:
13+
only: master

‎README.md‎

Lines changed: 56 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,56 @@
1+
<div align="center">
2+
<h1>hyper-night-owl</h1>
3+
4+
<a href="https://www.emojione.com/emoji/1f989">
5+
<img height="64" width="64" alt="owl" src="https://raw.githubusercontent.com/pbomb/hyper-night-owl/master/other/owl.png" />
6+
</a>
7+
</div>
8+
9+
hyper-night-owl is a beautiful theme for the Hyper terminal based on the [Night Owl VS Code dark theme](https://github.com/sdras/night-owl-vscode-theme), which is optimized for working at night, accessibility, and colorblindness.
10+
11+
This code for this theme is based on the [Verminal Hyper terminal theme](https://github.com/defringe/verminal).
12+
13+
<hr />
14+
15+
## INTRODUCTION
16+
17+
[![version][version-badge]][package]
18+
[![downloads][downloads-badge]][npmtrends]
19+
[![MIT License][license-badge]][license]
20+
21+
[![PRs Welcome][prs-badge]][prs]
22+
[![Code of Conduct][coc-badge]][coc]
23+
24+
## 🛠 Install
25+
26+
Installing the hyper-night-owl theme for your Hyper terminal couldn't be easier.
27+
28+
###### Hyper's built-in CLI (hyper)
29+
30+
1. `hyper i hyper-night-owl`
31+
1. Enjoy hyper-night-owl.
32+
33+
###### Manually
34+
35+
1. Open `~/.hyper.js` in your favorite editor.
36+
1. Add `hyper-night-owl` to the `plugins` array.
37+
1. Enjoy hyper-night-owl.
38+
39+
## ⚡️ Contribute
40+
41+
If you would like to help improve this themes, you're more than welcome to contribute.
42+
43+
1. [Fork](https://help.github.com/articles/fork-a-repo/) this repository to your own GitHub account.
44+
2. [Clone](https://help.github.com/articles/cloning-a-repository/) to your local device: `git clone git@github.com:<your_github_username>/hyper-night-owl.git`
45+
3. Run the setup script: `npm run setup`
46+
47+
[license-badge]: https://img.shields.io/npm/l/hyper-night-owl.svg?style=flat-square
48+
[license]: https://github.com/pbomb/hyper-night-owl/blob/master/LICENSE
49+
[version-badge]: https://img.shields.io/npm/v/hyper-night-owl.svg?style=flat-square
50+
[package]: https://www.npmjs.com/package/hyper-night-owl
51+
[downloads-badge]: https://img.shields.io/npm/dw/hyper-night-owl.svg?style=flat-square
52+
[npmtrends]: http://www.npmtrends.com/hyper-night-owl
53+
[prs-badge]: https://img.shields.io/badge/PRs-welcome-brightgreen.svg?style=flat-square
54+
[prs]: http://makeapullrequest.com
55+
[coc-badge]: https://img.shields.io/badge/code%20of-conduct-ff69b4.svg?style=flat-square
56+
[coc]: https://github.com/pbomb/hyper-night-owl/blob/master/other/CODE_OF_CONDUCT.md

‎index.js‎

Lines changed: 137 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,137 @@
1+
module.exports.onWindow = browserWindow =>
2+
browserWindow.setVibrancy("ultra-dark");
3+
4+
const backgroundColor = "rgba(0, 0, 0, .65)";
5+
const overlap = "rgba(0, 0, 0, .15)";
6+
7+
const colors = {
8+
"editorCursor.foreground": "#7e57c2",
9+
"tab.activeBackground": "#0b2942",
10+
"tab.activeForeground": "#d2dee7",
11+
"tab.border": "#272B3B",
12+
"tab.activeBorder": "#262A39",
13+
"tab.inactiveBackground": "#010e1a",
14+
"tab.inactiveForeground": "#5f7e97",
15+
"terminal.ansiWhite": "#ffffff",
16+
"terminal.ansiBlack": "#011627",
17+
"terminal.ansiBlue": "#82AAFF",
18+
"terminal.ansiCyan": "#7fdbca",
19+
"terminal.ansiGreen": "#ba67db",
20+
"terminal.ansiMagenta": "#C792EA",
21+
"terminal.ansi#5f7e97": "#7fdbca",
22+
"terminal.ansiYellow": "#addb67",
23+
"terminal.ansiBrightWhite": "#ffffff",
24+
"terminal.ansiBrightBlack": "#575656",
25+
"terminal.ansiBrightBlue": "#82AAFF",
26+
"terminal.ansiBrightCyan": "#7fdbca",
27+
"terminal.ansiBrightGreen": "#addb67",
28+
"terminal.ansiBrightMagenta": "#C792EA",
29+
"terminal.ansiBright#5f7e97": "#7fdbca",
30+
"terminal.ansiBrightYellow": "#addb67"
31+
};
32+
33+
exports.decorateConfig = config =>
34+
Object.assign({}, config, {
35+
backgroundColor,
36+
foregroundColor: colors["terminal.ansiWhite"],
37+
borderColor: overlap,
38+
cursorColor: colors["editorCursor.foreground"],
39+
colors: {
40+
black: colors["terminal.ansiBlack"],
41+
red: colors["terminal.ansiMagenta"],
42+
green: colors["terminal.ansiGreen"],
43+
yellow: colors["terminal.ansiYellow"],
44+
blue: colors["terminal.ansiBlue"],
45+
magenta: colors["terminal.ansiMagenta"],
46+
cyan: colors["terminal.ansiCyan"],
47+
white: colors["terminal.ansiBrightWhite"],
48+
lightBlack: colors["terminal.ansiBrightBlack"],
49+
lightRed: colors["terminal.ansiBrightMagenta"],
50+
lightGreen: colors["terminal.ansiBrightGreen"],
51+
lightYellow: colors["terminal.ansiBrightYellow"],
52+
lightBlue: colors["terminal.ansiBrightBlue"],
53+
lightMagenta: colors["terminal.ansiBrightMagenta"],
54+
lightCyan: colors["terminal.ansiBrightCyan"],
55+
lightWhite: colors["terminal.ansiBrightWhite"]
56+
},
57+
css: `
58+
${config.css}
59+
.hyper_main {
60+
border: none !important;
61+
}
62+
.header_header {
63+
background-color: ${overlap} !important;
64+
}
65+
.tabs_borderShim {
66+
border-color: transparent !important;
67+
}
68+
.tab_tab {
69+
border: 0;
70+
background-color: ${colors["tab.inactiveBackground"]};
71+
color: ${colors["tab.inactiveForeground"]};
72+
}
73+
.tab_tab::before {
74+
background-color: ${colors["tab.border"]};
75+
}
76+
.tab_active {
77+
background-color: ${colors["tab.activeBackground"]};
78+
color: ${colors["tab.activeForeground"]};
79+
}
80+
.tab_active::before {
81+
background-color: ${colors["tab.activeBorder"]};
82+
}
83+
.tab_text {
84+
background-color: ${colors["tab.inactiveBackground"]};
85+
color: ${colors["tab.inactiveForeground"]};
86+
}
87+
.tab_textActive {
88+
background-color: ${colors["tab.activeBackground"]};
89+
color: ${colors["tab.activeForeground"]};
90+
}
91+
.hyper-search-wrapper {
92+
border: 0 !important;
93+
padding: 0 !important;
94+
background-color: transparent !important;
95+
display: flex;
96+
opacity: 0.8 !important;
97+
}
98+
.hyper-search-wrapper button {
99+
top: 0 !important;
100+
opacity: 0.8 !important;
101+
padding: 0 6px;
102+
cursor: pointer;
103+
}
104+
.hyper-search-wrapper button:hover {
105+
opacity: 1.0 !important;
106+
}
107+
.hyper-search-wrapper button:nth-of-type(1) {
108+
border-radius: 4px 0 0 4px !important;
109+
border-right: 1px solid ${colors["terminal.ansiBrightBlack"]} !important;
110+
}
111+
.hyper-search-wrapper button:nth-of-type(2) {
112+
border-radius: 0 4px 4px 0 !important;
113+
}
114+
.hyper-search-wrapper:before {
115+
width: 20px;
116+
color: #000;
117+
position: absolute;
118+
content: "🔍";
119+
font-size: 10px;
120+
margin: 7px;
121+
z-index: 999;
122+
}
123+
#hyper-search-input {
124+
background-color: ${colors["terminal.ansiWhite"]} !important;
125+
border-radius: 4px;
126+
box-shadow: 0 1px 10px rgba(0, 0, 0, 0.5);
127+
padding: 3px 6px 3px 24px !important;
128+
color: ${colors["terminal.ansiBlack"]} !important;
129+
opacity: 0.9 !important;
130+
margin-right: 2px;
131+
}
132+
#hyper-search-input:focus {
133+
opacity: 1.0 !important;
134+
box-shadow: 0 1px 10px rgba(0, 0, 0, 1.0);
135+
}
136+
`
137+
});

‎license‎

Lines changed: 9 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,9 @@
1+
MIT License
2+
3+
Copyright (c) Matt Parrish <matt.r.parrish@gmail.com>
4+
5+
Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:
6+
7+
The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.
8+
9+
THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.

‎other/CODE_OF_CONDUCT.md‎

Lines changed: 74 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,74 @@
1+
# Contributor Covenant Code of Conduct
2+
3+
## Our Pledge
4+
5+
In the interest of fostering an open and welcoming environment, we as
6+
contributors and maintainers pledge to making participation in our project and
7+
our community a harassment-free experience for everyone, regardless of age, body
8+
size, disability, ethnicity, gender identity and expression, level of experience,
9+
nationality, personal appearance, race, religion, or sexual identity and
10+
orientation.
11+
12+
## Our Standards
13+
14+
Examples of behavior that contributes to creating a positive environment
15+
include:
16+
17+
* Using welcoming and inclusive language
18+
* Being respectful of differing viewpoints and experiences
19+
* Gracefully accepting constructive criticism
20+
* Focusing on what is best for the community
21+
* Showing empathy towards other community members
22+
23+
Examples of unacceptable behavior by participants include:
24+
25+
* The use of sexualized language or imagery and unwelcome sexual attention or
26+
advances
27+
* Trolling, insulting/derogatory comments, and personal or political attacks
28+
* Public or private harassment
29+
* Publishing others' private information, such as a physical or electronic
30+
address, without explicit permission
31+
* Other conduct which could reasonably be considered inappropriate in a
32+
professional setting
33+
34+
## Our Responsibilities
35+
36+
Project maintainers are responsible for clarifying the standards of acceptable
37+
behavior and are expected to take appropriate and fair corrective action in
38+
response to any instances of unacceptable behavior.
39+
40+
Project maintainers have the right and responsibility to remove, edit, or
41+
reject comments, commits, code, wiki edits, issues, and other contributions
42+
that are not aligned to this Code of Conduct, or to ban temporarily or
43+
permanently any contributor for other behaviors that they deem inappropriate,
44+
threatening, offensive, or harmful.
45+
46+
## Scope
47+
48+
This Code of Conduct applies both within project spaces and in public spaces
49+
when an individual is representing the project or its community. Examples of
50+
representing a project or community include using an official project e-mail
51+
address, posting via an official social media account, or acting as an appointed
52+
representative at an online or offline event. Representation of a project may be
53+
further defined and clarified by project maintainers.
54+
55+
## Enforcement
56+
57+
Instances of abusive, harassing, or otherwise unacceptable behavior may be
58+
reported by contacting the project team at kent+coc@doddsfamily.us. All
59+
complaints will be reviewed and investigated and will result in a response that
60+
is deemed necessary and appropriate to the circumstances. The project team is
61+
obligated to maintain confidentiality with regard to the reporter of an incident.
62+
Further details of specific enforcement policies may be posted separately.
63+
64+
Project maintainers who do not follow or enforce the Code of Conduct in good
65+
faith may face temporary or permanent repercussions as determined by other
66+
members of the project's leadership.
67+
68+
## Attribution
69+
70+
This Code of Conduct is adapted from the [Contributor Covenant][homepage], version 1.4,
71+
available at [http://contributor-covenant.org/version/1/4][version]
72+
73+
[homepage]: http://contributor-covenant.org
74+
[version]: http://contributor-covenant.org/version/1/4/

‎other/MAINTAINERS.md‎

Lines changed: 63 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,63 @@
1+
# Maintaining
2+
3+
This is documentation for maintainers of this project.
4+
5+
## Code of Conduct
6+
7+
Please review, understand, and be an example of it. Violations of the code of conduct are
8+
taken seriously, even (especially) for maintainers.
9+
10+
## Issues
11+
12+
We want to support and build the community. We do that best by helping people learn to solve
13+
their own problems. We have an issue template and hopefully most folks follow it. If it's
14+
not clear what the issue is, invite them to create a minimal reproduction of what they're trying
15+
to accomplish or the bug they think they've found.
16+
17+
Once it's determined that a code change is necessary, point people to
18+
[makeapullrequest.com](http://makeapullrequest.com) and invite them to make a pull request.
19+
If they're the one who needs the feature, they're the one who can build it. If they need
20+
some hand holding and you have time to lend a hand, please do so. It's an investment into
21+
another human being, and an investment into a potential maintainer.
22+
23+
Remember that this is open source, so the code is not yours, it's ours. If someone needs a change
24+
in the codebase, you don't have to make it happen yourself. Commit as much time to the project
25+
as you want/need to. Nobody can ask any more of you than that.
26+
27+
## Pull Requests
28+
29+
As a maintainer, you're fine to make your branches on the main repo or on your own fork. Either
30+
way is fine.
31+
32+
When we receive a pull request, a travis build is kicked off automatically (see the `.travis.yml`
33+
for what runs in the travis build). We avoid merging anything that breaks the travis build.
34+
35+
Please review PRs and focus on the code rather than the individual. You never know when this is
36+
someone's first ever PR and we want their experience to be as positive as possible, so be
37+
uplifting and constructive.
38+
39+
When you merge the pull request, 99% of the time you should use the
40+
[Squash and merge](https://help.github.com/articles/merging-a-pull-request/) feature. This keeps
41+
our git history clean, but more importantly, this allows us to make any necessary changes to the
42+
commit message so we release what we want to release. See the next section on Releases for more
43+
about that.
44+
45+
## Release
46+
47+
Our releases are automatic. They happen whenever code lands into `master`. A travis build gets
48+
kicked off and if it's successful, a tool called
49+
[`semantic-release`](https://github.com/semantic-release/semantic-release) is used to
50+
automatically publish a new release to npm as well as a changelog to GitHub. It is only able to
51+
determine the version and whether a release is necessary by the git commit messages. With this
52+
in mind, **please brush up on [the commit message convention][commit] which drives our releases.**
53+
54+
> One important note about this: Please make sure that commit messages do NOT contain the words
55+
> "BREAKING CHANGE" in them unless we want to push a major version. I've been burned by this
56+
> more than once where someone will include "BREAKING CHANGE: None" and it will end up releasing
57+
> a new major version. Not a huge deal honestly, but kind of annoying...
58+
59+
## Thanks!
60+
61+
Thank you so much for helping to maintain this project!
62+
63+
[commit]: https://github.com/conventional-changelog-archived-repos/conventional-changelog-angular/blob/ed32559941719a130bb0327f886d6a32a8cbc2ba/convention.md

‎other/owl.png‎

4.12 KB
Loading

0 commit comments

Comments
 (0)