Releases: jacksonrayhamilton/context-coloring
Releases · jacksonrayhamilton/context-coloring
v8.1.0
- Add
context-coloring-after-colorize-hookfor executing code after coloring. - Add
context-coloring-after-colorizefor asynchronous colorizers (now
recognized by:async-p tin a dispatch plist) to call after they finish
coloring. - Add support for Prettify Symbols Mode and potentially other Font Lock modes.
- Fix bug where enabling Context Coloring Mode after calling
narrow-to-region
in JS2 Mode would cause an error to be thrown.
v8.0.1
- Prevent development files from being byte-compiled.
v8.0.0
- Don't use
derived-mode-parentto determine if a dispatch should be used for a mode. Instead, explicitly list the modes that a dispatch should be enabled for. A dispatch for a parent mode is not necessarily suitable for child modes. - Dispatches are now autoloaded. Rather than defining them with
context-coloring-define-dispatch, useputhashto add a dispatch plist tocontext-coloring-dispatch-hash-table. js2-modeis now an optional dependency of this package. You must explicitly install it; it won't be installed automatically as a result of installing this one.- Remove obsolete variables
context-coloring-js-block-scopes,context-coloring-delayandcontext-coloring-comments-and-strings.
v7.2.1
- Prevent
normal-top-level-add-subdirs-to-load-pathand similar tools from adding development fixtures to theload-path.
v7.2.0
- Add
gv-letplaceandmacroexp-let2support. - Fix parsing bugs.
v7.1.0
- Fix tests on Windows (the OS didn't like "let*.el").
- Add
context-coloring-initial-levelto customize the initial scope level.- Useful for Node.js programs, where the top-level scope is not global (unlike in web browsers).
- Improve
customizeinterface. - Add
context-coloring-javascript-detect-top-level-scopeto automatically bind acontext-coloring-initial-level.- Useful when writing code for web browsers and Node.js simultaneously.
v7.0.0
- Remove shell command coloring (and thus
js-modesupport). Please use
js2-modeinstead.- I do not use
js-mode, so I am not motivated to maintain support for it,
especially when there is already JavaScript support available. - Supporting asynchronous coloring alongside synchronous coloring has
gradually become a maintenance issue.
- I do not use
- Remove automatic theme detection and application. Please use standard
customize interfaces instead. - Remove built-in themes. Context coloring's focus is not in providing arbitrary
color schemes; theme authors should be responsible for
that. See here
for snippets that will provide colors for the formerly-supported themes. - Fix bug where unavailable messages would be shown in the minibuffer.
v6.5.0
- Add
eval-expressionsupport. - Add
:predicateoption for dispatches.
v6.4.1
- Fix regression where multiple timers would collide.
v6.4.0
- Rewrite the Emacs Lisp parser as a recursive descent parser, fixing numerous parsing and coloring edge cases.
- Add support for
cond,condition-case,defadvice,dolistand backquote splicing. - Apply Emacs Lisp coloring lazily on change, with near-instantaneous results.
- Add support for running scopifiers as servers, improving the long-term performance of the
js-modescopifier dramatically. - Remove support for defining scopifiers written in Emacs Lisp (as the capability is unused, and a colorizer should be written instead).