| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
|
|
|
|
| |
* all: remove "u" string prefix
* util: remove unirange
Since Python 3.3, all builds are wide unicode compatible.
* unistring: remove support for narrow-unicode builds
which stopped being relevant with Python 3.3
|
| |
|
| |
|
| |
|
| |
|
|
|
| |
Some people use the full name of the markup.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
* Add support for Setext-style headings in Markdown
* Improve inline code detection in Markdown
* Add support for indented code blocks in Markdown
* Improve italics & bold detection in Markdown
* Simplify italics & bold regexes in Markdown
* Add warning about possible unrecognized internal tags in Markdown
* Improve striktethrough detection in Markdown
* Small bugfix in Markdown
* Small bugfix in Markdown
* Small refactoring in Markdown
|
|
|
|
|
|
|
|
|
|
|
| |
* add support for .tid files (TiddlyWiki5)
* add lexers/_mapping.py
* markup.py: change versionadded of TiddlyWiki5Lexer to 2.7
* markup.py, TiddlyWiki5Lexer: use non-greedy matcher for table headers, footers, captions and classes
* markup.py, TiddlyWiki5Lexer: make timestamps of type Number.Integer
|
| |
|
| |
|
|\
| |
| |
| | |
Markdown: add support for reference-style links
|
| | |
|
|/
|
|
|
|
|
| |
Fixes the bug reported in #1389, where the markdown lexer will not issue a
token for the closing code fence.
Issue: #1389
|
| |
|
|
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.
|