term-ng - npm Package Compare versions

Comparing version 0.1.0-beta.0 to 0.1.0-beta.1

index.js

@@ -31,3 +31,3 @@ 'use strict';
   if (!(/\-color/.test(process.argv.join('')))) {
-    process.argv.push('--color=16m');
+    process.argv.unshift('--color=16m');
   }
@@ -34,0 +34,0 @@ }

package.json

 {
   "name": "term-ng",
-  "version": "0.1.0-beta.0",
-  "description": "Terminal feature snooping and whitelisting",
+  "version": "0.1.0-beta.1",
+  "description": "Terminal/$TERM feature snooping and whitelisting",
   "main": "index.js",
@@ -29,2 +29,3 @@ "scripts": {
   "devDependencies": {
+    "coffee-script": "^1.10.0",
     "gulp": "^3.9.0",
@@ -31,0 +32,0 @@ "gulp-coffee": "^2.3.1",

readme.md

@@ -0,10 +1,44 @@
+[project-badge]: http://img.shields.io/badge/status-alpha-red.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  
-![Project status](http://img.shields.io/badge/status-alpha-red.svg?style=flat) [![Build Status](http://img.shields.io/travis/MarkGriffiths/term-ng.svg?style=flat)](https://travis-ci.org/MarkGriffiths/term-ng) [![Dependency Status](http://img.shields.io/david/MarkGriffiths/term-ng.svg?style=flat)](https://david-dm.org/MarkGriffiths/term-ng) [![devDependency Status](http://img.shields.io/david/dev/MarkGriffiths/term-ng.svg?style=flat)](https://david-dm.org/MarkGriffiths/term-ng#info=devDependencies)
+Enables enhanced node.js/fish-shell/XTerm/iTerm3 feature integration.
 
-Terminal feature snooping and whitelisting
+![Project status][project-badge]
+[![Build Status][build-badge]][travis]
+[![Dependency Status][david-badge]][david]
+[![devDependency Status][david-dev-badge]][david-dev]
+[![npm Status][npm-badge]][npm]
 
-Provides enhanced node.js/fish-shell/iTerm3 integration.
+-	Senses 24bit colour (truecolor) when `$TERM_COLOR=16m` environment variable is set.
+-	Adds `--color=16m` to front of process.argv before wrapping the `supports-color`.
+-	Indicate enhanced media support by setting:
+	+	`$TERM_IMAGES=enabled` : Allow rendering of inline images using OSC sequences.
+	+	`$TERM_AUDIO=enabled` : Allow enhanced audio.
+-	Sense $TERM suffixes to indicate enhanced termcap capabilities.
 
-- Senses enabled 24bit colour (truecolor).
-- Adds support for inline images and audio via enhanced termcap info.
-- Very basic at the moment.
+In some of my 'private' admin/control systems I use a customised terminfo database that wraps some fo the (very useful) enhanced OSC abilities of more recent iTerm builds into new commands available via `tput` (which I further wrap in fish functions).
+
+The `terminfo` directory above contains `iTerm.ti`. Using `/usr/bin/tic` and ncurses' terminfo database (available from [invisible-island.net](http://invisible-island.net/ncurses/ncurses.html#downloads)), I build a new terminal type `xterm-256color+iterm3`, and change the Terminal type preference in iTerm to the same, setting the $TERM environment variable.
+
+The new terminfo entries are built thusly...
+
+```sh
+cd term-ng/terminfo
+curl http://invisible-island.net/datafiles/current/terminfo.src.gz
+gunzip terminfo.src.gz
+tic -xrs -e xterm-256color terminfo.src
+tic -xsv3 iTerm.ti
+```
+
+This create a new, updated xterm-256color and then extends it for iTerm. this is non-destructive as it creates new entries at ` ~/.terminfo/`. Simply delete this directory to return the terminfo databases back to the original OS provided state.
+
+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.

New alerts

License Policy Violation

License

This package is not allowed per your license policy. Review the package's license to ensure compliance.

Found 1 instance in 1 package

No website

Quality

Package does not have a website.

Found 1 instance in 1 package

Fixed alerts

License Policy Violation

License

This package is not allowed per your license policy. Review the package's license to ensure compliance.

Found 1 instance in 1 package

Improved metrics

Total package byte prevSize

6614

increased by42.05%

Number of downloads

142

increased by545.45%

Number of lines in readme file

45

increased by309.09%

Worsened metrics

Dev dependency count

5

increased by25%

Number of low quality alerts

2

increased by100%

No dependency changes