Last maintained in 2013. Building fails due to vanished sources.
Upstream has the following to say:
“As of February 11th 2015, Fuze will no longer support a native
Linux-based client. This means that any customers attempting to
install or use our previous Linux client will be unable to do
so. There are currently no plans to create an updated version
of the Linux client for Fuze. For Linux based customers that
still wish to use Fuze, we recommend that you try our browser
client.” -- https://support.fuze.com/hc/en-us/articles/201527877-Does-Fuze-Support-Linux-
Never marked as broken, but has been so for quite some time.
- Added lexers, styles, formatters.
- New "filename" option for HTML formatter (PR#527).
- Improved performance of the HTML formatter for long lines (PR#504).
- Updated autopygmentize script (PR#445).
- Fixed style inheritance for non-standard token types in HTML
output.
- Added support for async/await to Python 3 lexer.
- Rewrote linenos option for TerminalFormatter (it's better, but
slightly different output than before) (#1147).
- Javascript lexer now supports most of ES6 (#1100).
- Cocoa builtins updated for iOS 8.1 (PR#433).
- Combined BashSessionLexer and ShellSessionLexer, new version
should support the prompt styles of either.
- Added option to pygmentize to show a full traceback on exceptions.
- Fixed incomplete output on Windows and Python 3 (e.g. when using
iPython Notebook) (#1153).
- Allowed more traceback styles in Python console lexer (PR#253).
- Added decorators to TypeScript (PR#509).
- Fix highlighting of certain IRC logs formats (#1076).
More: https://bitbucket.org/birkenfeld/pygments-main/src/tip/CHANGES
Recent illumos includes a linux-incompatible `inotify.h` header, which configure detects: compilation fails.
Also, a newer `dtrace` on SmartOS fails creating the probes ELF linkable object (with `dtrace -G`). Disable for now.
Remove old configure option `--disable-modular-tests`.
Building packages requires package-build.el from Melpa, but installing
packages only requires package.el. Packages from ELPA are already built,
so there is no need to involve package-build.el.
When building a package from a Melpa recipe file, get the Emacs package
name from the recipe. Nix is more restrictive about packages names than
Emacs, so the Nix name for a package is sometimes different.
