Comparing version 0.2.6 to 0.3.0-beta.0
@@ -31,3 +31,3 @@ 'use strict'; | ||
if (!(/\-color/.test(process.argv.join('')))) { | ||
process.argv.splice(3, 0, '--color=16m'); | ||
process.argv.splice(2, 0, '--color=16m'); | ||
} | ||
@@ -34,0 +34,0 @@ } |
{ | ||
"name": "term-ng", | ||
"version": "0.2.6", | ||
"version": "0.3.0-beta.0", | ||
"description": "Terminal/$TERM feature snooping and whitelisting", | ||
"main": "index.js", | ||
"scripts": { | ||
"test": "gulp test" | ||
"test": "gulp test", | ||
"colors": "scripts/colortest.pl" | ||
}, | ||
@@ -29,9 +30,3 @@ "repository": { | ||
"devDependencies": { | ||
"coffee-script": "^1.10.0", | ||
"gulp": "^3.9.0", | ||
"gulp-coffee": "^2.3.1", | ||
"gulp-git": "^1.6.1", | ||
"gulp-util": "^3.0.7", | ||
"guppy-post-checkout": "^0.2.1", | ||
"semver-regex": "^1.0.0" | ||
"@thebespokepixel/cordial": "^0.2.1" | ||
}, | ||
@@ -41,3 +36,4 @@ "dependencies": { | ||
"supports-color": "^3.1.2" | ||
} | ||
}, | ||
"build_number": 0 | ||
} |
@@ -1,12 +0,1 @@ | ||
[project-badge]: http://img.shields.io/badge/status-beta-blue.svg?style=flat | ||
[build-badge]: http://img.shields.io/travis/MarkGriffiths/term-ng.svg?branch=master&style=flat | ||
[david-badge]: http://img.shields.io/david/MarkGriffiths/term-ng.svg?style=flat | ||
[david-dev-badge]: http://img.shields.io/david/dev/MarkGriffiths/term-ng.svg?style=flat | ||
[npm-badge]: https://img.shields.io/npm/v/term-ng.svg?style=flat | ||
[travis]: https://travis-ci.org/MarkGriffiths/term-ng | ||
[david]: https://david-dm.org/MarkGriffiths/term-ng | ||
[david-dev]: https://david-dm.org/MarkGriffiths/term-ng#info=devDependencies | ||
[npm]: https://www.npmjs.com/package/term-ng | ||
# term-ng | ||
@@ -57,1 +46,19 @@ Enables enhanced node.js/fish-shell/XTerm/iTerm3 feature integration. | ||
A word of caution... while this has worked very well for me, I have found that some things complain about an unrecognized term type - Homebrew is notable here. A simple workaround is to have a standard `xterm-256color` profile defined to use when brewing. | ||
### Terminal Color Test | ||
From inside the package directory, running `npm run-script colors` will generate a preview of the entire color gamut your terminal is capable of. Output of a recent iTerm beta shown below: | ||
![Color preview][colors] | ||
[project-badge]: http://img.shields.io/badge/status-beta-blue.svg?style=flat | ||
[build-badge]: http://img.shields.io/travis/MarkGriffiths/term-ng.svg?branch=master&style=flat | ||
[david-badge]: http://img.shields.io/david/MarkGriffiths/term-ng.svg?style=flat | ||
[david-dev-badge]: http://img.shields.io/david/dev/MarkGriffiths/term-ng.svg?style=flat | ||
[npm-badge]: https://img.shields.io/npm/v/term-ng.svg?style=flat | ||
[colors]: http://markgriffiths.github.io/projects/term-ng/colors.png | ||
[travis]: https://travis-ci.org/MarkGriffiths/term-ng | ||
[david]: https://david-dm.org/MarkGriffiths/term-ng | ||
[david-dev]: https://david-dm.org/MarkGriffiths/term-ng#info=devDependencies | ||
[npm]: https://www.npmjs.com/package/term-ng |
15262
1
5
64