summaryrefslogtreecommitdiff
path: root/pygments/lexers/textedit.py
Commit message (Collapse)AuthorAgeFilesLines
* Update copyright year to 2023.Matthäus G. Chajdas2023-03-291-1/+1
|
* all: style fixesGeorg Brandl2022-10-271-1/+1
|
* Happy new year.Georg Brandl2022-01-251-1/+1
|
* Fix typos (#2030)Kian-Meng Ang2022-01-181-1/+1
|
* Remove accidental tab characterThomas Voss2021-10-311-1/+1
|
* Add a lexer for the sed scripting languageThomas Voss2021-10-311-6/+40
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Sed is a stream editing scripting language forming part of the POSIX standard. This means that sed cn be found as part of any POSIX compliant OS such as Linux, MacOS, and the BSDs. This lexer supports the complete POSIX standard for sed as well as various GNU extensions. The names 'gsed' and 'ssed' may sometimes be used as part of a file extension to refer specifically to GNU sed or Super Sed, two popular implementations of sed. The sed language is rather simple, here is a quick overview: - Comments begin with a '#' and continue to the end of the line. - Commands can be prepended with a range that selects lines. This can be either a number ([0-9]+), a '$', or a regular expression. Regular expressions can either be enclosed in '/' such as /regex/ or they can be exclosed in any other character however the opening delimiter must be escaped, for example: \@regex@. - Some commands such as 'w', 'r', and 'b' take a string as a parameter, this string extends either to the next ';' or newline. - Some commands such as 'a' can take multiline strings. - Commands can be grouped with braces ('{' and '}'). - The 'y' command takes two strings as parameters, seperated by any delimiter ('y/abc/123/' or 'y|abc|123|') - The 's' command is like the 'y' command but the fist parameter is a regular expression. Additionally it takes an optional 3rd parameter which are a sequence of flags ('s|regex|replace|flags'). I chose to add support for GNU sed extensions as it is by far the most used implementation.
* Run pyupgrade across codebase to modernize syntax and patterns (#1622)Jon Dufresne2021-01-171-1/+0
| | | | | | | | | | | | | | | | | | | | | | | | | | | | pyupgrade is a tool to automatically upgrade syntax for newer versions of the Python language. The project has been Python 3 only since 35544e2fc6eed0ce4a27ec7285aac71ff0ddc473, allowing for several cleanups: - Remove unnecessary "-*- coding: utf-8 -*-" cookie. Python 3 reads all source files as utf-8 by default. - Replace IOError/EnvironmentError with OSError. Python 3 unified these exceptions. The old names are aliases only. - Use the Python 3 shorter super() syntax. - Remove "utf8" argument form encode/decode. In Python 3, this value is the default. - Remove "r" from open() calls. In Python 3, this value is the default. - Remove u prefix from Unicode strings. In Python 3, all strings are Unicode. - Replace io.open() with builtin open(). In Python 3, these functions are functionally equivalent. Co-authored-by: Matthäus G. Chajdas <Anteru@users.noreply.github.com>
* Bump copyright year.Matthäus G. Chajdas2021-01-031-1/+1
|
* all: weed out more backtracking string regexesGeorg Brandl2020-12-251-2/+2
|
* Update copyright year (fixes #1514.)Matthäus G. Chajdas2020-08-221-1/+1
|
* Fix issue #1264: tweak patterns for regex and double-quoted strings for ↵Ash Searle2019-11-291-3/+3
| | | | performance, avoiding slow back-tracking
* Fixup all headers and some more minor problems.2.4.2Georg Brandl2019-05-281-1/+1
|
* Copyright update.Georg Brandl2017-01-221-1/+1
|
* Add support for partials and path segments for Handlebars.Christian Hammond2016-11-041-0/+169
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.