| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
| |
|
|
|
|
|
| |
This is a manual merge as we don't want to pull in the documentation
change as part of this fix for a cleaner history.
|
|
|
|
|
|
|
|
|
|
|
| |
* Add support for PowerShell Remoting sessions
* Add test case for PowerShell Remoting sessions
* Make whitespace after prompt optional
* Fix test case containing backslashes
* Add test case for local PowerShell sessions
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
* Implement lexer for execline.
This commit introduces a lexer for Laurent Bercot's execline scripting language
(https://skarnet.org/software/execline) based on Pygments' existing bash lexer,
with some minor adaptations for execline's variable naming rules.
* Add versionadded note and website link to execline lexer.
* Add execline to languages.rst and example execline script
* Explicitly mark non-special characters in execline lexer as Text
* Correct execline lexer version addded
Co-authored-by: Molly Miller <sysvinit@users.noreply.github.com>
|
| |
|
| |
|
|\
| |
| |
| | |
Recognize single > as a prompt in doscon
|
| |
| |
| |
| | |
Fixes https://bitbucket.org/birkenfeld/pygments-main/issues/1380/lexer-for-cmdexe-interactive-session-with
|
| |
| |
| |
| |
| | |
This fixes the catastrophic backtracking which previously occured for strings
like "\057hom\145/e2\071501\057pub\154ic_\150tml\057a
|
| |
| |
| |
| | |
Remove debug output, add a test file for the Slurm lexer.
|
|\ \
| | |
| | |
| | | |
add Slurm script parser
|
| |\ \
| | | |
| | | |
| | | | |
Added support for text/x-shellscript mime type.
|
| | |/ |
|
| | | |
|
| | |
| | |
| | |
| | |
| | |
| | | |
Adds the following verbs:
approve, assert, backup, block, close, compress, confirm, deny, dismount, edit, find, grant, hide, initialize, install, lock, merge, mount, open, optimize, protect, publish, redo, repair, request, revoke, save, search, step, submit, switch, sync, unblock, uninstall, unlock, unprotect, unpublish, watch
|
| |/ |
|
|/ |
|
| |
|
|\
| |
| |
| | |
Highlight zsh files using the BashLexer
|
| | |
|
|\ \
| | |
| | |
| | | |
Fix Batch variables after IF
|
| |/ |
|
| | |
|
| | |
|
| |
| |
| |
| | |
Fixes #1237
|
| |
| |
| |
| | |
Fixes #1244
|
| | |
|
| | |
|
| |
| |
| |
| |
| |
| | |
variable name.
Fixes #1214
|
| |
| |
| |
| | |
From: "Wulf C. Krueger" <philantrop@exherbo.org>
|
| |
|
| |
|
|
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.
|