| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
With the previous changes, we started to emit one <pre> per line for
line numbers. This breaks for instance the Sphinx-RTD-Theme, which
expects the line numbers to be formatted the same way as the normal
content. This commit makes the following changes:
* Emit a single <pre> inside the linenos div
* Wrap individual lines into <span> as needed
* Update all tests
* Don't yield empty <span> elements when no style is specified
This also makes the .html test files look correct when looked at with a
browser, as there is no extra whitespace in them which needs stripping.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
* Add font and background colors to Style
* Move all styles to get_style_defs, add tests
* Remove hardcoded styles, add special lineno style
* Add styles for special line numbers in tables
* Update noclasses documentation
* Refactor linenos elements and styles, add tests
* Update AUTHORS
* Fix multiple CSS prefixes, add tests
|
|
|
|
|
| |
* Fix an issue raised in the review -- don't raise None no matter what.
* Remove a few variables to make the control flow easier to understand
|
|
|
|
|
|
| |
This is slightly different from the code posted inside the issue:
* Use finally to close the registry key no matter what
* Don't use break, but return directly on the first hit
|
|
|
|
|
|
|
|
|
|
|
| |
* Remove Python 2 compatibility
* remove 2/3 shims in pygments.util
* update setup.py metadata
* Remove unneeded object inheritance.
* Remove unneeded future imports.
|
| |
|
|\ |
|
| | |
|
| |\ |
|
| | | |
|
| |/
|/|
| |
| |
| |
| |
| |
| |
| |
| |
| | |
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
|
|/ |
|
|
|
|
| |
Fixes #1053
|
|
|
|
|
|
|
|
|
|
| |
Run the pyupgrade tool across the project to use modern language
features.
- Use set literals
- Use dict comprehension
- Remove unnecessary numeric indexes in format string
- Remove unnecessary extra parentheses
|
| |
|
| |
|
|
|
|
|
| |
We're using pytest now, and that needs slightly different test-case
syntax.
|
|
|
|
|
| |
We're using Menlo on Mac OS now, and DejaVu Sans Mono on Unix. Also
updated the documentation to match the actually used fonts.
|
|
|
| |
changed font style to DejaVu Sans Mono in DEFAULT_FONT_NAME_NIX
|
| |
|
| |
|
| |
|
| |
|
|\
| |
| |
| |
| |
| | |
Allow for CSS variable in pygments stylesheets
Approved-by: Anteru <bitbucket@ca.sh13.net>
|
| |
| |
| |
| | |
Also update the license year to 2019.
|
| |
| |
| |
| | |
Adds a new option "wrapcode" which wraps the code using <code>.
|
|/ |
|
|
|
|
| |
Also uniformize usage of the 'with' contact manager to prevent resource leaks.
|
|\ |
|
| | |
|
| | |
|
| |\
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Change ansi color names to more saying names
Approved-by: Morten E. Lund <melund@gmail.com>
Approved-by: jonathanslenders <jonathan@slenders.be>
Approved-by: Anteru <bitbucket@ca.sh13.net>
|
| | |
| | |
| | |
| | | |
Also, raise on warnings from Pygments only.
|
| |/
|/| |
|
| | |
|
| | |
|
|/
|
|
|
|
| |
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.
|
| |
|
|\
| |
| |
| | |
Custom Lexer/Formatter File Loading
|
| | |
|
| |\
| | |
| | |
| | | |
Image Formatter: Mac-specific lookup for fonts (fixes #868)
|
| | | |
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
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.
|
| | |
|
| | |
|
| | |
|
|\ \
| |/
|/|
| | |
lexerdev documentation
|
| |
| |
| |
| | |
Custom lexer/formatter are no longer added to sys.modules()
|
| |
| |
| |
| |
| |
| |
| | |
Add optional function parameter for the class name to instantiate, and update cli to support this.
Move error handling to within the loading functions; they now only raise ClassNotFound.
Modify doc with these updates and the version number.
Test case clean up and additions.
|
| |
| |
| |
| |
| |
| |
| |
| | |
untrusted files
Finish custom-formatter loading and fill in some docstrings
Add load_?_from_file functions to API documentation
pep8 compliance
|