X-Git-Url: https://code.delx.au/gnu-emacs-elpa/blobdiff_plain/1ceb4600f0eda8d5b85076abe22ebb31d4eb6d2a..f0b45f4a010d8e5680f66c9a22f433386d023466:/README.md diff --git a/README.md b/README.md index 4a380be23..21f1eb5cf 100644 --- a/README.md +++ b/README.md @@ -1,102 +1,66 @@ -# Context Coloring +# Context Coloring [![Build Status](https://travis-ci.org/jacksonrayhamilton/context-coloring.png?branch=master)](https://travis-ci.org/jacksonrayhamilton/context-coloring) [![Coverage Status](https://coveralls.io/repos/jacksonrayhamilton/context-coloring/badge.svg?branch=master)](https://coveralls.io/r/jacksonrayhamilton/context-coloring?branch=master)

Screenshot of JavaScript code highlighted by context.

-Highlights code according to function context. +Highlights code by scope. Top-level scopes are one color, second-level scopes +are another color, and so on. Variables retain the color of the scope in which +they are defined. A variable defined in an outer scope referenced by an inner +scope is colored the same as the outer scope. -- Code in the global scope is one color. Code in functions within the global - scope is a different color, and code within such functions is another color, - and so on. -- Identifiers retain the color of the scope in which they were declared. -- Comments are gray. - -Lexical scope information at-a-glance can assist a programmer in understanding -the overall structure of a program. It can also help curb nasty bugs like name -shadowing or unexpected assignment. A rainbow can indicate excessive -complexity. A spot of contrast followed by an assignment expression could be a -side-effect... or, the state of a closure could be undergoing change. - -This coloring strategy is probably more useful than conventional *syntax* -highlighting. Highlighting keywords can help one to detect spelling errors, and -highlighting the content between quotation marks can alert one to unclosed -string literals. But a [linter][] could also spot those errors, and if -[integrated via flycheck][integration], an extra spot opens up in your editing -toolbelt. - -Give context coloring a try; you may find that it *changes the way you write -code*. +By default, comments and strings are still highlighted syntactically. ## Features -- Supported languages: JavaScript -- Light and dark (customizable) color schemes. -- Fast async AST parsing. Some total parse + recolor times: - - jQuery (9191 lines): 0.63 seconds - - Lodash (6786 lines): 0.37 seconds - - Async (1124 lines): 0.17 seconds - - mkdirp (98 lines): 0.09 seconds - -## Extending +- Light and dark customizable color schemes. +- JavaScript support: + - Script, function and block scopes (and even `catch` block scopes). + - Node.js "file-level" scope detection. +- Emacs Lisp support: + - `defun`, `lambda`, `let`, `let*`, `cond`, `condition-case`, `defadvice`, + `dolist`, `quote`, `backquote` and backquote splicing. + - Works in `eval-expression` too. -It would be great if this package supported more languages. I welcome any pull -request that adds new language support. +## Installation -Extension is relatively straightforward. Write a "scopifier" for the language of -your choice, add an entry to `context-coloring-scopifier-plist`, and the plugin -should handle the rest. +Requires Emacs 24.3+. JavaScript language support requires +[js2-mode](https://github.com/mooz/js2-mode). -A "scopifier" is a CLI program that reads a buffer's contents from stdin, and -then writes a JSON array of integers to stdout. Every three numbers in the array -represent a range of color. For instance, if I fed the following string of -JavaScript code to a scopifier, +To install, run the command `M-x package-install RET context-coloring RET`, and +then add the following to your init file: -```js -var a = function () {}; -``` +```lisp +;; JavaScript: +(add-to-list 'auto-mode-alist '("\\.js\\'" . js2-mode)) +(add-hook 'js2-mode-hook #'context-coloring-mode) -then the scopifier would produce the following array: +;; Emacs Lisp: +(add-hook 'emacs-lisp-mode-hook #'context-coloring-mode) -```js -[ - 1, 24, 0, - 9, 23, 1 -] +;; eval-expression: +(add-hook 'eval-expression-minibuffer-setup-hook #'context-coloring-mode) ; 24.4+ +(add-hook 'minibuffer-setup-hook #'context-coloring-mode) ; 24.3 ``` -Where, for every three numbers, the first number is a 1-indexed start [point][], -the second number is an exclusive end point, and the third number is a scope -level. The result of applying level 0 coloring to the range -\[1, 24) and then applying level 1 coloring to the range \[9, 23) would result in the following coloring: +## Color Schemes -

- Screenshot of ranges [1, 24) and [9, 23). -

+The [Zenburn](https://github.com/bbatsov/zenburn-emacs) theme, featured in the +screenshot above, now supports context coloring. -## Usage +You can define your own colors by customizing faces like +`context-coloring-level-N-face`, where N is a number starting from 0. -Requires Emacs 24+. +[See here](https://gist.github.com/jacksonrayhamilton/6b89ca3b85182c490816) for +some color schemes for popular custom themes. -JavaScript language support requires [Node.js 0.10+][node]. - -- Clone this repository. - -```bash -cd ~/.emacs.d/ -git clone https://github.com/jacksonrayhamilton/context-coloring.git -``` - -- Add the following to your `~/.emacs` file: - -```lisp -(add-to-list 'load-path "~/.emacs.d/context-coloring") -(require 'context-coloring) -(add-hook 'js-mode-hook 'context-coloring-mode) -``` +## Options -[linter]: https://github.com/jacksonrayhamilton/jslinted -[integration]: https://github.com/jacksonrayhamilton/jslinted#emacs-integration -[point]: http://www.gnu.org/software/emacs/manual/html_node/elisp/Point.html -[node]: http://nodejs.org/download/ -[load path]: https://www.gnu.org/software/emacs/manual/html_node/emacs/Lisp-Libraries.html +- `context-coloring-syntactic-comments` (default: `t`): If non-nil, also color + comments using `font-lock`. +- `context-coloring-syntactic-strings` (default: `t`): If non-nil, also color + strings using `font-lock`. +- `context-coloring-javascript-block-scopes` (default: `nil`): If non-nil, also + color block scopes in the scope hierarchy in JavaScript. +- `context-coloring-javascript-detect-top-level-scope` (default: `t`): If + non-nil, detect when to use file-level scope.