summaryrefslogtreecommitdiff
path: root/pygments/formatters/terminal256.py
Commit message (Collapse)AuthorAgeFilesLines
* Update copyright year (fixes #1514.)Matthäus G. Chajdas2020-08-221-1/+1
|
* Remove Python 2 compatibility (#1348)Georg Brandl2020-02-291-6/+0
| | | | | | | | | | | * Remove Python 2 compatibility * remove 2/3 shims in pygments.util * update setup.py metadata * Remove unneeded object inheritance. * Remove unneeded future imports.
* allow terminal256 formatter to show italics...Kurt Neufeld2019-12-011-2/+12
| | | | | | | | | | | OSX users will have to follow instructions at: http://www.eddieantonio.ca/blog/2015/04/16/iterm-italics/ tldr; infocmp xterm-256color > /tmp/xterm-256color.terminfo echo 'sitm=\E[3m, ritm=\E[23m,' >> /tmp/xterm-256color.terminfo tic /tmp/xterm-256color.terminfo make sure iTerm2.settings.profiles.terminal.terminal type=xterm-256color
* Fixup all headers and some more minor problems.2.4.2Georg Brandl2019-05-281-1/+1
|
* Fix a few markup problems in the docs.Georg Brandl2018-12-181-2/+2
|
* Update ansi color name change version.Matth?us G. Chajdas2018-12-161-2/+2
|
* Use replace instead of stripMorten Enemark Lund2018-08-211-2/+2
|
* Ensure terminal formatter works with new ansi colors namesMorten Enemark Lund2018-08-211-2/+2
|
* Change ansi color names to more saying namesMorten Enemark Lund2018-08-041-1/+7
| | | | | | The ansi color names are changed to names which are easier to understand and align with color names of other projects and terminals. (e.g. ``#ansifuchsia`` to ``ansibrightmagenta``) This also drops the # prefix to the color names. Hashtag # is usually used for hex colors and the names are already prefixed with `ansi`. Furthermore, it allows the new and old set of names to be exclusive.
* Copyright update.Georg Brandl2017-01-221-1/+1
|
* Add support for partials and path segments for Handlebars.Christian Hammond2016-11-041-0/+309
This introduces support for some missing features to the Handlebars lexer: Partials and path segments. Partials mostly appeared to work before, but the `>` in `{{> ... }}` would appear as a syntax error, as could other components of the partial. This change introduces support for: * Standard partials: `{{> partialName}}` * Partials with parameters: `{{> partialName varname="value"}}` * Ddynamic partials: `{{> (partialFunc)}}` * Ddynamic partials with lookups: `{{> (lookup ../path "partialName")}}` * Partial blocks: `{{> @partial-block}}` * Inline partials: `{{#*inline}}..{{/inline}}` It also introduces support for path segments, which can reference content in the current context or in a parent context. For instance, `this.name`, `this/name`, `./name`, `../name`, `this/name`, etc. These are all now tracked as variables.