wikimedia/mediawiki-extensions-SyntaxHighlight_GeSHi
1
0
Fork 0
mirror of https://gerrit.wikimedia.org/r/mediawiki/extensions/SyntaxHighlight_GeSHi synced 2024-11-15 02:24:07 +00:00
Code Issues Packages Projects Releases Wiki Activity
mediawiki-extensions-Syntax.../SyntaxHighlight.lexers.php

680 lines
7.6 KiB
PHP
Raw Normal View History

Highlight using Pygments rather than Geshi GeSHi is unmaintained, lacks support for many popular modern languages, and suffers from deep architectural flaws, chief among them the inconsistent tokenization of different languages, each of which requires a custom stylesheet. Pygments is a well-maintained alternative. It is, by my count, the most popular syntax highlighting library around. It is BSD-licensed, actively maintained, and is widely used in PHP projects. To keep this easy to review, this change does not include update for l10n files, and it does not delete the geshi/ directory. I will do those in a separate patch. The chief change between this and the previous implementation is that errors result in the code block not being highlighted, as opposed to not being printed at all, having been replaced by an angry red error message. I think that is the right user experience. If you go to StackOverflow or GitHub and try to mark up your code block as being written in some language that their highlighter doesn't know about, you don't get an error message -- the code simply doesn't get highlighted. Because we don't recursively load dependencies for extensions, to test this, you will need to create a composer.local.json in $IP and add: { "extra": { "merge-plugin": { "include": [ "extensions/SyntaxHighlight_GeSHi/composer.json" ] } } } Then run `composer update`. Bug: T85794 Change-Id: I07446ec9893fae3d1e394f435d3d95cf8be6bc33
2015-06-16 03:52:58 +00:00
<?php
// Generated by updateLexerList.php
Use short array syntax Done by phpcbf over composer fix Change-Id: I043252a1cce9e51f158e0e27983ed4ae18fcfb42
2017-06-15 16:16:11 +00:00
return [
Highlight using Pygments rather than Geshi GeSHi is unmaintained, lacks support for many popular modern languages, and suffers from deep architectural flaws, chief among them the inconsistent tokenization of different languages, each of which requires a custom stylesheet. Pygments is a well-maintained alternative. It is, by my count, the most popular syntax highlighting library around. It is BSD-licensed, actively maintained, and is widely used in PHP projects. To keep this easy to review, this change does not include update for l10n files, and it does not delete the geshi/ directory. I will do those in a separate patch. The chief change between this and the previous implementation is that errors result in the code block not being highlighted, as opposed to not being printed at all, having been replaced by an angry red error message. I think that is the right user experience. If you go to StackOverflow or GitHub and try to mark up your code block as being written in some language that their highlighter doesn't know about, you don't get an error message -- the code simply doesn't get highlighted. Because we don't recursively load dependencies for extensions, to test this, you will need to create a composer.local.json in $IP and add: { "extra": { "merge-plugin": { "include": [ "extensions/SyntaxHighlight_GeSHi/composer.json" ] } } } Then run `composer update`. Bug: T85794 Change-Id: I07446ec9893fae3d1e394f435d3d95cf8be6bc33
2015-06-16 03:52:58 +00:00
'abap',
'abl',
Update pygments bundle to 2.1 Changelog: https://bitbucket.org/birkenfeld/pygments-main/raw/7614bf7/CHANGES Lots of new lexers: Emacs Lisp, Arduino, Modula-2 with multi-dialect support, Fortran fixed format, Archetype Definition language, Terraform, Jcl, Easytrieve, ParaSail, Boogie, Turtle, Fish Shell, Roboconf, Test Anything Protocol, Shen, Component Pascal, SuperCollider, Shell consoles (Tcsh, PowerShell, MSDOS), Elm and J, Crmsh, Praat, CSound, Ezhil, Thrift, QVT Operational, Hexdump, and CAmkES Configuration. Bug: T125581 Change-Id: Ie881af3d1dff23f08ccc9cbcf5f94a084fa561e1
2016-02-02 21:37:11 +00:00
'abnf',
Highlight using Pygments rather than Geshi GeSHi is unmaintained, lacks support for many popular modern languages, and suffers from deep architectural flaws, chief among them the inconsistent tokenization of different languages, each of which requires a custom stylesheet. Pygments is a well-maintained alternative. It is, by my count, the most popular syntax highlighting library around. It is BSD-licensed, actively maintained, and is widely used in PHP projects. To keep this easy to review, this change does not include update for l10n files, and it does not delete the geshi/ directory. I will do those in a separate patch. The chief change between this and the previous implementation is that errors result in the code block not being highlighted, as opposed to not being printed at all, having been replaced by an angry red error message. I think that is the right user experience. If you go to StackOverflow or GitHub and try to mark up your code block as being written in some language that their highlighter doesn't know about, you don't get an error message -- the code simply doesn't get highlighted. Because we don't recursively load dependencies for extensions, to test this, you will need to create a composer.local.json in $IP and add: { "extra": { "merge-plugin": { "include": [ "extensions/SyntaxHighlight_GeSHi/composer.json" ] } } } Then run `composer update`. Bug: T85794 Change-Id: I07446ec9893fae3d1e394f435d3d95cf8be6bc33
2015-06-16 03:52:58 +00:00
'aconf',
'actionscript',
'actionscript3',
'ada',
'ada2005',
'ada95',
Update pygments bundle to 2.1 Changelog: https://bitbucket.org/birkenfeld/pygments-main/raw/7614bf7/CHANGES Lots of new lexers: Emacs Lisp, Arduino, Modula-2 with multi-dialect support, Fortran fixed format, Archetype Definition language, Terraform, Jcl, Easytrieve, ParaSail, Boogie, Turtle, Fish Shell, Roboconf, Test Anything Protocol, Shen, Component Pascal, SuperCollider, Shell consoles (Tcsh, PowerShell, MSDOS), Elm and J, Crmsh, Praat, CSound, Ezhil, Thrift, QVT Operational, Hexdump, and CAmkES Configuration. Bug: T125581 Change-Id: Ie881af3d1dff23f08ccc9cbcf5f94a084fa561e1
2016-02-02 21:37:11 +00:00
'adl',
Highlight using Pygments rather than Geshi GeSHi is unmaintained, lacks support for many popular modern languages, and suffers from deep architectural flaws, chief among them the inconsistent tokenization of different languages, each of which requires a custom stylesheet. Pygments is a well-maintained alternative. It is, by my count, the most popular syntax highlighting library around. It is BSD-licensed, actively maintained, and is widely used in PHP projects. To keep this easy to review, this change does not include update for l10n files, and it does not delete the geshi/ directory. I will do those in a separate patch. The chief change between this and the previous implementation is that errors result in the code block not being highlighted, as opposed to not being printed at all, having been replaced by an angry red error message. I think that is the right user experience. If you go to StackOverflow or GitHub and try to mark up your code block as being written in some language that their highlighter doesn't know about, you don't get an error message -- the code simply doesn't get highlighted. Because we don't recursively load dependencies for extensions, to test this, you will need to create a composer.local.json in $IP and add: { "extra": { "merge-plugin": { "include": [ "extensions/SyntaxHighlight_GeSHi/composer.json" ] } } } Then run `composer update`. Bug: T85794 Change-Id: I07446ec9893fae3d1e394f435d3d95cf8be6bc33
2015-06-16 03:52:58 +00:00
'agda',
Update pygments to 2.2 Notable changes: * Added new token types and lexing for magic methods and variables in Python and PHP. * Added a new token type for heredoc (and similar) string delimiters and lexing for them in C++, Perl, PHP, Postgresql and Ruby lexers. * Improved the CSS lexer. * Added Varnish config lexer Full changelog is found at: <https://bitbucket.org/birkenfeld/pygments-main/src/bc45808f83d5338e3116be91890e6ad15220ee45/CHANGES> Bug: T156573 Change-Id: I4dc1782f19881ba1294308e1cdea1b2e063f438a
2017-01-29 09:35:35 +00:00
'aheui',
Highlight using Pygments rather than Geshi GeSHi is unmaintained, lacks support for many popular modern languages, and suffers from deep architectural flaws, chief among them the inconsistent tokenization of different languages, each of which requires a custom stylesheet. Pygments is a well-maintained alternative. It is, by my count, the most popular syntax highlighting library around. It is BSD-licensed, actively maintained, and is widely used in PHP projects. To keep this easy to review, this change does not include update for l10n files, and it does not delete the geshi/ directory. I will do those in a separate patch. The chief change between this and the previous implementation is that errors result in the code block not being highlighted, as opposed to not being printed at all, having been replaced by an angry red error message. I think that is the right user experience. If you go to StackOverflow or GitHub and try to mark up your code block as being written in some language that their highlighter doesn't know about, you don't get an error message -- the code simply doesn't get highlighted. Because we don't recursively load dependencies for extensions, to test this, you will need to create a composer.local.json in $IP and add: { "extra": { "merge-plugin": { "include": [ "extensions/SyntaxHighlight_GeSHi/composer.json" ] } } } Then run `composer update`. Bug: T85794 Change-Id: I07446ec9893fae3d1e394f435d3d95cf8be6bc33
2015-06-16 03:52:58 +00:00
'ahk',
'alloy',
'ambienttalk',
'ambienttalk/2',
Update pygments to 2.2 Notable changes: * Added new token types and lexing for magic methods and variables in Python and PHP. * Added a new token type for heredoc (and similar) string delimiters and lexing for them in C++, Perl, PHP, Postgresql and Ruby lexers. * Improved the CSS lexer. * Added Varnish config lexer Full changelog is found at: <https://bitbucket.org/birkenfeld/pygments-main/src/bc45808f83d5338e3116be91890e6ad15220ee45/CHANGES> Bug: T156573 Change-Id: I4dc1782f19881ba1294308e1cdea1b2e063f438a
2017-01-29 09:35:35 +00:00
'ampl',
Highlight using Pygments rather than Geshi GeSHi is unmaintained, lacks support for many popular modern languages, and suffers from deep architectural flaws, chief among them the inconsistent tokenization of different languages, each of which requires a custom stylesheet. Pygments is a well-maintained alternative. It is, by my count, the most popular syntax highlighting library around. It is BSD-licensed, actively maintained, and is widely used in PHP projects. To keep this easy to review, this change does not include update for l10n files, and it does not delete the geshi/ directory. I will do those in a separate patch. The chief change between this and the previous implementation is that errors result in the code block not being highlighted, as opposed to not being printed at all, having been replaced by an angry red error message. I think that is the right user experience. If you go to StackOverflow or GitHub and try to mark up your code block as being written in some language that their highlighter doesn't know about, you don't get an error message -- the code simply doesn't get highlighted. Because we don't recursively load dependencies for extensions, to test this, you will need to create a composer.local.json in $IP and add: { "extra": { "merge-plugin": { "include": [ "extensions/SyntaxHighlight_GeSHi/composer.json" ] } } } Then run `composer update`. Bug: T85794 Change-Id: I07446ec9893fae3d1e394f435d3d95cf8be6bc33
2015-06-16 03:52:58 +00:00
'antlr',
'antlr-actionscript',
'antlr-as',
'antlr-c#',
'antlr-cpp',
'antlr-csharp',
'antlr-java',
'antlr-objc',
'antlr-perl',
'antlr-python',
'antlr-rb',
'antlr-ruby',
'apache',
'apacheconf',
'apl',
'applescript',
Update pygments bundle to 2.1 Changelog: https://bitbucket.org/birkenfeld/pygments-main/raw/7614bf7/CHANGES Lots of new lexers: Emacs Lisp, Arduino, Modula-2 with multi-dialect support, Fortran fixed format, Archetype Definition language, Terraform, Jcl, Easytrieve, ParaSail, Boogie, Turtle, Fish Shell, Roboconf, Test Anything Protocol, Shen, Component Pascal, SuperCollider, Shell consoles (Tcsh, PowerShell, MSDOS), Elm and J, Crmsh, Praat, CSound, Ezhil, Thrift, QVT Operational, Hexdump, and CAmkES Configuration. Bug: T125581 Change-Id: Ie881af3d1dff23f08ccc9cbcf5f94a084fa561e1
2016-02-02 21:37:11 +00:00
'arduino',
Highlight using Pygments rather than Geshi GeSHi is unmaintained, lacks support for many popular modern languages, and suffers from deep architectural flaws, chief among them the inconsistent tokenization of different languages, each of which requires a custom stylesheet. Pygments is a well-maintained alternative. It is, by my count, the most popular syntax highlighting library around. It is BSD-licensed, actively maintained, and is widely used in PHP projects. To keep this easy to review, this change does not include update for l10n files, and it does not delete the geshi/ directory. I will do those in a separate patch. The chief change between this and the previous implementation is that errors result in the code block not being highlighted, as opposed to not being printed at all, having been replaced by an angry red error message. I think that is the right user experience. If you go to StackOverflow or GitHub and try to mark up your code block as being written in some language that their highlighter doesn't know about, you don't get an error message -- the code simply doesn't get highlighted. Because we don't recursively load dependencies for extensions, to test this, you will need to create a composer.local.json in $IP and add: { "extra": { "merge-plugin": { "include": [ "extensions/SyntaxHighlight_GeSHi/composer.json" ] } } } Then run `composer update`. Bug: T85794 Change-Id: I07446ec9893fae3d1e394f435d3d95cf8be6bc33
2015-06-16 03:52:58 +00:00
'arexx',
'as',
'as3',
'asm',
'aspectj',
'aspx-cs',
'aspx-vb',
'asy',
'asymptote',
'at',
'autohotkey',
'autoit',
'awk',
'b3d',
'basemake',
'bash',
'basic',
'bat',
'batch',
'bbcode',
Update pygments bundle to 2.1 Changelog: https://bitbucket.org/birkenfeld/pygments-main/raw/7614bf7/CHANGES Lots of new lexers: Emacs Lisp, Arduino, Modula-2 with multi-dialect support, Fortran fixed format, Archetype Definition language, Terraform, Jcl, Easytrieve, ParaSail, Boogie, Turtle, Fish Shell, Roboconf, Test Anything Protocol, Shen, Component Pascal, SuperCollider, Shell consoles (Tcsh, PowerShell, MSDOS), Elm and J, Crmsh, Praat, CSound, Ezhil, Thrift, QVT Operational, Hexdump, and CAmkES Configuration. Bug: T125581 Change-Id: Ie881af3d1dff23f08ccc9cbcf5f94a084fa561e1
2016-02-02 21:37:11 +00:00
'bc',
Highlight using Pygments rather than Geshi GeSHi is unmaintained, lacks support for many popular modern languages, and suffers from deep architectural flaws, chief among them the inconsistent tokenization of different languages, each of which requires a custom stylesheet. Pygments is a well-maintained alternative. It is, by my count, the most popular syntax highlighting library around. It is BSD-licensed, actively maintained, and is widely used in PHP projects. To keep this easy to review, this change does not include update for l10n files, and it does not delete the geshi/ directory. I will do those in a separate patch. The chief change between this and the previous implementation is that errors result in the code block not being highlighted, as opposed to not being printed at all, having been replaced by an angry red error message. I think that is the right user experience. If you go to StackOverflow or GitHub and try to mark up your code block as being written in some language that their highlighter doesn't know about, you don't get an error message -- the code simply doesn't get highlighted. Because we don't recursively load dependencies for extensions, to test this, you will need to create a composer.local.json in $IP and add: { "extra": { "merge-plugin": { "include": [ "extensions/SyntaxHighlight_GeSHi/composer.json" ] } } } Then run `composer update`. Bug: T85794 Change-Id: I07446ec9893fae3d1e394f435d3d95cf8be6bc33
2015-06-16 03:52:58 +00:00
'befunge',
'bf',
Update pygments to 2.2 Notable changes: * Added new token types and lexing for magic methods and variables in Python and PHP. * Added a new token type for heredoc (and similar) string delimiters and lexing for them in C++, Perl, PHP, Postgresql and Ruby lexers. * Improved the CSS lexer. * Added Varnish config lexer Full changelog is found at: <https://bitbucket.org/birkenfeld/pygments-main/src/bc45808f83d5338e3116be91890e6ad15220ee45/CHANGES> Bug: T156573 Change-Id: I4dc1782f19881ba1294308e1cdea1b2e063f438a
2017-01-29 09:35:35 +00:00
'bib',
'bibtex',
Highlight using Pygments rather than Geshi GeSHi is unmaintained, lacks support for many popular modern languages, and suffers from deep architectural flaws, chief among them the inconsistent tokenization of different languages, each of which requires a custom stylesheet. Pygments is a well-maintained alternative. It is, by my count, the most popular syntax highlighting library around. It is BSD-licensed, actively maintained, and is widely used in PHP projects. To keep this easy to review, this change does not include update for l10n files, and it does not delete the geshi/ directory. I will do those in a separate patch. The chief change between this and the previous implementation is that errors result in the code block not being highlighted, as opposed to not being printed at all, having been replaced by an angry red error message. I think that is the right user experience. If you go to StackOverflow or GitHub and try to mark up your code block as being written in some language that their highlighter doesn't know about, you don't get an error message -- the code simply doesn't get highlighted. Because we don't recursively load dependencies for extensions, to test this, you will need to create a composer.local.json in $IP and add: { "extra": { "merge-plugin": { "include": [ "extensions/SyntaxHighlight_GeSHi/composer.json" ] } } } Then run `composer update`. Bug: T85794 Change-Id: I07446ec9893fae3d1e394f435d3d95cf8be6bc33
2015-06-16 03:52:58 +00:00
'blitzbasic',
'blitzmax',
'bmax',
Update pygments bundle to 2.1 Changelog: https://bitbucket.org/birkenfeld/pygments-main/raw/7614bf7/CHANGES Lots of new lexers: Emacs Lisp, Arduino, Modula-2 with multi-dialect support, Fortran fixed format, Archetype Definition language, Terraform, Jcl, Easytrieve, ParaSail, Boogie, Turtle, Fish Shell, Roboconf, Test Anything Protocol, Shen, Component Pascal, SuperCollider, Shell consoles (Tcsh, PowerShell, MSDOS), Elm and J, Crmsh, Praat, CSound, Ezhil, Thrift, QVT Operational, Hexdump, and CAmkES Configuration. Bug: T125581 Change-Id: Ie881af3d1dff23f08ccc9cbcf5f94a084fa561e1
2016-02-02 21:37:11 +00:00
'bnf',
Highlight using Pygments rather than Geshi GeSHi is unmaintained, lacks support for many popular modern languages, and suffers from deep architectural flaws, chief among them the inconsistent tokenization of different languages, each of which requires a custom stylesheet. Pygments is a well-maintained alternative. It is, by my count, the most popular syntax highlighting library around. It is BSD-licensed, actively maintained, and is widely used in PHP projects. To keep this easy to review, this change does not include update for l10n files, and it does not delete the geshi/ directory. I will do those in a separate patch. The chief change between this and the previous implementation is that errors result in the code block not being highlighted, as opposed to not being printed at all, having been replaced by an angry red error message. I think that is the right user experience. If you go to StackOverflow or GitHub and try to mark up your code block as being written in some language that their highlighter doesn't know about, you don't get an error message -- the code simply doesn't get highlighted. Because we don't recursively load dependencies for extensions, to test this, you will need to create a composer.local.json in $IP and add: { "extra": { "merge-plugin": { "include": [ "extensions/SyntaxHighlight_GeSHi/composer.json" ] } } } Then run `composer update`. Bug: T85794 Change-Id: I07446ec9893fae3d1e394f435d3d95cf8be6bc33
2015-06-16 03:52:58 +00:00
'boo',
Update pygments bundle to 2.1 Changelog: https://bitbucket.org/birkenfeld/pygments-main/raw/7614bf7/CHANGES Lots of new lexers: Emacs Lisp, Arduino, Modula-2 with multi-dialect support, Fortran fixed format, Archetype Definition language, Terraform, Jcl, Easytrieve, ParaSail, Boogie, Turtle, Fish Shell, Roboconf, Test Anything Protocol, Shen, Component Pascal, SuperCollider, Shell consoles (Tcsh, PowerShell, MSDOS), Elm and J, Crmsh, Praat, CSound, Ezhil, Thrift, QVT Operational, Hexdump, and CAmkES Configuration. Bug: T125581 Change-Id: Ie881af3d1dff23f08ccc9cbcf5f94a084fa561e1
2016-02-02 21:37:11 +00:00
'boogie',
Highlight using Pygments rather than Geshi GeSHi is unmaintained, lacks support for many popular modern languages, and suffers from deep architectural flaws, chief among them the inconsistent tokenization of different languages, each of which requires a custom stylesheet. Pygments is a well-maintained alternative. It is, by my count, the most popular syntax highlighting library around. It is BSD-licensed, actively maintained, and is widely used in PHP projects. To keep this easy to review, this change does not include update for l10n files, and it does not delete the geshi/ directory. I will do those in a separate patch. The chief change between this and the previous implementation is that errors result in the code block not being highlighted, as opposed to not being printed at all, having been replaced by an angry red error message. I think that is the right user experience. If you go to StackOverflow or GitHub and try to mark up your code block as being written in some language that their highlighter doesn't know about, you don't get an error message -- the code simply doesn't get highlighted. Because we don't recursively load dependencies for extensions, to test this, you will need to create a composer.local.json in $IP and add: { "extra": { "merge-plugin": { "include": [ "extensions/SyntaxHighlight_GeSHi/composer.json" ] } } } Then run `composer update`. Bug: T85794 Change-Id: I07446ec9893fae3d1e394f435d3d95cf8be6bc33
2015-06-16 03:52:58 +00:00
'bplus',
'brainfuck',
'bro',
'bsdmake',
Update pygments to 2.2 Notable changes: * Added new token types and lexing for magic methods and variables in Python and PHP. * Added a new token type for heredoc (and similar) string delimiters and lexing for them in C++, Perl, PHP, Postgresql and Ruby lexers. * Improved the CSS lexer. * Added Varnish config lexer Full changelog is found at: <https://bitbucket.org/birkenfeld/pygments-main/src/bc45808f83d5338e3116be91890e6ad15220ee45/CHANGES> Bug: T156573 Change-Id: I4dc1782f19881ba1294308e1cdea1b2e063f438a
2017-01-29 09:35:35 +00:00
'bst',
'bst-pybtex',
Highlight using Pygments rather than Geshi GeSHi is unmaintained, lacks support for many popular modern languages, and suffers from deep architectural flaws, chief among them the inconsistent tokenization of different languages, each of which requires a custom stylesheet. Pygments is a well-maintained alternative. It is, by my count, the most popular syntax highlighting library around. It is BSD-licensed, actively maintained, and is widely used in PHP projects. To keep this easy to review, this change does not include update for l10n files, and it does not delete the geshi/ directory. I will do those in a separate patch. The chief change between this and the previous implementation is that errors result in the code block not being highlighted, as opposed to not being printed at all, having been replaced by an angry red error message. I think that is the right user experience. If you go to StackOverflow or GitHub and try to mark up your code block as being written in some language that their highlighter doesn't know about, you don't get an error message -- the code simply doesn't get highlighted. Because we don't recursively load dependencies for extensions, to test this, you will need to create a composer.local.json in $IP and add: { "extra": { "merge-plugin": { "include": [ "extensions/SyntaxHighlight_GeSHi/composer.json" ] } } } Then run `composer update`. Bug: T85794 Change-Id: I07446ec9893fae3d1e394f435d3d95cf8be6bc33
2015-06-16 03:52:58 +00:00
'bugs',
'c',
'c#',
'c++',
'c++-objdumb',
'c-objdump',
'ca65',
Update pygments bundle to 2.1 Changelog: https://bitbucket.org/birkenfeld/pygments-main/raw/7614bf7/CHANGES Lots of new lexers: Emacs Lisp, Arduino, Modula-2 with multi-dialect support, Fortran fixed format, Archetype Definition language, Terraform, Jcl, Easytrieve, ParaSail, Boogie, Turtle, Fish Shell, Roboconf, Test Anything Protocol, Shen, Component Pascal, SuperCollider, Shell consoles (Tcsh, PowerShell, MSDOS), Elm and J, Crmsh, Praat, CSound, Ezhil, Thrift, QVT Operational, Hexdump, and CAmkES Configuration. Bug: T125581 Change-Id: Ie881af3d1dff23f08ccc9cbcf5f94a084fa561e1
2016-02-02 21:37:11 +00:00
'cadl',
'camkes',
Update pygments to 2.2 Notable changes: * Added new token types and lexing for magic methods and variables in Python and PHP. * Added a new token type for heredoc (and similar) string delimiters and lexing for them in C++, Perl, PHP, Postgresql and Ruby lexers. * Improved the CSS lexer. * Added Varnish config lexer Full changelog is found at: <https://bitbucket.org/birkenfeld/pygments-main/src/bc45808f83d5338e3116be91890e6ad15220ee45/CHANGES> Bug: T156573 Change-Id: I4dc1782f19881ba1294308e1cdea1b2e063f438a
2017-01-29 09:35:35 +00:00
'capdl',
'capnp',
Highlight using Pygments rather than Geshi GeSHi is unmaintained, lacks support for many popular modern languages, and suffers from deep architectural flaws, chief among them the inconsistent tokenization of different languages, each of which requires a custom stylesheet. Pygments is a well-maintained alternative. It is, by my count, the most popular syntax highlighting library around. It is BSD-licensed, actively maintained, and is widely used in PHP projects. To keep this easy to review, this change does not include update for l10n files, and it does not delete the geshi/ directory. I will do those in a separate patch. The chief change between this and the previous implementation is that errors result in the code block not being highlighted, as opposed to not being printed at all, having been replaced by an angry red error message. I think that is the right user experience. If you go to StackOverflow or GitHub and try to mark up your code block as being written in some language that their highlighter doesn't know about, you don't get an error message -- the code simply doesn't get highlighted. Because we don't recursively load dependencies for extensions, to test this, you will need to create a composer.local.json in $IP and add: { "extra": { "merge-plugin": { "include": [ "extensions/SyntaxHighlight_GeSHi/composer.json" ] } } } Then run `composer update`. Bug: T85794 Change-Id: I07446ec9893fae3d1e394f435d3d95cf8be6bc33
2015-06-16 03:52:58 +00:00
'cbmbas',
'ceylon',
'cf3',
'cfc',
'cfengine3',
'cfg',
'cfm',
'cfs',
'chai',
'chaiscript',
'chapel',
'cheetah',
'chpl',
'cirru',
'cl',
'clay',
Update pygments to 2.2 Notable changes: * Added new token types and lexing for magic methods and variables in Python and PHP. * Added a new token type for heredoc (and similar) string delimiters and lexing for them in C++, Perl, PHP, Postgresql and Ruby lexers. * Improved the CSS lexer. * Added Varnish config lexer Full changelog is found at: <https://bitbucket.org/birkenfeld/pygments-main/src/bc45808f83d5338e3116be91890e6ad15220ee45/CHANGES> Bug: T156573 Change-Id: I4dc1782f19881ba1294308e1cdea1b2e063f438a
2017-01-29 09:35:35 +00:00
'clean',
Highlight using Pygments rather than Geshi GeSHi is unmaintained, lacks support for many popular modern languages, and suffers from deep architectural flaws, chief among them the inconsistent tokenization of different languages, each of which requires a custom stylesheet. Pygments is a well-maintained alternative. It is, by my count, the most popular syntax highlighting library around. It is BSD-licensed, actively maintained, and is widely used in PHP projects. To keep this easy to review, this change does not include update for l10n files, and it does not delete the geshi/ directory. I will do those in a separate patch. The chief change between this and the previous implementation is that errors result in the code block not being highlighted, as opposed to not being printed at all, having been replaced by an angry red error message. I think that is the right user experience. If you go to StackOverflow or GitHub and try to mark up your code block as being written in some language that their highlighter doesn't know about, you don't get an error message -- the code simply doesn't get highlighted. Because we don't recursively load dependencies for extensions, to test this, you will need to create a composer.local.json in $IP and add: { "extra": { "merge-plugin": { "include": [ "extensions/SyntaxHighlight_GeSHi/composer.json" ] } } } Then run `composer update`. Bug: T85794 Change-Id: I07446ec9893fae3d1e394f435d3d95cf8be6bc33
2015-06-16 03:52:58 +00:00
'clipper',
'clj',
'cljs',
'clojure',
'clojurescript',
'cmake',
'cobol',
'cobolfree',
'coffee',
'coffee-script',
'coffeescript',
'common-lisp',
Update pygments bundle to 2.1 Changelog: https://bitbucket.org/birkenfeld/pygments-main/raw/7614bf7/CHANGES Lots of new lexers: Emacs Lisp, Arduino, Modula-2 with multi-dialect support, Fortran fixed format, Archetype Definition language, Terraform, Jcl, Easytrieve, ParaSail, Boogie, Turtle, Fish Shell, Roboconf, Test Anything Protocol, Shen, Component Pascal, SuperCollider, Shell consoles (Tcsh, PowerShell, MSDOS), Elm and J, Crmsh, Praat, CSound, Ezhil, Thrift, QVT Operational, Hexdump, and CAmkES Configuration. Bug: T125581 Change-Id: Ie881af3d1dff23f08ccc9cbcf5f94a084fa561e1
2016-02-02 21:37:11 +00:00
'componentpascal',
Highlight using Pygments rather than Geshi GeSHi is unmaintained, lacks support for many popular modern languages, and suffers from deep architectural flaws, chief among them the inconsistent tokenization of different languages, each of which requires a custom stylesheet. Pygments is a well-maintained alternative. It is, by my count, the most popular syntax highlighting library around. It is BSD-licensed, actively maintained, and is widely used in PHP projects. To keep this easy to review, this change does not include update for l10n files, and it does not delete the geshi/ directory. I will do those in a separate patch. The chief change between this and the previous implementation is that errors result in the code block not being highlighted, as opposed to not being printed at all, having been replaced by an angry red error message. I think that is the right user experience. If you go to StackOverflow or GitHub and try to mark up your code block as being written in some language that their highlighter doesn't know about, you don't get an error message -- the code simply doesn't get highlighted. Because we don't recursively load dependencies for extensions, to test this, you will need to create a composer.local.json in $IP and add: { "extra": { "merge-plugin": { "include": [ "extensions/SyntaxHighlight_GeSHi/composer.json" ] } } } Then run `composer update`. Bug: T85794 Change-Id: I07446ec9893fae3d1e394f435d3d95cf8be6bc33
2015-06-16 03:52:58 +00:00
'console',
'control',
'coq',
Update pygments bundle to 2.1 Changelog: https://bitbucket.org/birkenfeld/pygments-main/raw/7614bf7/CHANGES Lots of new lexers: Emacs Lisp, Arduino, Modula-2 with multi-dialect support, Fortran fixed format, Archetype Definition language, Terraform, Jcl, Easytrieve, ParaSail, Boogie, Turtle, Fish Shell, Roboconf, Test Anything Protocol, Shen, Component Pascal, SuperCollider, Shell consoles (Tcsh, PowerShell, MSDOS), Elm and J, Crmsh, Praat, CSound, Ezhil, Thrift, QVT Operational, Hexdump, and CAmkES Configuration. Bug: T125581 Change-Id: Ie881af3d1dff23f08ccc9cbcf5f94a084fa561e1
2016-02-02 21:37:11 +00:00
'cp',
Highlight using Pygments rather than Geshi GeSHi is unmaintained, lacks support for many popular modern languages, and suffers from deep architectural flaws, chief among them the inconsistent tokenization of different languages, each of which requires a custom stylesheet. Pygments is a well-maintained alternative. It is, by my count, the most popular syntax highlighting library around. It is BSD-licensed, actively maintained, and is widely used in PHP projects. To keep this easy to review, this change does not include update for l10n files, and it does not delete the geshi/ directory. I will do those in a separate patch. The chief change between this and the previous implementation is that errors result in the code block not being highlighted, as opposed to not being printed at all, having been replaced by an angry red error message. I think that is the right user experience. If you go to StackOverflow or GitHub and try to mark up your code block as being written in some language that their highlighter doesn't know about, you don't get an error message -- the code simply doesn't get highlighted. Because we don't recursively load dependencies for extensions, to test this, you will need to create a composer.local.json in $IP and add: { "extra": { "merge-plugin": { "include": [ "extensions/SyntaxHighlight_GeSHi/composer.json" ] } } } Then run `composer update`. Bug: T85794 Change-Id: I07446ec9893fae3d1e394f435d3d95cf8be6bc33
2015-06-16 03:52:58 +00:00
'cpp',
'cpp-objdump',
Update pygments bundle to 2.1 Changelog: https://bitbucket.org/birkenfeld/pygments-main/raw/7614bf7/CHANGES Lots of new lexers: Emacs Lisp, Arduino, Modula-2 with multi-dialect support, Fortran fixed format, Archetype Definition language, Terraform, Jcl, Easytrieve, ParaSail, Boogie, Turtle, Fish Shell, Roboconf, Test Anything Protocol, Shen, Component Pascal, SuperCollider, Shell consoles (Tcsh, PowerShell, MSDOS), Elm and J, Crmsh, Praat, CSound, Ezhil, Thrift, QVT Operational, Hexdump, and CAmkES Configuration. Bug: T125581 Change-Id: Ie881af3d1dff23f08ccc9cbcf5f94a084fa561e1
2016-02-02 21:37:11 +00:00
'cpsa',
Update pygments to 2.2 Notable changes: * Added new token types and lexing for magic methods and variables in Python and PHP. * Added a new token type for heredoc (and similar) string delimiters and lexing for them in C++, Perl, PHP, Postgresql and Ruby lexers. * Improved the CSS lexer. * Added Varnish config lexer Full changelog is found at: <https://bitbucket.org/birkenfeld/pygments-main/src/bc45808f83d5338e3116be91890e6ad15220ee45/CHANGES> Bug: T156573 Change-Id: I4dc1782f19881ba1294308e1cdea1b2e063f438a
2017-01-29 09:35:35 +00:00
'cr',
Update pygments bundle to 2.1 Changelog: https://bitbucket.org/birkenfeld/pygments-main/raw/7614bf7/CHANGES Lots of new lexers: Emacs Lisp, Arduino, Modula-2 with multi-dialect support, Fortran fixed format, Archetype Definition language, Terraform, Jcl, Easytrieve, ParaSail, Boogie, Turtle, Fish Shell, Roboconf, Test Anything Protocol, Shen, Component Pascal, SuperCollider, Shell consoles (Tcsh, PowerShell, MSDOS), Elm and J, Crmsh, Praat, CSound, Ezhil, Thrift, QVT Operational, Hexdump, and CAmkES Configuration. Bug: T125581 Change-Id: Ie881af3d1dff23f08ccc9cbcf5f94a084fa561e1
2016-02-02 21:37:11 +00:00
'crmsh',
Highlight using Pygments rather than Geshi GeSHi is unmaintained, lacks support for many popular modern languages, and suffers from deep architectural flaws, chief among them the inconsistent tokenization of different languages, each of which requires a custom stylesheet. Pygments is a well-maintained alternative. It is, by my count, the most popular syntax highlighting library around. It is BSD-licensed, actively maintained, and is widely used in PHP projects. To keep this easy to review, this change does not include update for l10n files, and it does not delete the geshi/ directory. I will do those in a separate patch. The chief change between this and the previous implementation is that errors result in the code block not being highlighted, as opposed to not being printed at all, having been replaced by an angry red error message. I think that is the right user experience. If you go to StackOverflow or GitHub and try to mark up your code block as being written in some language that their highlighter doesn't know about, you don't get an error message -- the code simply doesn't get highlighted. Because we don't recursively load dependencies for extensions, to test this, you will need to create a composer.local.json in $IP and add: { "extra": { "merge-plugin": { "include": [ "extensions/SyntaxHighlight_GeSHi/composer.json" ] } } } Then run `composer update`. Bug: T85794 Change-Id: I07446ec9893fae3d1e394f435d3d95cf8be6bc33
2015-06-16 03:52:58 +00:00
'croc',
'cry',
'cryptol',
Update pygments to 2.2 Notable changes: * Added new token types and lexing for magic methods and variables in Python and PHP. * Added a new token type for heredoc (and similar) string delimiters and lexing for them in C++, Perl, PHP, Postgresql and Ruby lexers. * Improved the CSS lexer. * Added Varnish config lexer Full changelog is found at: <https://bitbucket.org/birkenfeld/pygments-main/src/bc45808f83d5338e3116be91890e6ad15220ee45/CHANGES> Bug: T156573 Change-Id: I4dc1782f19881ba1294308e1cdea1b2e063f438a
2017-01-29 09:35:35 +00:00
'crystal',
Highlight using Pygments rather than Geshi GeSHi is unmaintained, lacks support for many popular modern languages, and suffers from deep architectural flaws, chief among them the inconsistent tokenization of different languages, each of which requires a custom stylesheet. Pygments is a well-maintained alternative. It is, by my count, the most popular syntax highlighting library around. It is BSD-licensed, actively maintained, and is widely used in PHP projects. To keep this easy to review, this change does not include update for l10n files, and it does not delete the geshi/ directory. I will do those in a separate patch. The chief change between this and the previous implementation is that errors result in the code block not being highlighted, as opposed to not being printed at all, having been replaced by an angry red error message. I think that is the right user experience. If you go to StackOverflow or GitHub and try to mark up your code block as being written in some language that their highlighter doesn't know about, you don't get an error message -- the code simply doesn't get highlighted. Because we don't recursively load dependencies for extensions, to test this, you will need to create a composer.local.json in $IP and add: { "extra": { "merge-plugin": { "include": [ "extensions/SyntaxHighlight_GeSHi/composer.json" ] } } } Then run `composer update`. Bug: T85794 Change-Id: I07446ec9893fae3d1e394f435d3d95cf8be6bc33
2015-06-16 03:52:58 +00:00
'csh',
'csharp',
Update pygments bundle to 2.1 Changelog: https://bitbucket.org/birkenfeld/pygments-main/raw/7614bf7/CHANGES Lots of new lexers: Emacs Lisp, Arduino, Modula-2 with multi-dialect support, Fortran fixed format, Archetype Definition language, Terraform, Jcl, Easytrieve, ParaSail, Boogie, Turtle, Fish Shell, Roboconf, Test Anything Protocol, Shen, Component Pascal, SuperCollider, Shell consoles (Tcsh, PowerShell, MSDOS), Elm and J, Crmsh, Praat, CSound, Ezhil, Thrift, QVT Operational, Hexdump, and CAmkES Configuration. Bug: T125581 Change-Id: Ie881af3d1dff23f08ccc9cbcf5f94a084fa561e1
2016-02-02 21:37:11 +00:00
'csound',
'csound-csd',
'csound-document',
'csound-orc',
'csound-sco',
'csound-score',
Highlight using Pygments rather than Geshi GeSHi is unmaintained, lacks support for many popular modern languages, and suffers from deep architectural flaws, chief among them the inconsistent tokenization of different languages, each of which requires a custom stylesheet. Pygments is a well-maintained alternative. It is, by my count, the most popular syntax highlighting library around. It is BSD-licensed, actively maintained, and is widely used in PHP projects. To keep this easy to review, this change does not include update for l10n files, and it does not delete the geshi/ directory. I will do those in a separate patch. The chief change between this and the previous implementation is that errors result in the code block not being highlighted, as opposed to not being printed at all, having been replaced by an angry red error message. I think that is the right user experience. If you go to StackOverflow or GitHub and try to mark up your code block as being written in some language that their highlighter doesn't know about, you don't get an error message -- the code simply doesn't get highlighted. Because we don't recursively load dependencies for extensions, to test this, you will need to create a composer.local.json in $IP and add: { "extra": { "merge-plugin": { "include": [ "extensions/SyntaxHighlight_GeSHi/composer.json" ] } } } Then run `composer update`. Bug: T85794 Change-Id: I07446ec9893fae3d1e394f435d3d95cf8be6bc33
2015-06-16 03:52:58 +00:00
'css',
'css+django',
'css+erb',
'css+genshi',
'css+genshitext',
'css+jinja',
'css+lasso',
'css+mako',
'css+mozpreproc',
'css+myghty',
'css+php',
'css+ruby',
'css+smarty',
'cu',
'cucumber',
'cuda',
'cxx-objdump',
'cypher',
'cython',
'd',
'd-objdump',
'dart',
'debcontrol',
'debsources',
'delphi',
'dg',
'diff',
'django',
Update pygments to 2.2 Notable changes: * Added new token types and lexing for magic methods and variables in Python and PHP. * Added a new token type for heredoc (and similar) string delimiters and lexing for them in C++, Perl, PHP, Postgresql and Ruby lexers. * Improved the CSS lexer. * Added Varnish config lexer Full changelog is found at: <https://bitbucket.org/birkenfeld/pygments-main/src/bc45808f83d5338e3116be91890e6ad15220ee45/CHANGES> Bug: T156573 Change-Id: I4dc1782f19881ba1294308e1cdea1b2e063f438a
2017-01-29 09:35:35 +00:00
'do',
Highlight using Pygments rather than Geshi GeSHi is unmaintained, lacks support for many popular modern languages, and suffers from deep architectural flaws, chief among them the inconsistent tokenization of different languages, each of which requires a custom stylesheet. Pygments is a well-maintained alternative. It is, by my count, the most popular syntax highlighting library around. It is BSD-licensed, actively maintained, and is widely used in PHP projects. To keep this easy to review, this change does not include update for l10n files, and it does not delete the geshi/ directory. I will do those in a separate patch. The chief change between this and the previous implementation is that errors result in the code block not being highlighted, as opposed to not being printed at all, having been replaced by an angry red error message. I think that is the right user experience. If you go to StackOverflow or GitHub and try to mark up your code block as being written in some language that their highlighter doesn't know about, you don't get an error message -- the code simply doesn't get highlighted. Because we don't recursively load dependencies for extensions, to test this, you will need to create a composer.local.json in $IP and add: { "extra": { "merge-plugin": { "include": [ "extensions/SyntaxHighlight_GeSHi/composer.json" ] } } } Then run `composer update`. Bug: T85794 Change-Id: I07446ec9893fae3d1e394f435d3d95cf8be6bc33
2015-06-16 03:52:58 +00:00
'docker',
'dockerfile',
'dosbatch',
Update pygments bundle to 2.1 Changelog: https://bitbucket.org/birkenfeld/pygments-main/raw/7614bf7/CHANGES Lots of new lexers: Emacs Lisp, Arduino, Modula-2 with multi-dialect support, Fortran fixed format, Archetype Definition language, Terraform, Jcl, Easytrieve, ParaSail, Boogie, Turtle, Fish Shell, Roboconf, Test Anything Protocol, Shen, Component Pascal, SuperCollider, Shell consoles (Tcsh, PowerShell, MSDOS), Elm and J, Crmsh, Praat, CSound, Ezhil, Thrift, QVT Operational, Hexdump, and CAmkES Configuration. Bug: T125581 Change-Id: Ie881af3d1dff23f08ccc9cbcf5f94a084fa561e1
2016-02-02 21:37:11 +00:00
'doscon',
Highlight using Pygments rather than Geshi GeSHi is unmaintained, lacks support for many popular modern languages, and suffers from deep architectural flaws, chief among them the inconsistent tokenization of different languages, each of which requires a custom stylesheet. Pygments is a well-maintained alternative. It is, by my count, the most popular syntax highlighting library around. It is BSD-licensed, actively maintained, and is widely used in PHP projects. To keep this easy to review, this change does not include update for l10n files, and it does not delete the geshi/ directory. I will do those in a separate patch. The chief change between this and the previous implementation is that errors result in the code block not being highlighted, as opposed to not being printed at all, having been replaced by an angry red error message. I think that is the right user experience. If you go to StackOverflow or GitHub and try to mark up your code block as being written in some language that their highlighter doesn't know about, you don't get an error message -- the code simply doesn't get highlighted. Because we don't recursively load dependencies for extensions, to test this, you will need to create a composer.local.json in $IP and add: { "extra": { "merge-plugin": { "include": [ "extensions/SyntaxHighlight_GeSHi/composer.json" ] } } } Then run `composer update`. Bug: T85794 Change-Id: I07446ec9893fae3d1e394f435d3d95cf8be6bc33
2015-06-16 03:52:58 +00:00
'dosini',
'dpatch',
'dtd',
'duby',
'duel',
'dylan',
'dylan-console',
'dylan-lid',
'dylan-repl',
Update pygments bundle to 2.1 Changelog: https://bitbucket.org/birkenfeld/pygments-main/raw/7614bf7/CHANGES Lots of new lexers: Emacs Lisp, Arduino, Modula-2 with multi-dialect support, Fortran fixed format, Archetype Definition language, Terraform, Jcl, Easytrieve, ParaSail, Boogie, Turtle, Fish Shell, Roboconf, Test Anything Protocol, Shen, Component Pascal, SuperCollider, Shell consoles (Tcsh, PowerShell, MSDOS), Elm and J, Crmsh, Praat, CSound, Ezhil, Thrift, QVT Operational, Hexdump, and CAmkES Configuration. Bug: T125581 Change-Id: Ie881af3d1dff23f08ccc9cbcf5f94a084fa561e1
2016-02-02 21:37:11 +00:00
'earl-grey',
'earlgrey',
'easytrieve',
Highlight using Pygments rather than Geshi GeSHi is unmaintained, lacks support for many popular modern languages, and suffers from deep architectural flaws, chief among them the inconsistent tokenization of different languages, each of which requires a custom stylesheet. Pygments is a well-maintained alternative. It is, by my count, the most popular syntax highlighting library around. It is BSD-licensed, actively maintained, and is widely used in PHP projects. To keep this easy to review, this change does not include update for l10n files, and it does not delete the geshi/ directory. I will do those in a separate patch. The chief change between this and the previous implementation is that errors result in the code block not being highlighted, as opposed to not being printed at all, having been replaced by an angry red error message. I think that is the right user experience. If you go to StackOverflow or GitHub and try to mark up your code block as being written in some language that their highlighter doesn't know about, you don't get an error message -- the code simply doesn't get highlighted. Because we don't recursively load dependencies for extensions, to test this, you will need to create a composer.local.json in $IP and add: { "extra": { "merge-plugin": { "include": [ "extensions/SyntaxHighlight_GeSHi/composer.json" ] } } } Then run `composer update`. Bug: T85794 Change-Id: I07446ec9893fae3d1e394f435d3d95cf8be6bc33
2015-06-16 03:52:58 +00:00
'ebnf',
'ec',
'ecl',
Update pygments bundle to 2.1 Changelog: https://bitbucket.org/birkenfeld/pygments-main/raw/7614bf7/CHANGES Lots of new lexers: Emacs Lisp, Arduino, Modula-2 with multi-dialect support, Fortran fixed format, Archetype Definition language, Terraform, Jcl, Easytrieve, ParaSail, Boogie, Turtle, Fish Shell, Roboconf, Test Anything Protocol, Shen, Component Pascal, SuperCollider, Shell consoles (Tcsh, PowerShell, MSDOS), Elm and J, Crmsh, Praat, CSound, Ezhil, Thrift, QVT Operational, Hexdump, and CAmkES Configuration. Bug: T125581 Change-Id: Ie881af3d1dff23f08ccc9cbcf5f94a084fa561e1
2016-02-02 21:37:11 +00:00
'eg',
Highlight using Pygments rather than Geshi GeSHi is unmaintained, lacks support for many popular modern languages, and suffers from deep architectural flaws, chief among them the inconsistent tokenization of different languages, each of which requires a custom stylesheet. Pygments is a well-maintained alternative. It is, by my count, the most popular syntax highlighting library around. It is BSD-licensed, actively maintained, and is widely used in PHP projects. To keep this easy to review, this change does not include update for l10n files, and it does not delete the geshi/ directory. I will do those in a separate patch. The chief change between this and the previous implementation is that errors result in the code block not being highlighted, as opposed to not being printed at all, having been replaced by an angry red error message. I think that is the right user experience. If you go to StackOverflow or GitHub and try to mark up your code block as being written in some language that their highlighter doesn't know about, you don't get an error message -- the code simply doesn't get highlighted. Because we don't recursively load dependencies for extensions, to test this, you will need to create a composer.local.json in $IP and add: { "extra": { "merge-plugin": { "include": [ "extensions/SyntaxHighlight_GeSHi/composer.json" ] } } } Then run `composer update`. Bug: T85794 Change-Id: I07446ec9893fae3d1e394f435d3d95cf8be6bc33
2015-06-16 03:52:58 +00:00
'eiffel',
'elisp',
'elixir',
Update pygments bundle to 2.1 Changelog: https://bitbucket.org/birkenfeld/pygments-main/raw/7614bf7/CHANGES Lots of new lexers: Emacs Lisp, Arduino, Modula-2 with multi-dialect support, Fortran fixed format, Archetype Definition language, Terraform, Jcl, Easytrieve, ParaSail, Boogie, Turtle, Fish Shell, Roboconf, Test Anything Protocol, Shen, Component Pascal, SuperCollider, Shell consoles (Tcsh, PowerShell, MSDOS), Elm and J, Crmsh, Praat, CSound, Ezhil, Thrift, QVT Operational, Hexdump, and CAmkES Configuration. Bug: T125581 Change-Id: Ie881af3d1dff23f08ccc9cbcf5f94a084fa561e1
2016-02-02 21:37:11 +00:00
'elm',
Highlight using Pygments rather than Geshi GeSHi is unmaintained, lacks support for many popular modern languages, and suffers from deep architectural flaws, chief among them the inconsistent tokenization of different languages, each of which requires a custom stylesheet. Pygments is a well-maintained alternative. It is, by my count, the most popular syntax highlighting library around. It is BSD-licensed, actively maintained, and is widely used in PHP projects. To keep this easy to review, this change does not include update for l10n files, and it does not delete the geshi/ directory. I will do those in a separate patch. The chief change between this and the previous implementation is that errors result in the code block not being highlighted, as opposed to not being printed at all, having been replaced by an angry red error message. I think that is the right user experience. If you go to StackOverflow or GitHub and try to mark up your code block as being written in some language that their highlighter doesn't know about, you don't get an error message -- the code simply doesn't get highlighted. Because we don't recursively load dependencies for extensions, to test this, you will need to create a composer.local.json in $IP and add: { "extra": { "merge-plugin": { "include": [ "extensions/SyntaxHighlight_GeSHi/composer.json" ] } } } Then run `composer update`. Bug: T85794 Change-Id: I07446ec9893fae3d1e394f435d3d95cf8be6bc33
2015-06-16 03:52:58 +00:00
'emacs',
Update pygments to 2.2 Notable changes: * Added new token types and lexing for magic methods and variables in Python and PHP. * Added a new token type for heredoc (and similar) string delimiters and lexing for them in C++, Perl, PHP, Postgresql and Ruby lexers. * Improved the CSS lexer. * Added Varnish config lexer Full changelog is found at: <https://bitbucket.org/birkenfeld/pygments-main/src/bc45808f83d5338e3116be91890e6ad15220ee45/CHANGES> Bug: T156573 Change-Id: I4dc1782f19881ba1294308e1cdea1b2e063f438a
2017-01-29 09:35:35 +00:00
'emacs-lisp',
Highlight using Pygments rather than Geshi GeSHi is unmaintained, lacks support for many popular modern languages, and suffers from deep architectural flaws, chief among them the inconsistent tokenization of different languages, each of which requires a custom stylesheet. Pygments is a well-maintained alternative. It is, by my count, the most popular syntax highlighting library around. It is BSD-licensed, actively maintained, and is widely used in PHP projects. To keep this easy to review, this change does not include update for l10n files, and it does not delete the geshi/ directory. I will do those in a separate patch. The chief change between this and the previous implementation is that errors result in the code block not being highlighted, as opposed to not being printed at all, having been replaced by an angry red error message. I think that is the right user experience. If you go to StackOverflow or GitHub and try to mark up your code block as being written in some language that their highlighter doesn't know about, you don't get an error message -- the code simply doesn't get highlighted. Because we don't recursively load dependencies for extensions, to test this, you will need to create a composer.local.json in $IP and add: { "extra": { "merge-plugin": { "include": [ "extensions/SyntaxHighlight_GeSHi/composer.json" ] } } } Then run `composer update`. Bug: T85794 Change-Id: I07446ec9893fae3d1e394f435d3d95cf8be6bc33
2015-06-16 03:52:58 +00:00
'erb',
'erl',
'erlang',
'evoque',
'ex',
'exs',
Update pygments to 2.2 Notable changes: * Added new token types and lexing for magic methods and variables in Python and PHP. * Added a new token type for heredoc (and similar) string delimiters and lexing for them in C++, Perl, PHP, Postgresql and Ruby lexers. * Improved the CSS lexer. * Added Varnish config lexer Full changelog is found at: <https://bitbucket.org/birkenfeld/pygments-main/src/bc45808f83d5338e3116be91890e6ad15220ee45/CHANGES> Bug: T156573 Change-Id: I4dc1782f19881ba1294308e1cdea1b2e063f438a
2017-01-29 09:35:35 +00:00
'extempore',
Update pygments bundle to 2.1 Changelog: https://bitbucket.org/birkenfeld/pygments-main/raw/7614bf7/CHANGES Lots of new lexers: Emacs Lisp, Arduino, Modula-2 with multi-dialect support, Fortran fixed format, Archetype Definition language, Terraform, Jcl, Easytrieve, ParaSail, Boogie, Turtle, Fish Shell, Roboconf, Test Anything Protocol, Shen, Component Pascal, SuperCollider, Shell consoles (Tcsh, PowerShell, MSDOS), Elm and J, Crmsh, Praat, CSound, Ezhil, Thrift, QVT Operational, Hexdump, and CAmkES Configuration. Bug: T125581 Change-Id: Ie881af3d1dff23f08ccc9cbcf5f94a084fa561e1
2016-02-02 21:37:11 +00:00
'ezhil',
Highlight using Pygments rather than Geshi GeSHi is unmaintained, lacks support for many popular modern languages, and suffers from deep architectural flaws, chief among them the inconsistent tokenization of different languages, each of which requires a custom stylesheet. Pygments is a well-maintained alternative. It is, by my count, the most popular syntax highlighting library around. It is BSD-licensed, actively maintained, and is widely used in PHP projects. To keep this easy to review, this change does not include update for l10n files, and it does not delete the geshi/ directory. I will do those in a separate patch. The chief change between this and the previous implementation is that errors result in the code block not being highlighted, as opposed to not being printed at all, having been replaced by an angry red error message. I think that is the right user experience. If you go to StackOverflow or GitHub and try to mark up your code block as being written in some language that their highlighter doesn't know about, you don't get an error message -- the code simply doesn't get highlighted. Because we don't recursively load dependencies for extensions, to test this, you will need to create a composer.local.json in $IP and add: { "extra": { "merge-plugin": { "include": [ "extensions/SyntaxHighlight_GeSHi/composer.json" ] } } } Then run `composer update`. Bug: T85794 Change-Id: I07446ec9893fae3d1e394f435d3d95cf8be6bc33
2015-06-16 03:52:58 +00:00
'factor',
'fan',
'fancy',
'felix',
Update pygments bundle to 2.1 Changelog: https://bitbucket.org/birkenfeld/pygments-main/raw/7614bf7/CHANGES Lots of new lexers: Emacs Lisp, Arduino, Modula-2 with multi-dialect support, Fortran fixed format, Archetype Definition language, Terraform, Jcl, Easytrieve, ParaSail, Boogie, Turtle, Fish Shell, Roboconf, Test Anything Protocol, Shen, Component Pascal, SuperCollider, Shell consoles (Tcsh, PowerShell, MSDOS), Elm and J, Crmsh, Praat, CSound, Ezhil, Thrift, QVT Operational, Hexdump, and CAmkES Configuration. Bug: T125581 Change-Id: Ie881af3d1dff23f08ccc9cbcf5f94a084fa561e1
2016-02-02 21:37:11 +00:00
'fish',
'fishshell',
Update pygments to 2.2 Notable changes: * Added new token types and lexing for magic methods and variables in Python and PHP. * Added a new token type for heredoc (and similar) string delimiters and lexing for them in C++, Perl, PHP, Postgresql and Ruby lexers. * Improved the CSS lexer. * Added Varnish config lexer Full changelog is found at: <https://bitbucket.org/birkenfeld/pygments-main/src/bc45808f83d5338e3116be91890e6ad15220ee45/CHANGES> Bug: T156573 Change-Id: I4dc1782f19881ba1294308e1cdea1b2e063f438a
2017-01-29 09:35:35 +00:00
'flatline',
Highlight using Pygments rather than Geshi GeSHi is unmaintained, lacks support for many popular modern languages, and suffers from deep architectural flaws, chief among them the inconsistent tokenization of different languages, each of which requires a custom stylesheet. Pygments is a well-maintained alternative. It is, by my count, the most popular syntax highlighting library around. It is BSD-licensed, actively maintained, and is widely used in PHP projects. To keep this easy to review, this change does not include update for l10n files, and it does not delete the geshi/ directory. I will do those in a separate patch. The chief change between this and the previous implementation is that errors result in the code block not being highlighted, as opposed to not being printed at all, having been replaced by an angry red error message. I think that is the right user experience. If you go to StackOverflow or GitHub and try to mark up your code block as being written in some language that their highlighter doesn't know about, you don't get an error message -- the code simply doesn't get highlighted. Because we don't recursively load dependencies for extensions, to test this, you will need to create a composer.local.json in $IP and add: { "extra": { "merge-plugin": { "include": [ "extensions/SyntaxHighlight_GeSHi/composer.json" ] } } } Then run `composer update`. Bug: T85794 Change-Id: I07446ec9893fae3d1e394f435d3d95cf8be6bc33
2015-06-16 03:52:58 +00:00
'flx',
Update pygments to 2.2 Notable changes: * Added new token types and lexing for magic methods and variables in Python and PHP. * Added a new token type for heredoc (and similar) string delimiters and lexing for them in C++, Perl, PHP, Postgresql and Ruby lexers. * Improved the CSS lexer. * Added Varnish config lexer Full changelog is found at: <https://bitbucket.org/birkenfeld/pygments-main/src/bc45808f83d5338e3116be91890e6ad15220ee45/CHANGES> Bug: T156573 Change-Id: I4dc1782f19881ba1294308e1cdea1b2e063f438a
2017-01-29 09:35:35 +00:00
'forth',
Highlight using Pygments rather than Geshi GeSHi is unmaintained, lacks support for many popular modern languages, and suffers from deep architectural flaws, chief among them the inconsistent tokenization of different languages, each of which requires a custom stylesheet. Pygments is a well-maintained alternative. It is, by my count, the most popular syntax highlighting library around. It is BSD-licensed, actively maintained, and is widely used in PHP projects. To keep this easy to review, this change does not include update for l10n files, and it does not delete the geshi/ directory. I will do those in a separate patch. The chief change between this and the previous implementation is that errors result in the code block not being highlighted, as opposed to not being printed at all, having been replaced by an angry red error message. I think that is the right user experience. If you go to StackOverflow or GitHub and try to mark up your code block as being written in some language that their highlighter doesn't know about, you don't get an error message -- the code simply doesn't get highlighted. Because we don't recursively load dependencies for extensions, to test this, you will need to create a composer.local.json in $IP and add: { "extra": { "merge-plugin": { "include": [ "extensions/SyntaxHighlight_GeSHi/composer.json" ] } } } Then run `composer update`. Bug: T85794 Change-Id: I07446ec9893fae3d1e394f435d3d95cf8be6bc33
2015-06-16 03:52:58 +00:00
'fortran',
Update pygments bundle to 2.1 Changelog: https://bitbucket.org/birkenfeld/pygments-main/raw/7614bf7/CHANGES Lots of new lexers: Emacs Lisp, Arduino, Modula-2 with multi-dialect support, Fortran fixed format, Archetype Definition language, Terraform, Jcl, Easytrieve, ParaSail, Boogie, Turtle, Fish Shell, Roboconf, Test Anything Protocol, Shen, Component Pascal, SuperCollider, Shell consoles (Tcsh, PowerShell, MSDOS), Elm and J, Crmsh, Praat, CSound, Ezhil, Thrift, QVT Operational, Hexdump, and CAmkES Configuration. Bug: T125581 Change-Id: Ie881af3d1dff23f08ccc9cbcf5f94a084fa561e1
2016-02-02 21:37:11 +00:00
'fortranfixed',
Highlight using Pygments rather than Geshi GeSHi is unmaintained, lacks support for many popular modern languages, and suffers from deep architectural flaws, chief among them the inconsistent tokenization of different languages, each of which requires a custom stylesheet. Pygments is a well-maintained alternative. It is, by my count, the most popular syntax highlighting library around. It is BSD-licensed, actively maintained, and is widely used in PHP projects. To keep this easy to review, this change does not include update for l10n files, and it does not delete the geshi/ directory. I will do those in a separate patch. The chief change between this and the previous implementation is that errors result in the code block not being highlighted, as opposed to not being printed at all, having been replaced by an angry red error message. I think that is the right user experience. If you go to StackOverflow or GitHub and try to mark up your code block as being written in some language that their highlighter doesn't know about, you don't get an error message -- the code simply doesn't get highlighted. Because we don't recursively load dependencies for extensions, to test this, you will need to create a composer.local.json in $IP and add: { "extra": { "merge-plugin": { "include": [ "extensions/SyntaxHighlight_GeSHi/composer.json" ] } } } Then run `composer update`. Bug: T85794 Change-Id: I07446ec9893fae3d1e394f435d3d95cf8be6bc33
2015-06-16 03:52:58 +00:00
'foxpro',
'fsharp',
'fy',
'gap',
'gas',
'gawk',
'genshi',
'genshitext',
'gherkin',
'glsl',
'gnuplot',
'go',
'golo',
'gooddata-cl',
'gosu',
'groff',
'groovy',
'gst',
'haml',
'handlebars',
'haskell',
'haxe',
'haxeml',
Update pygments bundle to 2.1 Changelog: https://bitbucket.org/birkenfeld/pygments-main/raw/7614bf7/CHANGES Lots of new lexers: Emacs Lisp, Arduino, Modula-2 with multi-dialect support, Fortran fixed format, Archetype Definition language, Terraform, Jcl, Easytrieve, ParaSail, Boogie, Turtle, Fish Shell, Roboconf, Test Anything Protocol, Shen, Component Pascal, SuperCollider, Shell consoles (Tcsh, PowerShell, MSDOS), Elm and J, Crmsh, Praat, CSound, Ezhil, Thrift, QVT Operational, Hexdump, and CAmkES Configuration. Bug: T125581 Change-Id: Ie881af3d1dff23f08ccc9cbcf5f94a084fa561e1
2016-02-02 21:37:11 +00:00
'hexdump',
Highlight using Pygments rather than Geshi GeSHi is unmaintained, lacks support for many popular modern languages, and suffers from deep architectural flaws, chief among them the inconsistent tokenization of different languages, each of which requires a custom stylesheet. Pygments is a well-maintained alternative. It is, by my count, the most popular syntax highlighting library around. It is BSD-licensed, actively maintained, and is widely used in PHP projects. To keep this easy to review, this change does not include update for l10n files, and it does not delete the geshi/ directory. I will do those in a separate patch. The chief change between this and the previous implementation is that errors result in the code block not being highlighted, as opposed to not being printed at all, having been replaced by an angry red error message. I think that is the right user experience. If you go to StackOverflow or GitHub and try to mark up your code block as being written in some language that their highlighter doesn't know about, you don't get an error message -- the code simply doesn't get highlighted. Because we don't recursively load dependencies for extensions, to test this, you will need to create a composer.local.json in $IP and add: { "extra": { "merge-plugin": { "include": [ "extensions/SyntaxHighlight_GeSHi/composer.json" ] } } } Then run `composer update`. Bug: T85794 Change-Id: I07446ec9893fae3d1e394f435d3d95cf8be6bc33
2015-06-16 03:52:58 +00:00
'hs',
Update pygments to 2.2 Notable changes: * Added new token types and lexing for magic methods and variables in Python and PHP. * Added a new token type for heredoc (and similar) string delimiters and lexing for them in C++, Perl, PHP, Postgresql and Ruby lexers. * Improved the CSS lexer. * Added Varnish config lexer Full changelog is found at: <https://bitbucket.org/birkenfeld/pygments-main/src/bc45808f83d5338e3116be91890e6ad15220ee45/CHANGES> Bug: T156573 Change-Id: I4dc1782f19881ba1294308e1cdea1b2e063f438a
2017-01-29 09:35:35 +00:00
'hsa',
'hsail',
Highlight using Pygments rather than Geshi GeSHi is unmaintained, lacks support for many popular modern languages, and suffers from deep architectural flaws, chief among them the inconsistent tokenization of different languages, each of which requires a custom stylesheet. Pygments is a well-maintained alternative. It is, by my count, the most popular syntax highlighting library around. It is BSD-licensed, actively maintained, and is widely used in PHP projects. To keep this easy to review, this change does not include update for l10n files, and it does not delete the geshi/ directory. I will do those in a separate patch. The chief change between this and the previous implementation is that errors result in the code block not being highlighted, as opposed to not being printed at all, having been replaced by an angry red error message. I think that is the right user experience. If you go to StackOverflow or GitHub and try to mark up your code block as being written in some language that their highlighter doesn't know about, you don't get an error message -- the code simply doesn't get highlighted. Because we don't recursively load dependencies for extensions, to test this, you will need to create a composer.local.json in $IP and add: { "extra": { "merge-plugin": { "include": [ "extensions/SyntaxHighlight_GeSHi/composer.json" ] } } } Then run `composer update`. Bug: T85794 Change-Id: I07446ec9893fae3d1e394f435d3d95cf8be6bc33
2015-06-16 03:52:58 +00:00
'html',
'html+cheetah',
'html+django',
'html+erb',
'html+evoque',
'html+genshi',
'html+handlebars',
'html+jinja',
'html+kid',
'html+lasso',
'html+mako',
'html+myghty',
Update pygments to 2.2 Notable changes: * Added new token types and lexing for magic methods and variables in Python and PHP. * Added a new token type for heredoc (and similar) string delimiters and lexing for them in C++, Perl, PHP, Postgresql and Ruby lexers. * Improved the CSS lexer. * Added Varnish config lexer Full changelog is found at: <https://bitbucket.org/birkenfeld/pygments-main/src/bc45808f83d5338e3116be91890e6ad15220ee45/CHANGES> Bug: T156573 Change-Id: I4dc1782f19881ba1294308e1cdea1b2e063f438a
2017-01-29 09:35:35 +00:00
'html+ng2',
Highlight using Pygments rather than Geshi GeSHi is unmaintained, lacks support for many popular modern languages, and suffers from deep architectural flaws, chief among them the inconsistent tokenization of different languages, each of which requires a custom stylesheet. Pygments is a well-maintained alternative. It is, by my count, the most popular syntax highlighting library around. It is BSD-licensed, actively maintained, and is widely used in PHP projects. To keep this easy to review, this change does not include update for l10n files, and it does not delete the geshi/ directory. I will do those in a separate patch. The chief change between this and the previous implementation is that errors result in the code block not being highlighted, as opposed to not being printed at all, having been replaced by an angry red error message. I think that is the right user experience. If you go to StackOverflow or GitHub and try to mark up your code block as being written in some language that their highlighter doesn't know about, you don't get an error message -- the code simply doesn't get highlighted. Because we don't recursively load dependencies for extensions, to test this, you will need to create a composer.local.json in $IP and add: { "extra": { "merge-plugin": { "include": [ "extensions/SyntaxHighlight_GeSHi/composer.json" ] } } } Then run `composer update`. Bug: T85794 Change-Id: I07446ec9893fae3d1e394f435d3d95cf8be6bc33
2015-06-16 03:52:58 +00:00
'html+php',
'html+ruby',
'html+smarty',
'html+spitfire',
'html+twig',
'html+velocity',
'htmlcheetah',
'htmldjango',
'http',
'hx',
'hxml',
'hxsl',
'hy',
'hybris',
'hylang',
'i6',
'i6t',
'i7',
'idl',
Update pygments bundle to 2.1 Changelog: https://bitbucket.org/birkenfeld/pygments-main/raw/7614bf7/CHANGES Lots of new lexers: Emacs Lisp, Arduino, Modula-2 with multi-dialect support, Fortran fixed format, Archetype Definition language, Terraform, Jcl, Easytrieve, ParaSail, Boogie, Turtle, Fish Shell, Roboconf, Test Anything Protocol, Shen, Component Pascal, SuperCollider, Shell consoles (Tcsh, PowerShell, MSDOS), Elm and J, Crmsh, Praat, CSound, Ezhil, Thrift, QVT Operational, Hexdump, and CAmkES Configuration. Bug: T125581 Change-Id: Ie881af3d1dff23f08ccc9cbcf5f94a084fa561e1
2016-02-02 21:37:11 +00:00
'idl4',
Highlight using Pygments rather than Geshi GeSHi is unmaintained, lacks support for many popular modern languages, and suffers from deep architectural flaws, chief among them the inconsistent tokenization of different languages, each of which requires a custom stylesheet. Pygments is a well-maintained alternative. It is, by my count, the most popular syntax highlighting library around. It is BSD-licensed, actively maintained, and is widely used in PHP projects. To keep this easy to review, this change does not include update for l10n files, and it does not delete the geshi/ directory. I will do those in a separate patch. The chief change between this and the previous implementation is that errors result in the code block not being highlighted, as opposed to not being printed at all, having been replaced by an angry red error message. I think that is the right user experience. If you go to StackOverflow or GitHub and try to mark up your code block as being written in some language that their highlighter doesn't know about, you don't get an error message -- the code simply doesn't get highlighted. Because we don't recursively load dependencies for extensions, to test this, you will need to create a composer.local.json in $IP and add: { "extra": { "merge-plugin": { "include": [ "extensions/SyntaxHighlight_GeSHi/composer.json" ] } } } Then run `composer update`. Bug: T85794 Change-Id: I07446ec9893fae3d1e394f435d3d95cf8be6bc33
2015-06-16 03:52:58 +00:00
'idr',
'idris',
'iex',
'igor',
'igorpro',
'ik',
'inform6',
'inform7',
'ini',
'io',
'ioke',
'irb',
'irc',
'isabelle',
Update pygments bundle to 2.1 Changelog: https://bitbucket.org/birkenfeld/pygments-main/raw/7614bf7/CHANGES Lots of new lexers: Emacs Lisp, Arduino, Modula-2 with multi-dialect support, Fortran fixed format, Archetype Definition language, Terraform, Jcl, Easytrieve, ParaSail, Boogie, Turtle, Fish Shell, Roboconf, Test Anything Protocol, Shen, Component Pascal, SuperCollider, Shell consoles (Tcsh, PowerShell, MSDOS), Elm and J, Crmsh, Praat, CSound, Ezhil, Thrift, QVT Operational, Hexdump, and CAmkES Configuration. Bug: T125581 Change-Id: Ie881af3d1dff23f08ccc9cbcf5f94a084fa561e1
2016-02-02 21:37:11 +00:00
'j',
Highlight using Pygments rather than Geshi GeSHi is unmaintained, lacks support for many popular modern languages, and suffers from deep architectural flaws, chief among them the inconsistent tokenization of different languages, each of which requires a custom stylesheet. Pygments is a well-maintained alternative. It is, by my count, the most popular syntax highlighting library around. It is BSD-licensed, actively maintained, and is widely used in PHP projects. To keep this easy to review, this change does not include update for l10n files, and it does not delete the geshi/ directory. I will do those in a separate patch. The chief change between this and the previous implementation is that errors result in the code block not being highlighted, as opposed to not being printed at all, having been replaced by an angry red error message. I think that is the right user experience. If you go to StackOverflow or GitHub and try to mark up your code block as being written in some language that their highlighter doesn't know about, you don't get an error message -- the code simply doesn't get highlighted. Because we don't recursively load dependencies for extensions, to test this, you will need to create a composer.local.json in $IP and add: { "extra": { "merge-plugin": { "include": [ "extensions/SyntaxHighlight_GeSHi/composer.json" ] } } } Then run `composer update`. Bug: T85794 Change-Id: I07446ec9893fae3d1e394f435d3d95cf8be6bc33
2015-06-16 03:52:58 +00:00
'jade',
'jags',
'jasmin',
'jasminxt',
'java',
'javascript',
'javascript+cheetah',
'javascript+django',
'javascript+erb',
'javascript+genshi',
'javascript+genshitext',
'javascript+jinja',
'javascript+lasso',
'javascript+mako',
'javascript+mozpreproc',
'javascript+myghty',
'javascript+php',
'javascript+ruby',
'javascript+smarty',
'javascript+spitfire',
'jbst',
Update pygments bundle to 2.1 Changelog: https://bitbucket.org/birkenfeld/pygments-main/raw/7614bf7/CHANGES Lots of new lexers: Emacs Lisp, Arduino, Modula-2 with multi-dialect support, Fortran fixed format, Archetype Definition language, Terraform, Jcl, Easytrieve, ParaSail, Boogie, Turtle, Fish Shell, Roboconf, Test Anything Protocol, Shen, Component Pascal, SuperCollider, Shell consoles (Tcsh, PowerShell, MSDOS), Elm and J, Crmsh, Praat, CSound, Ezhil, Thrift, QVT Operational, Hexdump, and CAmkES Configuration. Bug: T125581 Change-Id: Ie881af3d1dff23f08ccc9cbcf5f94a084fa561e1
2016-02-02 21:37:11 +00:00
'jcl',
Highlight using Pygments rather than Geshi GeSHi is unmaintained, lacks support for many popular modern languages, and suffers from deep architectural flaws, chief among them the inconsistent tokenization of different languages, each of which requires a custom stylesheet. Pygments is a well-maintained alternative. It is, by my count, the most popular syntax highlighting library around. It is BSD-licensed, actively maintained, and is widely used in PHP projects. To keep this easy to review, this change does not include update for l10n files, and it does not delete the geshi/ directory. I will do those in a separate patch. The chief change between this and the previous implementation is that errors result in the code block not being highlighted, as opposed to not being printed at all, having been replaced by an angry red error message. I think that is the right user experience. If you go to StackOverflow or GitHub and try to mark up your code block as being written in some language that their highlighter doesn't know about, you don't get an error message -- the code simply doesn't get highlighted. Because we don't recursively load dependencies for extensions, to test this, you will need to create a composer.local.json in $IP and add: { "extra": { "merge-plugin": { "include": [ "extensions/SyntaxHighlight_GeSHi/composer.json" ] } } } Then run `composer update`. Bug: T85794 Change-Id: I07446ec9893fae3d1e394f435d3d95cf8be6bc33
2015-06-16 03:52:58 +00:00
'jinja',
'jl',
'jlcon',
'jproperties',
'js',
'js+cheetah',
'js+django',
'js+erb',
'js+genshi',
'js+genshitext',
'js+jinja',
'js+lasso',
'js+mako',
'js+myghty',
'js+php',
'js+ruby',
'js+smarty',
'js+spitfire',
Update pygments to 2.2 Notable changes: * Added new token types and lexing for magic methods and variables in Python and PHP. * Added a new token type for heredoc (and similar) string delimiters and lexing for them in C++, Perl, PHP, Postgresql and Ruby lexers. * Improved the CSS lexer. * Added Varnish config lexer Full changelog is found at: <https://bitbucket.org/birkenfeld/pygments-main/src/bc45808f83d5338e3116be91890e6ad15220ee45/CHANGES> Bug: T156573 Change-Id: I4dc1782f19881ba1294308e1cdea1b2e063f438a
2017-01-29 09:35:35 +00:00
'jsgf',
Highlight using Pygments rather than Geshi GeSHi is unmaintained, lacks support for many popular modern languages, and suffers from deep architectural flaws, chief among them the inconsistent tokenization of different languages, each of which requires a custom stylesheet. Pygments is a well-maintained alternative. It is, by my count, the most popular syntax highlighting library around. It is BSD-licensed, actively maintained, and is widely used in PHP projects. To keep this easy to review, this change does not include update for l10n files, and it does not delete the geshi/ directory. I will do those in a separate patch. The chief change between this and the previous implementation is that errors result in the code block not being highlighted, as opposed to not being printed at all, having been replaced by an angry red error message. I think that is the right user experience. If you go to StackOverflow or GitHub and try to mark up your code block as being written in some language that their highlighter doesn't know about, you don't get an error message -- the code simply doesn't get highlighted. Because we don't recursively load dependencies for extensions, to test this, you will need to create a composer.local.json in $IP and add: { "extra": { "merge-plugin": { "include": [ "extensions/SyntaxHighlight_GeSHi/composer.json" ] } } } Then run `composer update`. Bug: T85794 Change-Id: I07446ec9893fae3d1e394f435d3d95cf8be6bc33
2015-06-16 03:52:58 +00:00
'json',
'json-ld',
Update pygments to 2.2 Notable changes: * Added new token types and lexing for magic methods and variables in Python and PHP. * Added a new token type for heredoc (and similar) string delimiters and lexing for them in C++, Perl, PHP, Postgresql and Ruby lexers. * Improved the CSS lexer. * Added Varnish config lexer Full changelog is found at: <https://bitbucket.org/birkenfeld/pygments-main/src/bc45808f83d5338e3116be91890e6ad15220ee45/CHANGES> Bug: T156573 Change-Id: I4dc1782f19881ba1294308e1cdea1b2e063f438a
2017-01-29 09:35:35 +00:00
'json-object',
Highlight using Pygments rather than Geshi GeSHi is unmaintained, lacks support for many popular modern languages, and suffers from deep architectural flaws, chief among them the inconsistent tokenization of different languages, each of which requires a custom stylesheet. Pygments is a well-maintained alternative. It is, by my count, the most popular syntax highlighting library around. It is BSD-licensed, actively maintained, and is widely used in PHP projects. To keep this easy to review, this change does not include update for l10n files, and it does not delete the geshi/ directory. I will do those in a separate patch. The chief change between this and the previous implementation is that errors result in the code block not being highlighted, as opposed to not being printed at all, having been replaced by an angry red error message. I think that is the right user experience. If you go to StackOverflow or GitHub and try to mark up your code block as being written in some language that their highlighter doesn't know about, you don't get an error message -- the code simply doesn't get highlighted. Because we don't recursively load dependencies for extensions, to test this, you will need to create a composer.local.json in $IP and add: { "extra": { "merge-plugin": { "include": [ "extensions/SyntaxHighlight_GeSHi/composer.json" ] } } } Then run `composer update`. Bug: T85794 Change-Id: I07446ec9893fae3d1e394f435d3d95cf8be6bc33
2015-06-16 03:52:58 +00:00
'jsonld',
'jsonml+bst',
'jsp',
'julia',
Update pygments to 2.2 Notable changes: * Added new token types and lexing for magic methods and variables in Python and PHP. * Added a new token type for heredoc (and similar) string delimiters and lexing for them in C++, Perl, PHP, Postgresql and Ruby lexers. * Improved the CSS lexer. * Added Varnish config lexer Full changelog is found at: <https://bitbucket.org/birkenfeld/pygments-main/src/bc45808f83d5338e3116be91890e6ad15220ee45/CHANGES> Bug: T156573 Change-Id: I4dc1782f19881ba1294308e1cdea1b2e063f438a
2017-01-29 09:35:35 +00:00
'juttle',
Highlight using Pygments rather than Geshi GeSHi is unmaintained, lacks support for many popular modern languages, and suffers from deep architectural flaws, chief among them the inconsistent tokenization of different languages, each of which requires a custom stylesheet. Pygments is a well-maintained alternative. It is, by my count, the most popular syntax highlighting library around. It is BSD-licensed, actively maintained, and is widely used in PHP projects. To keep this easy to review, this change does not include update for l10n files, and it does not delete the geshi/ directory. I will do those in a separate patch. The chief change between this and the previous implementation is that errors result in the code block not being highlighted, as opposed to not being printed at all, having been replaced by an angry red error message. I think that is the right user experience. If you go to StackOverflow or GitHub and try to mark up your code block as being written in some language that their highlighter doesn't know about, you don't get an error message -- the code simply doesn't get highlighted. Because we don't recursively load dependencies for extensions, to test this, you will need to create a composer.local.json in $IP and add: { "extra": { "merge-plugin": { "include": [ "extensions/SyntaxHighlight_GeSHi/composer.json" ] } } } Then run `composer update`. Bug: T85794 Change-Id: I07446ec9893fae3d1e394f435d3d95cf8be6bc33
2015-06-16 03:52:58 +00:00
'kal',
'kconfig',
'kernel-config',
'kid',
'koka',
'kotlin',
'ksh',
'lagda',
'lasso',
'lassoscript',
'latex',
'lcry',
'lcryptol',
'lean',
Update pygments bundle to 2.1 Changelog: https://bitbucket.org/birkenfeld/pygments-main/raw/7614bf7/CHANGES Lots of new lexers: Emacs Lisp, Arduino, Modula-2 with multi-dialect support, Fortran fixed format, Archetype Definition language, Terraform, Jcl, Easytrieve, ParaSail, Boogie, Turtle, Fish Shell, Roboconf, Test Anything Protocol, Shen, Component Pascal, SuperCollider, Shell consoles (Tcsh, PowerShell, MSDOS), Elm and J, Crmsh, Praat, CSound, Ezhil, Thrift, QVT Operational, Hexdump, and CAmkES Configuration. Bug: T125581 Change-Id: Ie881af3d1dff23f08ccc9cbcf5f94a084fa561e1
2016-02-02 21:37:11 +00:00
'less',
Highlight using Pygments rather than Geshi GeSHi is unmaintained, lacks support for many popular modern languages, and suffers from deep architectural flaws, chief among them the inconsistent tokenization of different languages, each of which requires a custom stylesheet. Pygments is a well-maintained alternative. It is, by my count, the most popular syntax highlighting library around. It is BSD-licensed, actively maintained, and is widely used in PHP projects. To keep this easy to review, this change does not include update for l10n files, and it does not delete the geshi/ directory. I will do those in a separate patch. The chief change between this and the previous implementation is that errors result in the code block not being highlighted, as opposed to not being printed at all, having been replaced by an angry red error message. I think that is the right user experience. If you go to StackOverflow or GitHub and try to mark up your code block as being written in some language that their highlighter doesn't know about, you don't get an error message -- the code simply doesn't get highlighted. Because we don't recursively load dependencies for extensions, to test this, you will need to create a composer.local.json in $IP and add: { "extra": { "merge-plugin": { "include": [ "extensions/SyntaxHighlight_GeSHi/composer.json" ] } } } Then run `composer update`. Bug: T85794 Change-Id: I07446ec9893fae3d1e394f435d3d95cf8be6bc33
2015-06-16 03:52:58 +00:00
'lhaskell',
'lhs',
'lid',
'lidr',
'lidris',
'lighttpd',
'lighty',
'limbo',
'linux-config',
'liquid',
'lisp',
'literate-agda',
'literate-cryptol',
'literate-haskell',
'literate-idris',
'live-script',
'livescript',
'llvm',
'logos',
'logtalk',
'lsl',
'lua',
'm2',
'make',
'makefile',
'mako',
'man',
'maql',
'mask',
'mason',
'mathematica',
'matlab',
'matlabsession',
'mawk',
Update pygments to 2.2 Notable changes: * Added new token types and lexing for magic methods and variables in Python and PHP. * Added a new token type for heredoc (and similar) string delimiters and lexing for them in C++, Perl, PHP, Postgresql and Ruby lexers. * Improved the CSS lexer. * Added Varnish config lexer Full changelog is found at: <https://bitbucket.org/birkenfeld/pygments-main/src/bc45808f83d5338e3116be91890e6ad15220ee45/CHANGES> Bug: T156573 Change-Id: I4dc1782f19881ba1294308e1cdea1b2e063f438a
2017-01-29 09:35:35 +00:00
'md',
Highlight using Pygments rather than Geshi GeSHi is unmaintained, lacks support for many popular modern languages, and suffers from deep architectural flaws, chief among them the inconsistent tokenization of different languages, each of which requires a custom stylesheet. Pygments is a well-maintained alternative. It is, by my count, the most popular syntax highlighting library around. It is BSD-licensed, actively maintained, and is widely used in PHP projects. To keep this easy to review, this change does not include update for l10n files, and it does not delete the geshi/ directory. I will do those in a separate patch. The chief change between this and the previous implementation is that errors result in the code block not being highlighted, as opposed to not being printed at all, having been replaced by an angry red error message. I think that is the right user experience. If you go to StackOverflow or GitHub and try to mark up your code block as being written in some language that their highlighter doesn't know about, you don't get an error message -- the code simply doesn't get highlighted. Because we don't recursively load dependencies for extensions, to test this, you will need to create a composer.local.json in $IP and add: { "extra": { "merge-plugin": { "include": [ "extensions/SyntaxHighlight_GeSHi/composer.json" ] } } } Then run `composer update`. Bug: T85794 Change-Id: I07446ec9893fae3d1e394f435d3d95cf8be6bc33
2015-06-16 03:52:58 +00:00
'menuconfig',
'mf',
'minid',
'mma',
'modelica',
'modula2',
'moin',
'monkey',
Update pygments to 2.2 Notable changes: * Added new token types and lexing for magic methods and variables in Python and PHP. * Added a new token type for heredoc (and similar) string delimiters and lexing for them in C++, Perl, PHP, Postgresql and Ruby lexers. * Improved the CSS lexer. * Added Varnish config lexer Full changelog is found at: <https://bitbucket.org/birkenfeld/pygments-main/src/bc45808f83d5338e3116be91890e6ad15220ee45/CHANGES> Bug: T156573 Change-Id: I4dc1782f19881ba1294308e1cdea1b2e063f438a
2017-01-29 09:35:35 +00:00
'monte',
Highlight using Pygments rather than Geshi GeSHi is unmaintained, lacks support for many popular modern languages, and suffers from deep architectural flaws, chief among them the inconsistent tokenization of different languages, each of which requires a custom stylesheet. Pygments is a well-maintained alternative. It is, by my count, the most popular syntax highlighting library around. It is BSD-licensed, actively maintained, and is widely used in PHP projects. To keep this easy to review, this change does not include update for l10n files, and it does not delete the geshi/ directory. I will do those in a separate patch. The chief change between this and the previous implementation is that errors result in the code block not being highlighted, as opposed to not being printed at all, having been replaced by an angry red error message. I think that is the right user experience. If you go to StackOverflow or GitHub and try to mark up your code block as being written in some language that their highlighter doesn't know about, you don't get an error message -- the code simply doesn't get highlighted. Because we don't recursively load dependencies for extensions, to test this, you will need to create a composer.local.json in $IP and add: { "extra": { "merge-plugin": { "include": [ "extensions/SyntaxHighlight_GeSHi/composer.json" ] } } } Then run `composer update`. Bug: T85794 Change-Id: I07446ec9893fae3d1e394f435d3d95cf8be6bc33
2015-06-16 03:52:58 +00:00
'moo',
'moocode',
'moon',
'moonscript',
'mozhashpreproc',
'mozpercentpreproc',
'mq4',
'mq5',
'mql',
'mql4',
'mql5',
'msc',
'mscgen',
'mupad',
'mxml',
'myghty',
'mysql',
'nasm',
'nawk',
'nb',
Update pygments to 2.2 Notable changes: * Added new token types and lexing for magic methods and variables in Python and PHP. * Added a new token type for heredoc (and similar) string delimiters and lexing for them in C++, Perl, PHP, Postgresql and Ruby lexers. * Improved the CSS lexer. * Added Varnish config lexer Full changelog is found at: <https://bitbucket.org/birkenfeld/pygments-main/src/bc45808f83d5338e3116be91890e6ad15220ee45/CHANGES> Bug: T156573 Change-Id: I4dc1782f19881ba1294308e1cdea1b2e063f438a
2017-01-29 09:35:35 +00:00
'ncl',
Highlight using Pygments rather than Geshi GeSHi is unmaintained, lacks support for many popular modern languages, and suffers from deep architectural flaws, chief among them the inconsistent tokenization of different languages, each of which requires a custom stylesheet. Pygments is a well-maintained alternative. It is, by my count, the most popular syntax highlighting library around. It is BSD-licensed, actively maintained, and is widely used in PHP projects. To keep this easy to review, this change does not include update for l10n files, and it does not delete the geshi/ directory. I will do those in a separate patch. The chief change between this and the previous implementation is that errors result in the code block not being highlighted, as opposed to not being printed at all, having been replaced by an angry red error message. I think that is the right user experience. If you go to StackOverflow or GitHub and try to mark up your code block as being written in some language that their highlighter doesn't know about, you don't get an error message -- the code simply doesn't get highlighted. Because we don't recursively load dependencies for extensions, to test this, you will need to create a composer.local.json in $IP and add: { "extra": { "merge-plugin": { "include": [ "extensions/SyntaxHighlight_GeSHi/composer.json" ] } } } Then run `composer update`. Bug: T85794 Change-Id: I07446ec9893fae3d1e394f435d3d95cf8be6bc33
2015-06-16 03:52:58 +00:00
'nemerle',
'nesc',
'newlisp',
'newspeak',
Update pygments to 2.2 Notable changes: * Added new token types and lexing for magic methods and variables in Python and PHP. * Added a new token type for heredoc (and similar) string delimiters and lexing for them in C++, Perl, PHP, Postgresql and Ruby lexers. * Improved the CSS lexer. * Added Varnish config lexer Full changelog is found at: <https://bitbucket.org/birkenfeld/pygments-main/src/bc45808f83d5338e3116be91890e6ad15220ee45/CHANGES> Bug: T156573 Change-Id: I4dc1782f19881ba1294308e1cdea1b2e063f438a
2017-01-29 09:35:35 +00:00
'ng2',
Highlight using Pygments rather than Geshi GeSHi is unmaintained, lacks support for many popular modern languages, and suffers from deep architectural flaws, chief among them the inconsistent tokenization of different languages, each of which requires a custom stylesheet. Pygments is a well-maintained alternative. It is, by my count, the most popular syntax highlighting library around. It is BSD-licensed, actively maintained, and is widely used in PHP projects. To keep this easy to review, this change does not include update for l10n files, and it does not delete the geshi/ directory. I will do those in a separate patch. The chief change between this and the previous implementation is that errors result in the code block not being highlighted, as opposed to not being printed at all, having been replaced by an angry red error message. I think that is the right user experience. If you go to StackOverflow or GitHub and try to mark up your code block as being written in some language that their highlighter doesn't know about, you don't get an error message -- the code simply doesn't get highlighted. Because we don't recursively load dependencies for extensions, to test this, you will need to create a composer.local.json in $IP and add: { "extra": { "merge-plugin": { "include": [ "extensions/SyntaxHighlight_GeSHi/composer.json" ] } } } Then run `composer update`. Bug: T85794 Change-Id: I07446ec9893fae3d1e394f435d3d95cf8be6bc33
2015-06-16 03:52:58 +00:00
'nginx',
'nim',
'nimrod',
'nit',
'nix',
'nixos',
'nroff',
'nsh',
'nsi',
'nsis',
'numpy',
Update pygments to 2.2 Notable changes: * Added new token types and lexing for magic methods and variables in Python and PHP. * Added a new token type for heredoc (and similar) string delimiters and lexing for them in C++, Perl, PHP, Postgresql and Ruby lexers. * Improved the CSS lexer. * Added Varnish config lexer Full changelog is found at: <https://bitbucket.org/birkenfeld/pygments-main/src/bc45808f83d5338e3116be91890e6ad15220ee45/CHANGES> Bug: T156573 Change-Id: I4dc1782f19881ba1294308e1cdea1b2e063f438a
2017-01-29 09:35:35 +00:00
'nusmv',
Highlight using Pygments rather than Geshi GeSHi is unmaintained, lacks support for many popular modern languages, and suffers from deep architectural flaws, chief among them the inconsistent tokenization of different languages, each of which requires a custom stylesheet. Pygments is a well-maintained alternative. It is, by my count, the most popular syntax highlighting library around. It is BSD-licensed, actively maintained, and is widely used in PHP projects. To keep this easy to review, this change does not include update for l10n files, and it does not delete the geshi/ directory. I will do those in a separate patch. The chief change between this and the previous implementation is that errors result in the code block not being highlighted, as opposed to not being printed at all, having been replaced by an angry red error message. I think that is the right user experience. If you go to StackOverflow or GitHub and try to mark up your code block as being written in some language that their highlighter doesn't know about, you don't get an error message -- the code simply doesn't get highlighted. Because we don't recursively load dependencies for extensions, to test this, you will need to create a composer.local.json in $IP and add: { "extra": { "merge-plugin": { "include": [ "extensions/SyntaxHighlight_GeSHi/composer.json" ] } } } Then run `composer update`. Bug: T85794 Change-Id: I07446ec9893fae3d1e394f435d3d95cf8be6bc33
2015-06-16 03:52:58 +00:00
'obj-c',
'obj-c++',
'obj-j',
'objc',
'objc++',
'objdump',
'objdump-nasm',
'objective-c',
'objective-c++',
'objective-j',
'objectivec',
'objectivec++',
'objectivej',
'objectpascal',
'objj',
'ocaml',
'octave',
Update pygments bundle to 2.1 Changelog: https://bitbucket.org/birkenfeld/pygments-main/raw/7614bf7/CHANGES Lots of new lexers: Emacs Lisp, Arduino, Modula-2 with multi-dialect support, Fortran fixed format, Archetype Definition language, Terraform, Jcl, Easytrieve, ParaSail, Boogie, Turtle, Fish Shell, Roboconf, Test Anything Protocol, Shen, Component Pascal, SuperCollider, Shell consoles (Tcsh, PowerShell, MSDOS), Elm and J, Crmsh, Praat, CSound, Ezhil, Thrift, QVT Operational, Hexdump, and CAmkES Configuration. Bug: T125581 Change-Id: Ie881af3d1dff23f08ccc9cbcf5f94a084fa561e1
2016-02-02 21:37:11 +00:00
'odin',
Highlight using Pygments rather than Geshi GeSHi is unmaintained, lacks support for many popular modern languages, and suffers from deep architectural flaws, chief among them the inconsistent tokenization of different languages, each of which requires a custom stylesheet. Pygments is a well-maintained alternative. It is, by my count, the most popular syntax highlighting library around. It is BSD-licensed, actively maintained, and is widely used in PHP projects. To keep this easy to review, this change does not include update for l10n files, and it does not delete the geshi/ directory. I will do those in a separate patch. The chief change between this and the previous implementation is that errors result in the code block not being highlighted, as opposed to not being printed at all, having been replaced by an angry red error message. I think that is the right user experience. If you go to StackOverflow or GitHub and try to mark up your code block as being written in some language that their highlighter doesn't know about, you don't get an error message -- the code simply doesn't get highlighted. Because we don't recursively load dependencies for extensions, to test this, you will need to create a composer.local.json in $IP and add: { "extra": { "merge-plugin": { "include": [ "extensions/SyntaxHighlight_GeSHi/composer.json" ] } } } Then run `composer update`. Bug: T85794 Change-Id: I07446ec9893fae3d1e394f435d3d95cf8be6bc33
2015-06-16 03:52:58 +00:00
'ooc',
'opa',
'openbugs',
'openedge',
Update pygments bundle to 2.1 Changelog: https://bitbucket.org/birkenfeld/pygments-main/raw/7614bf7/CHANGES Lots of new lexers: Emacs Lisp, Arduino, Modula-2 with multi-dialect support, Fortran fixed format, Archetype Definition language, Terraform, Jcl, Easytrieve, ParaSail, Boogie, Turtle, Fish Shell, Roboconf, Test Anything Protocol, Shen, Component Pascal, SuperCollider, Shell consoles (Tcsh, PowerShell, MSDOS), Elm and J, Crmsh, Praat, CSound, Ezhil, Thrift, QVT Operational, Hexdump, and CAmkES Configuration. Bug: T125581 Change-Id: Ie881af3d1dff23f08ccc9cbcf5f94a084fa561e1
2016-02-02 21:37:11 +00:00
'pacmanconf',
Highlight using Pygments rather than Geshi GeSHi is unmaintained, lacks support for many popular modern languages, and suffers from deep architectural flaws, chief among them the inconsistent tokenization of different languages, each of which requires a custom stylesheet. Pygments is a well-maintained alternative. It is, by my count, the most popular syntax highlighting library around. It is BSD-licensed, actively maintained, and is widely used in PHP projects. To keep this easy to review, this change does not include update for l10n files, and it does not delete the geshi/ directory. I will do those in a separate patch. The chief change between this and the previous implementation is that errors result in the code block not being highlighted, as opposed to not being printed at all, having been replaced by an angry red error message. I think that is the right user experience. If you go to StackOverflow or GitHub and try to mark up your code block as being written in some language that their highlighter doesn't know about, you don't get an error message -- the code simply doesn't get highlighted. Because we don't recursively load dependencies for extensions, to test this, you will need to create a composer.local.json in $IP and add: { "extra": { "merge-plugin": { "include": [ "extensions/SyntaxHighlight_GeSHi/composer.json" ] } } } Then run `composer update`. Bug: T85794 Change-Id: I07446ec9893fae3d1e394f435d3d95cf8be6bc33
2015-06-16 03:52:58 +00:00
'pan',
Update pygments bundle to 2.1 Changelog: https://bitbucket.org/birkenfeld/pygments-main/raw/7614bf7/CHANGES Lots of new lexers: Emacs Lisp, Arduino, Modula-2 with multi-dialect support, Fortran fixed format, Archetype Definition language, Terraform, Jcl, Easytrieve, ParaSail, Boogie, Turtle, Fish Shell, Roboconf, Test Anything Protocol, Shen, Component Pascal, SuperCollider, Shell consoles (Tcsh, PowerShell, MSDOS), Elm and J, Crmsh, Praat, CSound, Ezhil, Thrift, QVT Operational, Hexdump, and CAmkES Configuration. Bug: T125581 Change-Id: Ie881af3d1dff23f08ccc9cbcf5f94a084fa561e1
2016-02-02 21:37:11 +00:00
'parasail',
Highlight using Pygments rather than Geshi GeSHi is unmaintained, lacks support for many popular modern languages, and suffers from deep architectural flaws, chief among them the inconsistent tokenization of different languages, each of which requires a custom stylesheet. Pygments is a well-maintained alternative. It is, by my count, the most popular syntax highlighting library around. It is BSD-licensed, actively maintained, and is widely used in PHP projects. To keep this easy to review, this change does not include update for l10n files, and it does not delete the geshi/ directory. I will do those in a separate patch. The chief change between this and the previous implementation is that errors result in the code block not being highlighted, as opposed to not being printed at all, having been replaced by an angry red error message. I think that is the right user experience. If you go to StackOverflow or GitHub and try to mark up your code block as being written in some language that their highlighter doesn't know about, you don't get an error message -- the code simply doesn't get highlighted. Because we don't recursively load dependencies for extensions, to test this, you will need to create a composer.local.json in $IP and add: { "extra": { "merge-plugin": { "include": [ "extensions/SyntaxHighlight_GeSHi/composer.json" ] } } } Then run `composer update`. Bug: T85794 Change-Id: I07446ec9893fae3d1e394f435d3d95cf8be6bc33
2015-06-16 03:52:58 +00:00
'pas',
'pascal',
'pawn',
Update pygments bundle to 2.1 Changelog: https://bitbucket.org/birkenfeld/pygments-main/raw/7614bf7/CHANGES Lots of new lexers: Emacs Lisp, Arduino, Modula-2 with multi-dialect support, Fortran fixed format, Archetype Definition language, Terraform, Jcl, Easytrieve, ParaSail, Boogie, Turtle, Fish Shell, Roboconf, Test Anything Protocol, Shen, Component Pascal, SuperCollider, Shell consoles (Tcsh, PowerShell, MSDOS), Elm and J, Crmsh, Praat, CSound, Ezhil, Thrift, QVT Operational, Hexdump, and CAmkES Configuration. Bug: T125581 Change-Id: Ie881af3d1dff23f08ccc9cbcf5f94a084fa561e1
2016-02-02 21:37:11 +00:00
'pcmk',
Highlight using Pygments rather than Geshi GeSHi is unmaintained, lacks support for many popular modern languages, and suffers from deep architectural flaws, chief among them the inconsistent tokenization of different languages, each of which requires a custom stylesheet. Pygments is a well-maintained alternative. It is, by my count, the most popular syntax highlighting library around. It is BSD-licensed, actively maintained, and is widely used in PHP projects. To keep this easy to review, this change does not include update for l10n files, and it does not delete the geshi/ directory. I will do those in a separate patch. The chief change between this and the previous implementation is that errors result in the code block not being highlighted, as opposed to not being printed at all, having been replaced by an angry red error message. I think that is the right user experience. If you go to StackOverflow or GitHub and try to mark up your code block as being written in some language that their highlighter doesn't know about, you don't get an error message -- the code simply doesn't get highlighted. Because we don't recursively load dependencies for extensions, to test this, you will need to create a composer.local.json in $IP and add: { "extra": { "merge-plugin": { "include": [ "extensions/SyntaxHighlight_GeSHi/composer.json" ] } } } Then run `composer update`. Bug: T85794 Change-Id: I07446ec9893fae3d1e394f435d3d95cf8be6bc33
2015-06-16 03:52:58 +00:00
'perl',
'perl6',
'php',
'php3',
'php4',
'php5',
'pig',
'pike',
Update pygments bundle to 2.1 Changelog: https://bitbucket.org/birkenfeld/pygments-main/raw/7614bf7/CHANGES Lots of new lexers: Emacs Lisp, Arduino, Modula-2 with multi-dialect support, Fortran fixed format, Archetype Definition language, Terraform, Jcl, Easytrieve, ParaSail, Boogie, Turtle, Fish Shell, Roboconf, Test Anything Protocol, Shen, Component Pascal, SuperCollider, Shell consoles (Tcsh, PowerShell, MSDOS), Elm and J, Crmsh, Praat, CSound, Ezhil, Thrift, QVT Operational, Hexdump, and CAmkES Configuration. Bug: T125581 Change-Id: Ie881af3d1dff23f08ccc9cbcf5f94a084fa561e1
2016-02-02 21:37:11 +00:00
'pkgconfig',
Highlight using Pygments rather than Geshi GeSHi is unmaintained, lacks support for many popular modern languages, and suffers from deep architectural flaws, chief among them the inconsistent tokenization of different languages, each of which requires a custom stylesheet. Pygments is a well-maintained alternative. It is, by my count, the most popular syntax highlighting library around. It is BSD-licensed, actively maintained, and is widely used in PHP projects. To keep this easy to review, this change does not include update for l10n files, and it does not delete the geshi/ directory. I will do those in a separate patch. The chief change between this and the previous implementation is that errors result in the code block not being highlighted, as opposed to not being printed at all, having been replaced by an angry red error message. I think that is the right user experience. If you go to StackOverflow or GitHub and try to mark up your code block as being written in some language that their highlighter doesn't know about, you don't get an error message -- the code simply doesn't get highlighted. Because we don't recursively load dependencies for extensions, to test this, you will need to create a composer.local.json in $IP and add: { "extra": { "merge-plugin": { "include": [ "extensions/SyntaxHighlight_GeSHi/composer.json" ] } } } Then run `composer update`. Bug: T85794 Change-Id: I07446ec9893fae3d1e394f435d3d95cf8be6bc33
2015-06-16 03:52:58 +00:00
'pl',
'pl6',
'plpgsql',
'po',
'posh',
'postgres',
'postgres-console',
'postgresql',
'postgresql-console',
'postscr',
'postscript',
'pot',
'pov',
'powershell',
Update pygments bundle to 2.1 Changelog: https://bitbucket.org/birkenfeld/pygments-main/raw/7614bf7/CHANGES Lots of new lexers: Emacs Lisp, Arduino, Modula-2 with multi-dialect support, Fortran fixed format, Archetype Definition language, Terraform, Jcl, Easytrieve, ParaSail, Boogie, Turtle, Fish Shell, Roboconf, Test Anything Protocol, Shen, Component Pascal, SuperCollider, Shell consoles (Tcsh, PowerShell, MSDOS), Elm and J, Crmsh, Praat, CSound, Ezhil, Thrift, QVT Operational, Hexdump, and CAmkES Configuration. Bug: T125581 Change-Id: Ie881af3d1dff23f08ccc9cbcf5f94a084fa561e1
2016-02-02 21:37:11 +00:00
'praat',
Highlight using Pygments rather than Geshi GeSHi is unmaintained, lacks support for many popular modern languages, and suffers from deep architectural flaws, chief among them the inconsistent tokenization of different languages, each of which requires a custom stylesheet. Pygments is a well-maintained alternative. It is, by my count, the most popular syntax highlighting library around. It is BSD-licensed, actively maintained, and is widely used in PHP projects. To keep this easy to review, this change does not include update for l10n files, and it does not delete the geshi/ directory. I will do those in a separate patch. The chief change between this and the previous implementation is that errors result in the code block not being highlighted, as opposed to not being printed at all, having been replaced by an angry red error message. I think that is the right user experience. If you go to StackOverflow or GitHub and try to mark up your code block as being written in some language that their highlighter doesn't know about, you don't get an error message -- the code simply doesn't get highlighted. Because we don't recursively load dependencies for extensions, to test this, you will need to create a composer.local.json in $IP and add: { "extra": { "merge-plugin": { "include": [ "extensions/SyntaxHighlight_GeSHi/composer.json" ] } } } Then run `composer update`. Bug: T85794 Change-Id: I07446ec9893fae3d1e394f435d3d95cf8be6bc33
2015-06-16 03:52:58 +00:00
'progress',
'prolog',
'properties',
'proto',
'protobuf',
'ps1',
Update pygments bundle to 2.1 Changelog: https://bitbucket.org/birkenfeld/pygments-main/raw/7614bf7/CHANGES Lots of new lexers: Emacs Lisp, Arduino, Modula-2 with multi-dialect support, Fortran fixed format, Archetype Definition language, Terraform, Jcl, Easytrieve, ParaSail, Boogie, Turtle, Fish Shell, Roboconf, Test Anything Protocol, Shen, Component Pascal, SuperCollider, Shell consoles (Tcsh, PowerShell, MSDOS), Elm and J, Crmsh, Praat, CSound, Ezhil, Thrift, QVT Operational, Hexdump, and CAmkES Configuration. Bug: T125581 Change-Id: Ie881af3d1dff23f08ccc9cbcf5f94a084fa561e1
2016-02-02 21:37:11 +00:00
'ps1con',
Highlight using Pygments rather than Geshi GeSHi is unmaintained, lacks support for many popular modern languages, and suffers from deep architectural flaws, chief among them the inconsistent tokenization of different languages, each of which requires a custom stylesheet. Pygments is a well-maintained alternative. It is, by my count, the most popular syntax highlighting library around. It is BSD-licensed, actively maintained, and is widely used in PHP projects. To keep this easy to review, this change does not include update for l10n files, and it does not delete the geshi/ directory. I will do those in a separate patch. The chief change between this and the previous implementation is that errors result in the code block not being highlighted, as opposed to not being printed at all, having been replaced by an angry red error message. I think that is the right user experience. If you go to StackOverflow or GitHub and try to mark up your code block as being written in some language that their highlighter doesn't know about, you don't get an error message -- the code simply doesn't get highlighted. Because we don't recursively load dependencies for extensions, to test this, you will need to create a composer.local.json in $IP and add: { "extra": { "merge-plugin": { "include": [ "extensions/SyntaxHighlight_GeSHi/composer.json" ] } } } Then run `composer update`. Bug: T85794 Change-Id: I07446ec9893fae3d1e394f435d3d95cf8be6bc33
2015-06-16 03:52:58 +00:00
'psm1',
'psql',
Update pygments to 2.2 Notable changes: * Added new token types and lexing for magic methods and variables in Python and PHP. * Added a new token type for heredoc (and similar) string delimiters and lexing for them in C++, Perl, PHP, Postgresql and Ruby lexers. * Improved the CSS lexer. * Added Varnish config lexer Full changelog is found at: <https://bitbucket.org/birkenfeld/pygments-main/src/bc45808f83d5338e3116be91890e6ad15220ee45/CHANGES> Bug: T156573 Change-Id: I4dc1782f19881ba1294308e1cdea1b2e063f438a
2017-01-29 09:35:35 +00:00
'pug',
Highlight using Pygments rather than Geshi GeSHi is unmaintained, lacks support for many popular modern languages, and suffers from deep architectural flaws, chief among them the inconsistent tokenization of different languages, each of which requires a custom stylesheet. Pygments is a well-maintained alternative. It is, by my count, the most popular syntax highlighting library around. It is BSD-licensed, actively maintained, and is widely used in PHP projects. To keep this easy to review, this change does not include update for l10n files, and it does not delete the geshi/ directory. I will do those in a separate patch. The chief change between this and the previous implementation is that errors result in the code block not being highlighted, as opposed to not being printed at all, having been replaced by an angry red error message. I think that is the right user experience. If you go to StackOverflow or GitHub and try to mark up your code block as being written in some language that their highlighter doesn't know about, you don't get an error message -- the code simply doesn't get highlighted. Because we don't recursively load dependencies for extensions, to test this, you will need to create a composer.local.json in $IP and add: { "extra": { "merge-plugin": { "include": [ "extensions/SyntaxHighlight_GeSHi/composer.json" ] } } } Then run `composer update`. Bug: T85794 Change-Id: I07446ec9893fae3d1e394f435d3d95cf8be6bc33
2015-06-16 03:52:58 +00:00
'puppet',
'py',
'py3',
'py3tb',
'pycon',
'pypy',
'pypylog',
'pyrex',
'pytb',
'python',
'python3',
'pyx',
'qbasic',
Update pygments bundle to 2.1 Changelog: https://bitbucket.org/birkenfeld/pygments-main/raw/7614bf7/CHANGES Lots of new lexers: Emacs Lisp, Arduino, Modula-2 with multi-dialect support, Fortran fixed format, Archetype Definition language, Terraform, Jcl, Easytrieve, ParaSail, Boogie, Turtle, Fish Shell, Roboconf, Test Anything Protocol, Shen, Component Pascal, SuperCollider, Shell consoles (Tcsh, PowerShell, MSDOS), Elm and J, Crmsh, Praat, CSound, Ezhil, Thrift, QVT Operational, Hexdump, and CAmkES Configuration. Bug: T125581 Change-Id: Ie881af3d1dff23f08ccc9cbcf5f94a084fa561e1
2016-02-02 21:37:11 +00:00
'qbs',
Highlight using Pygments rather than Geshi GeSHi is unmaintained, lacks support for many popular modern languages, and suffers from deep architectural flaws, chief among them the inconsistent tokenization of different languages, each of which requires a custom stylesheet. Pygments is a well-maintained alternative. It is, by my count, the most popular syntax highlighting library around. It is BSD-licensed, actively maintained, and is widely used in PHP projects. To keep this easy to review, this change does not include update for l10n files, and it does not delete the geshi/ directory. I will do those in a separate patch. The chief change between this and the previous implementation is that errors result in the code block not being highlighted, as opposed to not being printed at all, having been replaced by an angry red error message. I think that is the right user experience. If you go to StackOverflow or GitHub and try to mark up your code block as being written in some language that their highlighter doesn't know about, you don't get an error message -- the code simply doesn't get highlighted. Because we don't recursively load dependencies for extensions, to test this, you will need to create a composer.local.json in $IP and add: { "extra": { "merge-plugin": { "include": [ "extensions/SyntaxHighlight_GeSHi/composer.json" ] } } } Then run `composer update`. Bug: T85794 Change-Id: I07446ec9893fae3d1e394f435d3d95cf8be6bc33
2015-06-16 03:52:58 +00:00
'qml',
Update pygments bundle to 2.1 Changelog: https://bitbucket.org/birkenfeld/pygments-main/raw/7614bf7/CHANGES Lots of new lexers: Emacs Lisp, Arduino, Modula-2 with multi-dialect support, Fortran fixed format, Archetype Definition language, Terraform, Jcl, Easytrieve, ParaSail, Boogie, Turtle, Fish Shell, Roboconf, Test Anything Protocol, Shen, Component Pascal, SuperCollider, Shell consoles (Tcsh, PowerShell, MSDOS), Elm and J, Crmsh, Praat, CSound, Ezhil, Thrift, QVT Operational, Hexdump, and CAmkES Configuration. Bug: T125581 Change-Id: Ie881af3d1dff23f08ccc9cbcf5f94a084fa561e1
2016-02-02 21:37:11 +00:00
'qvt',
'qvto',
Highlight using Pygments rather than Geshi GeSHi is unmaintained, lacks support for many popular modern languages, and suffers from deep architectural flaws, chief among them the inconsistent tokenization of different languages, each of which requires a custom stylesheet. Pygments is a well-maintained alternative. It is, by my count, the most popular syntax highlighting library around. It is BSD-licensed, actively maintained, and is widely used in PHP projects. To keep this easy to review, this change does not include update for l10n files, and it does not delete the geshi/ directory. I will do those in a separate patch. The chief change between this and the previous implementation is that errors result in the code block not being highlighted, as opposed to not being printed at all, having been replaced by an angry red error message. I think that is the right user experience. If you go to StackOverflow or GitHub and try to mark up your code block as being written in some language that their highlighter doesn't know about, you don't get an error message -- the code simply doesn't get highlighted. Because we don't recursively load dependencies for extensions, to test this, you will need to create a composer.local.json in $IP and add: { "extra": { "merge-plugin": { "include": [ "extensions/SyntaxHighlight_GeSHi/composer.json" ] } } } Then run `composer update`. Bug: T85794 Change-Id: I07446ec9893fae3d1e394f435d3d95cf8be6bc33
2015-06-16 03:52:58 +00:00
'r',
'racket',
'ragel',
'ragel-c',
'ragel-cpp',
'ragel-d',
'ragel-em',
'ragel-java',
'ragel-objc',
'ragel-rb',
'ragel-ruby',
'raw',
'rb',
'rbcon',
'rconsole',
'rd',
'rebol',
'red',
'red/system',
'redcode',
'registry',
'resource',
'resourcebundle',
'rest',
'restructuredtext',
'rexx',
'rhtml',
'rkt',
Update pygments to 2.2 Notable changes: * Added new token types and lexing for magic methods and variables in Python and PHP. * Added a new token type for heredoc (and similar) string delimiters and lexing for them in C++, Perl, PHP, Postgresql and Ruby lexers. * Improved the CSS lexer. * Added Varnish config lexer Full changelog is found at: <https://bitbucket.org/birkenfeld/pygments-main/src/bc45808f83d5338e3116be91890e6ad15220ee45/CHANGES> Bug: T156573 Change-Id: I4dc1782f19881ba1294308e1cdea1b2e063f438a
2017-01-29 09:35:35 +00:00
'rnc',
'rng-compact',
Update pygments bundle to 2.1 Changelog: https://bitbucket.org/birkenfeld/pygments-main/raw/7614bf7/CHANGES Lots of new lexers: Emacs Lisp, Arduino, Modula-2 with multi-dialect support, Fortran fixed format, Archetype Definition language, Terraform, Jcl, Easytrieve, ParaSail, Boogie, Turtle, Fish Shell, Roboconf, Test Anything Protocol, Shen, Component Pascal, SuperCollider, Shell consoles (Tcsh, PowerShell, MSDOS), Elm and J, Crmsh, Praat, CSound, Ezhil, Thrift, QVT Operational, Hexdump, and CAmkES Configuration. Bug: T125581 Change-Id: Ie881af3d1dff23f08ccc9cbcf5f94a084fa561e1
2016-02-02 21:37:11 +00:00
'roboconf-graph',
'roboconf-instances',
Highlight using Pygments rather than Geshi GeSHi is unmaintained, lacks support for many popular modern languages, and suffers from deep architectural flaws, chief among them the inconsistent tokenization of different languages, each of which requires a custom stylesheet. Pygments is a well-maintained alternative. It is, by my count, the most popular syntax highlighting library around. It is BSD-licensed, actively maintained, and is widely used in PHP projects. To keep this easy to review, this change does not include update for l10n files, and it does not delete the geshi/ directory. I will do those in a separate patch. The chief change between this and the previous implementation is that errors result in the code block not being highlighted, as opposed to not being printed at all, having been replaced by an angry red error message. I think that is the right user experience. If you go to StackOverflow or GitHub and try to mark up your code block as being written in some language that their highlighter doesn't know about, you don't get an error message -- the code simply doesn't get highlighted. Because we don't recursively load dependencies for extensions, to test this, you will need to create a composer.local.json in $IP and add: { "extra": { "merge-plugin": { "include": [ "extensions/SyntaxHighlight_GeSHi/composer.json" ] } } } Then run `composer update`. Bug: T85794 Change-Id: I07446ec9893fae3d1e394f435d3d95cf8be6bc33
2015-06-16 03:52:58 +00:00
'robotframework',
'rout',
'rql',
'rsl',
'rst',
Update pygments bundle to 2.1 Changelog: https://bitbucket.org/birkenfeld/pygments-main/raw/7614bf7/CHANGES Lots of new lexers: Emacs Lisp, Arduino, Modula-2 with multi-dialect support, Fortran fixed format, Archetype Definition language, Terraform, Jcl, Easytrieve, ParaSail, Boogie, Turtle, Fish Shell, Roboconf, Test Anything Protocol, Shen, Component Pascal, SuperCollider, Shell consoles (Tcsh, PowerShell, MSDOS), Elm and J, Crmsh, Praat, CSound, Ezhil, Thrift, QVT Operational, Hexdump, and CAmkES Configuration. Bug: T125581 Change-Id: Ie881af3d1dff23f08ccc9cbcf5f94a084fa561e1
2016-02-02 21:37:11 +00:00
'rts',
Highlight using Pygments rather than Geshi GeSHi is unmaintained, lacks support for many popular modern languages, and suffers from deep architectural flaws, chief among them the inconsistent tokenization of different languages, each of which requires a custom stylesheet. Pygments is a well-maintained alternative. It is, by my count, the most popular syntax highlighting library around. It is BSD-licensed, actively maintained, and is widely used in PHP projects. To keep this easy to review, this change does not include update for l10n files, and it does not delete the geshi/ directory. I will do those in a separate patch. The chief change between this and the previous implementation is that errors result in the code block not being highlighted, as opposed to not being printed at all, having been replaced by an angry red error message. I think that is the right user experience. If you go to StackOverflow or GitHub and try to mark up your code block as being written in some language that their highlighter doesn't know about, you don't get an error message -- the code simply doesn't get highlighted. Because we don't recursively load dependencies for extensions, to test this, you will need to create a composer.local.json in $IP and add: { "extra": { "merge-plugin": { "include": [ "extensions/SyntaxHighlight_GeSHi/composer.json" ] } } } Then run `composer update`. Bug: T85794 Change-Id: I07446ec9893fae3d1e394f435d3d95cf8be6bc33
2015-06-16 03:52:58 +00:00
'ruby',
'rust',
's',
'sage',
'salt',
Update pygments to 2.2 Notable changes: * Added new token types and lexing for magic methods and variables in Python and PHP. * Added a new token type for heredoc (and similar) string delimiters and lexing for them in C++, Perl, PHP, Postgresql and Ruby lexers. * Improved the CSS lexer. * Added Varnish config lexer Full changelog is found at: <https://bitbucket.org/birkenfeld/pygments-main/src/bc45808f83d5338e3116be91890e6ad15220ee45/CHANGES> Bug: T156573 Change-Id: I4dc1782f19881ba1294308e1cdea1b2e063f438a
2017-01-29 09:35:35 +00:00
'sas',
Highlight using Pygments rather than Geshi GeSHi is unmaintained, lacks support for many popular modern languages, and suffers from deep architectural flaws, chief among them the inconsistent tokenization of different languages, each of which requires a custom stylesheet. Pygments is a well-maintained alternative. It is, by my count, the most popular syntax highlighting library around. It is BSD-licensed, actively maintained, and is widely used in PHP projects. To keep this easy to review, this change does not include update for l10n files, and it does not delete the geshi/ directory. I will do those in a separate patch. The chief change between this and the previous implementation is that errors result in the code block not being highlighted, as opposed to not being printed at all, having been replaced by an angry red error message. I think that is the right user experience. If you go to StackOverflow or GitHub and try to mark up your code block as being written in some language that their highlighter doesn't know about, you don't get an error message -- the code simply doesn't get highlighted. Because we don't recursively load dependencies for extensions, to test this, you will need to create a composer.local.json in $IP and add: { "extra": { "merge-plugin": { "include": [ "extensions/SyntaxHighlight_GeSHi/composer.json" ] } } } Then run `composer update`. Bug: T85794 Change-Id: I07446ec9893fae3d1e394f435d3d95cf8be6bc33
2015-06-16 03:52:58 +00:00
'sass',
Update pygments bundle to 2.1 Changelog: https://bitbucket.org/birkenfeld/pygments-main/raw/7614bf7/CHANGES Lots of new lexers: Emacs Lisp, Arduino, Modula-2 with multi-dialect support, Fortran fixed format, Archetype Definition language, Terraform, Jcl, Easytrieve, ParaSail, Boogie, Turtle, Fish Shell, Roboconf, Test Anything Protocol, Shen, Component Pascal, SuperCollider, Shell consoles (Tcsh, PowerShell, MSDOS), Elm and J, Crmsh, Praat, CSound, Ezhil, Thrift, QVT Operational, Hexdump, and CAmkES Configuration. Bug: T125581 Change-Id: Ie881af3d1dff23f08ccc9cbcf5f94a084fa561e1
2016-02-02 21:37:11 +00:00
'sc',
Highlight using Pygments rather than Geshi GeSHi is unmaintained, lacks support for many popular modern languages, and suffers from deep architectural flaws, chief among them the inconsistent tokenization of different languages, each of which requires a custom stylesheet. Pygments is a well-maintained alternative. It is, by my count, the most popular syntax highlighting library around. It is BSD-licensed, actively maintained, and is widely used in PHP projects. To keep this easy to review, this change does not include update for l10n files, and it does not delete the geshi/ directory. I will do those in a separate patch. The chief change between this and the previous implementation is that errors result in the code block not being highlighted, as opposed to not being printed at all, having been replaced by an angry red error message. I think that is the right user experience. If you go to StackOverflow or GitHub and try to mark up your code block as being written in some language that their highlighter doesn't know about, you don't get an error message -- the code simply doesn't get highlighted. Because we don't recursively load dependencies for extensions, to test this, you will need to create a composer.local.json in $IP and add: { "extra": { "merge-plugin": { "include": [ "extensions/SyntaxHighlight_GeSHi/composer.json" ] } } } Then run `composer update`. Bug: T85794 Change-Id: I07446ec9893fae3d1e394f435d3d95cf8be6bc33
2015-06-16 03:52:58 +00:00
'scala',
'scaml',
'scheme',
'scilab',
'scm',
'scss',
'sh',
'shell',
'shell-session',
Update pygments bundle to 2.1 Changelog: https://bitbucket.org/birkenfeld/pygments-main/raw/7614bf7/CHANGES Lots of new lexers: Emacs Lisp, Arduino, Modula-2 with multi-dialect support, Fortran fixed format, Archetype Definition language, Terraform, Jcl, Easytrieve, ParaSail, Boogie, Turtle, Fish Shell, Roboconf, Test Anything Protocol, Shen, Component Pascal, SuperCollider, Shell consoles (Tcsh, PowerShell, MSDOS), Elm and J, Crmsh, Praat, CSound, Ezhil, Thrift, QVT Operational, Hexdump, and CAmkES Configuration. Bug: T125581 Change-Id: Ie881af3d1dff23f08ccc9cbcf5f94a084fa561e1
2016-02-02 21:37:11 +00:00
'shen',
Update pygments to 2.2 Notable changes: * Added new token types and lexing for magic methods and variables in Python and PHP. * Added a new token type for heredoc (and similar) string delimiters and lexing for them in C++, Perl, PHP, Postgresql and Ruby lexers. * Improved the CSS lexer. * Added Varnish config lexer Full changelog is found at: <https://bitbucket.org/birkenfeld/pygments-main/src/bc45808f83d5338e3116be91890e6ad15220ee45/CHANGES> Bug: T156573 Change-Id: I4dc1782f19881ba1294308e1cdea1b2e063f438a
2017-01-29 09:35:35 +00:00
'silver',
Highlight using Pygments rather than Geshi GeSHi is unmaintained, lacks support for many popular modern languages, and suffers from deep architectural flaws, chief among them the inconsistent tokenization of different languages, each of which requires a custom stylesheet. Pygments is a well-maintained alternative. It is, by my count, the most popular syntax highlighting library around. It is BSD-licensed, actively maintained, and is widely used in PHP projects. To keep this easy to review, this change does not include update for l10n files, and it does not delete the geshi/ directory. I will do those in a separate patch. The chief change between this and the previous implementation is that errors result in the code block not being highlighted, as opposed to not being printed at all, having been replaced by an angry red error message. I think that is the right user experience. If you go to StackOverflow or GitHub and try to mark up your code block as being written in some language that their highlighter doesn't know about, you don't get an error message -- the code simply doesn't get highlighted. Because we don't recursively load dependencies for extensions, to test this, you will need to create a composer.local.json in $IP and add: { "extra": { "merge-plugin": { "include": [ "extensions/SyntaxHighlight_GeSHi/composer.json" ] } } } Then run `composer update`. Bug: T85794 Change-Id: I07446ec9893fae3d1e394f435d3d95cf8be6bc33
2015-06-16 03:52:58 +00:00
'slim',
'sls',
'smali',
'smalltalk',
'smarty',
'sml',
'snobol',
Update pygments to 2.2 Notable changes: * Added new token types and lexing for magic methods and variables in Python and PHP. * Added a new token type for heredoc (and similar) string delimiters and lexing for them in C++, Perl, PHP, Postgresql and Ruby lexers. * Improved the CSS lexer. * Added Varnish config lexer Full changelog is found at: <https://bitbucket.org/birkenfeld/pygments-main/src/bc45808f83d5338e3116be91890e6ad15220ee45/CHANGES> Bug: T156573 Change-Id: I4dc1782f19881ba1294308e1cdea1b2e063f438a
2017-01-29 09:35:35 +00:00
'snowball',
Highlight using Pygments rather than Geshi GeSHi is unmaintained, lacks support for many popular modern languages, and suffers from deep architectural flaws, chief among them the inconsistent tokenization of different languages, each of which requires a custom stylesheet. Pygments is a well-maintained alternative. It is, by my count, the most popular syntax highlighting library around. It is BSD-licensed, actively maintained, and is widely used in PHP projects. To keep this easy to review, this change does not include update for l10n files, and it does not delete the geshi/ directory. I will do those in a separate patch. The chief change between this and the previous implementation is that errors result in the code block not being highlighted, as opposed to not being printed at all, having been replaced by an angry red error message. I think that is the right user experience. If you go to StackOverflow or GitHub and try to mark up your code block as being written in some language that their highlighter doesn't know about, you don't get an error message -- the code simply doesn't get highlighted. Because we don't recursively load dependencies for extensions, to test this, you will need to create a composer.local.json in $IP and add: { "extra": { "merge-plugin": { "include": [ "extensions/SyntaxHighlight_GeSHi/composer.json" ] } } } Then run `composer update`. Bug: T85794 Change-Id: I07446ec9893fae3d1e394f435d3d95cf8be6bc33
2015-06-16 03:52:58 +00:00
'sources.list',
'sourceslist',
'sp',
'sparql',
'spec',
'spitfire',
'splus',
'sql',
'sqlite3',
'squeak',
'squid',
'squid.conf',
'squidconf',
'ssp',
'st',
'stan',
Update pygments to 2.2 Notable changes: * Added new token types and lexing for magic methods and variables in Python and PHP. * Added a new token type for heredoc (and similar) string delimiters and lexing for them in C++, Perl, PHP, Postgresql and Ruby lexers. * Improved the CSS lexer. * Added Varnish config lexer Full changelog is found at: <https://bitbucket.org/birkenfeld/pygments-main/src/bc45808f83d5338e3116be91890e6ad15220ee45/CHANGES> Bug: T156573 Change-Id: I4dc1782f19881ba1294308e1cdea1b2e063f438a
2017-01-29 09:35:35 +00:00
'stata',
Update pygments bundle to 2.1 Changelog: https://bitbucket.org/birkenfeld/pygments-main/raw/7614bf7/CHANGES Lots of new lexers: Emacs Lisp, Arduino, Modula-2 with multi-dialect support, Fortran fixed format, Archetype Definition language, Terraform, Jcl, Easytrieve, ParaSail, Boogie, Turtle, Fish Shell, Roboconf, Test Anything Protocol, Shen, Component Pascal, SuperCollider, Shell consoles (Tcsh, PowerShell, MSDOS), Elm and J, Crmsh, Praat, CSound, Ezhil, Thrift, QVT Operational, Hexdump, and CAmkES Configuration. Bug: T125581 Change-Id: Ie881af3d1dff23f08ccc9cbcf5f94a084fa561e1
2016-02-02 21:37:11 +00:00
'supercollider',
Highlight using Pygments rather than Geshi GeSHi is unmaintained, lacks support for many popular modern languages, and suffers from deep architectural flaws, chief among them the inconsistent tokenization of different languages, each of which requires a custom stylesheet. Pygments is a well-maintained alternative. It is, by my count, the most popular syntax highlighting library around. It is BSD-licensed, actively maintained, and is widely used in PHP projects. To keep this easy to review, this change does not include update for l10n files, and it does not delete the geshi/ directory. I will do those in a separate patch. The chief change between this and the previous implementation is that errors result in the code block not being highlighted, as opposed to not being printed at all, having been replaced by an angry red error message. I think that is the right user experience. If you go to StackOverflow or GitHub and try to mark up your code block as being written in some language that their highlighter doesn't know about, you don't get an error message -- the code simply doesn't get highlighted. Because we don't recursively load dependencies for extensions, to test this, you will need to create a composer.local.json in $IP and add: { "extra": { "merge-plugin": { "include": [ "extensions/SyntaxHighlight_GeSHi/composer.json" ] } } } Then run `composer update`. Bug: T85794 Change-Id: I07446ec9893fae3d1e394f435d3d95cf8be6bc33
2015-06-16 03:52:58 +00:00
'sv',
'swift',
'swig',
'systemverilog',
Update pygments to 2.2 Notable changes: * Added new token types and lexing for magic methods and variables in Python and PHP. * Added a new token type for heredoc (and similar) string delimiters and lexing for them in C++, Perl, PHP, Postgresql and Ruby lexers. * Improved the CSS lexer. * Added Varnish config lexer Full changelog is found at: <https://bitbucket.org/birkenfeld/pygments-main/src/bc45808f83d5338e3116be91890e6ad15220ee45/CHANGES> Bug: T156573 Change-Id: I4dc1782f19881ba1294308e1cdea1b2e063f438a
2017-01-29 09:35:35 +00:00
't-sql',
Highlight using Pygments rather than Geshi GeSHi is unmaintained, lacks support for many popular modern languages, and suffers from deep architectural flaws, chief among them the inconsistent tokenization of different languages, each of which requires a custom stylesheet. Pygments is a well-maintained alternative. It is, by my count, the most popular syntax highlighting library around. It is BSD-licensed, actively maintained, and is widely used in PHP projects. To keep this easy to review, this change does not include update for l10n files, and it does not delete the geshi/ directory. I will do those in a separate patch. The chief change between this and the previous implementation is that errors result in the code block not being highlighted, as opposed to not being printed at all, having been replaced by an angry red error message. I think that is the right user experience. If you go to StackOverflow or GitHub and try to mark up your code block as being written in some language that their highlighter doesn't know about, you don't get an error message -- the code simply doesn't get highlighted. Because we don't recursively load dependencies for extensions, to test this, you will need to create a composer.local.json in $IP and add: { "extra": { "merge-plugin": { "include": [ "extensions/SyntaxHighlight_GeSHi/composer.json" ] } } } Then run `composer update`. Bug: T85794 Change-Id: I07446ec9893fae3d1e394f435d3d95cf8be6bc33
2015-06-16 03:52:58 +00:00
'tads3',
Update pygments bundle to 2.1 Changelog: https://bitbucket.org/birkenfeld/pygments-main/raw/7614bf7/CHANGES Lots of new lexers: Emacs Lisp, Arduino, Modula-2 with multi-dialect support, Fortran fixed format, Archetype Definition language, Terraform, Jcl, Easytrieve, ParaSail, Boogie, Turtle, Fish Shell, Roboconf, Test Anything Protocol, Shen, Component Pascal, SuperCollider, Shell consoles (Tcsh, PowerShell, MSDOS), Elm and J, Crmsh, Praat, CSound, Ezhil, Thrift, QVT Operational, Hexdump, and CAmkES Configuration. Bug: T125581 Change-Id: Ie881af3d1dff23f08ccc9cbcf5f94a084fa561e1
2016-02-02 21:37:11 +00:00
'tap',
Update pygments to 2.2 Notable changes: * Added new token types and lexing for magic methods and variables in Python and PHP. * Added a new token type for heredoc (and similar) string delimiters and lexing for them in C++, Perl, PHP, Postgresql and Ruby lexers. * Improved the CSS lexer. * Added Varnish config lexer Full changelog is found at: <https://bitbucket.org/birkenfeld/pygments-main/src/bc45808f83d5338e3116be91890e6ad15220ee45/CHANGES> Bug: T156573 Change-Id: I4dc1782f19881ba1294308e1cdea1b2e063f438a
2017-01-29 09:35:35 +00:00
'tasm',
Highlight using Pygments rather than Geshi GeSHi is unmaintained, lacks support for many popular modern languages, and suffers from deep architectural flaws, chief among them the inconsistent tokenization of different languages, each of which requires a custom stylesheet. Pygments is a well-maintained alternative. It is, by my count, the most popular syntax highlighting library around. It is BSD-licensed, actively maintained, and is widely used in PHP projects. To keep this easy to review, this change does not include update for l10n files, and it does not delete the geshi/ directory. I will do those in a separate patch. The chief change between this and the previous implementation is that errors result in the code block not being highlighted, as opposed to not being printed at all, having been replaced by an angry red error message. I think that is the right user experience. If you go to StackOverflow or GitHub and try to mark up your code block as being written in some language that their highlighter doesn't know about, you don't get an error message -- the code simply doesn't get highlighted. Because we don't recursively load dependencies for extensions, to test this, you will need to create a composer.local.json in $IP and add: { "extra": { "merge-plugin": { "include": [ "extensions/SyntaxHighlight_GeSHi/composer.json" ] } } } Then run `composer update`. Bug: T85794 Change-Id: I07446ec9893fae3d1e394f435d3d95cf8be6bc33
2015-06-16 03:52:58 +00:00
'tcl',
'tcsh',
Update pygments bundle to 2.1 Changelog: https://bitbucket.org/birkenfeld/pygments-main/raw/7614bf7/CHANGES Lots of new lexers: Emacs Lisp, Arduino, Modula-2 with multi-dialect support, Fortran fixed format, Archetype Definition language, Terraform, Jcl, Easytrieve, ParaSail, Boogie, Turtle, Fish Shell, Roboconf, Test Anything Protocol, Shen, Component Pascal, SuperCollider, Shell consoles (Tcsh, PowerShell, MSDOS), Elm and J, Crmsh, Praat, CSound, Ezhil, Thrift, QVT Operational, Hexdump, and CAmkES Configuration. Bug: T125581 Change-Id: Ie881af3d1dff23f08ccc9cbcf5f94a084fa561e1
2016-02-02 21:37:11 +00:00
'tcshcon',
Highlight using Pygments rather than Geshi GeSHi is unmaintained, lacks support for many popular modern languages, and suffers from deep architectural flaws, chief among them the inconsistent tokenization of different languages, each of which requires a custom stylesheet. Pygments is a well-maintained alternative. It is, by my count, the most popular syntax highlighting library around. It is BSD-licensed, actively maintained, and is widely used in PHP projects. To keep this easy to review, this change does not include update for l10n files, and it does not delete the geshi/ directory. I will do those in a separate patch. The chief change between this and the previous implementation is that errors result in the code block not being highlighted, as opposed to not being printed at all, having been replaced by an angry red error message. I think that is the right user experience. If you go to StackOverflow or GitHub and try to mark up your code block as being written in some language that their highlighter doesn't know about, you don't get an error message -- the code simply doesn't get highlighted. Because we don't recursively load dependencies for extensions, to test this, you will need to create a composer.local.json in $IP and add: { "extra": { "merge-plugin": { "include": [ "extensions/SyntaxHighlight_GeSHi/composer.json" ] } } } Then run `composer update`. Bug: T85794 Change-Id: I07446ec9893fae3d1e394f435d3d95cf8be6bc33
2015-06-16 03:52:58 +00:00
'tea',
Update pygments bundle to 2.1 Changelog: https://bitbucket.org/birkenfeld/pygments-main/raw/7614bf7/CHANGES Lots of new lexers: Emacs Lisp, Arduino, Modula-2 with multi-dialect support, Fortran fixed format, Archetype Definition language, Terraform, Jcl, Easytrieve, ParaSail, Boogie, Turtle, Fish Shell, Roboconf, Test Anything Protocol, Shen, Component Pascal, SuperCollider, Shell consoles (Tcsh, PowerShell, MSDOS), Elm and J, Crmsh, Praat, CSound, Ezhil, Thrift, QVT Operational, Hexdump, and CAmkES Configuration. Bug: T125581 Change-Id: Ie881af3d1dff23f08ccc9cbcf5f94a084fa561e1
2016-02-02 21:37:11 +00:00
'termcap',
'terminfo',
'terraform',
Highlight using Pygments rather than Geshi GeSHi is unmaintained, lacks support for many popular modern languages, and suffers from deep architectural flaws, chief among them the inconsistent tokenization of different languages, each of which requires a custom stylesheet. Pygments is a well-maintained alternative. It is, by my count, the most popular syntax highlighting library around. It is BSD-licensed, actively maintained, and is widely used in PHP projects. To keep this easy to review, this change does not include update for l10n files, and it does not delete the geshi/ directory. I will do those in a separate patch. The chief change between this and the previous implementation is that errors result in the code block not being highlighted, as opposed to not being printed at all, having been replaced by an angry red error message. I think that is the right user experience. If you go to StackOverflow or GitHub and try to mark up your code block as being written in some language that their highlighter doesn't know about, you don't get an error message -- the code simply doesn't get highlighted. Because we don't recursively load dependencies for extensions, to test this, you will need to create a composer.local.json in $IP and add: { "extra": { "merge-plugin": { "include": [ "extensions/SyntaxHighlight_GeSHi/composer.json" ] } } } Then run `composer update`. Bug: T85794 Change-Id: I07446ec9893fae3d1e394f435d3d95cf8be6bc33
2015-06-16 03:52:58 +00:00
'tex',
'text',
Update pygments bundle to 2.1 Changelog: https://bitbucket.org/birkenfeld/pygments-main/raw/7614bf7/CHANGES Lots of new lexers: Emacs Lisp, Arduino, Modula-2 with multi-dialect support, Fortran fixed format, Archetype Definition language, Terraform, Jcl, Easytrieve, ParaSail, Boogie, Turtle, Fish Shell, Roboconf, Test Anything Protocol, Shen, Component Pascal, SuperCollider, Shell consoles (Tcsh, PowerShell, MSDOS), Elm and J, Crmsh, Praat, CSound, Ezhil, Thrift, QVT Operational, Hexdump, and CAmkES Configuration. Bug: T125581 Change-Id: Ie881af3d1dff23f08ccc9cbcf5f94a084fa561e1
2016-02-02 21:37:11 +00:00
'tf',
'thrift',
Highlight using Pygments rather than Geshi GeSHi is unmaintained, lacks support for many popular modern languages, and suffers from deep architectural flaws, chief among them the inconsistent tokenization of different languages, each of which requires a custom stylesheet. Pygments is a well-maintained alternative. It is, by my count, the most popular syntax highlighting library around. It is BSD-licensed, actively maintained, and is widely used in PHP projects. To keep this easy to review, this change does not include update for l10n files, and it does not delete the geshi/ directory. I will do those in a separate patch. The chief change between this and the previous implementation is that errors result in the code block not being highlighted, as opposed to not being printed at all, having been replaced by an angry red error message. I think that is the right user experience. If you go to StackOverflow or GitHub and try to mark up your code block as being written in some language that their highlighter doesn't know about, you don't get an error message -- the code simply doesn't get highlighted. Because we don't recursively load dependencies for extensions, to test this, you will need to create a composer.local.json in $IP and add: { "extra": { "merge-plugin": { "include": [ "extensions/SyntaxHighlight_GeSHi/composer.json" ] } } } Then run `composer update`. Bug: T85794 Change-Id: I07446ec9893fae3d1e394f435d3d95cf8be6bc33
2015-06-16 03:52:58 +00:00
'todotxt',
'trac-wiki',
Update pygments bundle to 2.1 Changelog: https://bitbucket.org/birkenfeld/pygments-main/raw/7614bf7/CHANGES Lots of new lexers: Emacs Lisp, Arduino, Modula-2 with multi-dialect support, Fortran fixed format, Archetype Definition language, Terraform, Jcl, Easytrieve, ParaSail, Boogie, Turtle, Fish Shell, Roboconf, Test Anything Protocol, Shen, Component Pascal, SuperCollider, Shell consoles (Tcsh, PowerShell, MSDOS), Elm and J, Crmsh, Praat, CSound, Ezhil, Thrift, QVT Operational, Hexdump, and CAmkES Configuration. Bug: T125581 Change-Id: Ie881af3d1dff23f08ccc9cbcf5f94a084fa561e1
2016-02-02 21:37:11 +00:00
'trafficscript',
Highlight using Pygments rather than Geshi GeSHi is unmaintained, lacks support for many popular modern languages, and suffers from deep architectural flaws, chief among them the inconsistent tokenization of different languages, each of which requires a custom stylesheet. Pygments is a well-maintained alternative. It is, by my count, the most popular syntax highlighting library around. It is BSD-licensed, actively maintained, and is widely used in PHP projects. To keep this easy to review, this change does not include update for l10n files, and it does not delete the geshi/ directory. I will do those in a separate patch. The chief change between this and the previous implementation is that errors result in the code block not being highlighted, as opposed to not being printed at all, having been replaced by an angry red error message. I think that is the right user experience. If you go to StackOverflow or GitHub and try to mark up your code block as being written in some language that their highlighter doesn't know about, you don't get an error message -- the code simply doesn't get highlighted. Because we don't recursively load dependencies for extensions, to test this, you will need to create a composer.local.json in $IP and add: { "extra": { "merge-plugin": { "include": [ "extensions/SyntaxHighlight_GeSHi/composer.json" ] } } } Then run `composer update`. Bug: T85794 Change-Id: I07446ec9893fae3d1e394f435d3d95cf8be6bc33
2015-06-16 03:52:58 +00:00
'treetop',
'ts',
Update pygments to 2.2 Notable changes: * Added new token types and lexing for magic methods and variables in Python and PHP. * Added a new token type for heredoc (and similar) string delimiters and lexing for them in C++, Perl, PHP, Postgresql and Ruby lexers. * Improved the CSS lexer. * Added Varnish config lexer Full changelog is found at: <https://bitbucket.org/birkenfeld/pygments-main/src/bc45808f83d5338e3116be91890e6ad15220ee45/CHANGES> Bug: T156573 Change-Id: I4dc1782f19881ba1294308e1cdea1b2e063f438a
2017-01-29 09:35:35 +00:00
'tsql',
Update pygments bundle to 2.1 Changelog: https://bitbucket.org/birkenfeld/pygments-main/raw/7614bf7/CHANGES Lots of new lexers: Emacs Lisp, Arduino, Modula-2 with multi-dialect support, Fortran fixed format, Archetype Definition language, Terraform, Jcl, Easytrieve, ParaSail, Boogie, Turtle, Fish Shell, Roboconf, Test Anything Protocol, Shen, Component Pascal, SuperCollider, Shell consoles (Tcsh, PowerShell, MSDOS), Elm and J, Crmsh, Praat, CSound, Ezhil, Thrift, QVT Operational, Hexdump, and CAmkES Configuration. Bug: T125581 Change-Id: Ie881af3d1dff23f08ccc9cbcf5f94a084fa561e1
2016-02-02 21:37:11 +00:00
'turtle',
Highlight using Pygments rather than Geshi GeSHi is unmaintained, lacks support for many popular modern languages, and suffers from deep architectural flaws, chief among them the inconsistent tokenization of different languages, each of which requires a custom stylesheet. Pygments is a well-maintained alternative. It is, by my count, the most popular syntax highlighting library around. It is BSD-licensed, actively maintained, and is widely used in PHP projects. To keep this easy to review, this change does not include update for l10n files, and it does not delete the geshi/ directory. I will do those in a separate patch. The chief change between this and the previous implementation is that errors result in the code block not being highlighted, as opposed to not being printed at all, having been replaced by an angry red error message. I think that is the right user experience. If you go to StackOverflow or GitHub and try to mark up your code block as being written in some language that their highlighter doesn't know about, you don't get an error message -- the code simply doesn't get highlighted. Because we don't recursively load dependencies for extensions, to test this, you will need to create a composer.local.json in $IP and add: { "extra": { "merge-plugin": { "include": [ "extensions/SyntaxHighlight_GeSHi/composer.json" ] } } } Then run `composer update`. Bug: T85794 Change-Id: I07446ec9893fae3d1e394f435d3d95cf8be6bc33
2015-06-16 03:52:58 +00:00
'twig',
Update pygments bundle to 2.1 Changelog: https://bitbucket.org/birkenfeld/pygments-main/raw/7614bf7/CHANGES Lots of new lexers: Emacs Lisp, Arduino, Modula-2 with multi-dialect support, Fortran fixed format, Archetype Definition language, Terraform, Jcl, Easytrieve, ParaSail, Boogie, Turtle, Fish Shell, Roboconf, Test Anything Protocol, Shen, Component Pascal, SuperCollider, Shell consoles (Tcsh, PowerShell, MSDOS), Elm and J, Crmsh, Praat, CSound, Ezhil, Thrift, QVT Operational, Hexdump, and CAmkES Configuration. Bug: T125581 Change-Id: Ie881af3d1dff23f08ccc9cbcf5f94a084fa561e1
2016-02-02 21:37:11 +00:00
'typescript',
Update pygments to 2.2 Notable changes: * Added new token types and lexing for magic methods and variables in Python and PHP. * Added a new token type for heredoc (and similar) string delimiters and lexing for them in C++, Perl, PHP, Postgresql and Ruby lexers. * Improved the CSS lexer. * Added Varnish config lexer Full changelog is found at: <https://bitbucket.org/birkenfeld/pygments-main/src/bc45808f83d5338e3116be91890e6ad15220ee45/CHANGES> Bug: T156573 Change-Id: I4dc1782f19881ba1294308e1cdea1b2e063f438a
2017-01-29 09:35:35 +00:00
'typoscript',
'typoscriptcssdata',
'typoscripthtmldata',
Highlight using Pygments rather than Geshi GeSHi is unmaintained, lacks support for many popular modern languages, and suffers from deep architectural flaws, chief among them the inconsistent tokenization of different languages, each of which requires a custom stylesheet. Pygments is a well-maintained alternative. It is, by my count, the most popular syntax highlighting library around. It is BSD-licensed, actively maintained, and is widely used in PHP projects. To keep this easy to review, this change does not include update for l10n files, and it does not delete the geshi/ directory. I will do those in a separate patch. The chief change between this and the previous implementation is that errors result in the code block not being highlighted, as opposed to not being printed at all, having been replaced by an angry red error message. I think that is the right user experience. If you go to StackOverflow or GitHub and try to mark up your code block as being written in some language that their highlighter doesn't know about, you don't get an error message -- the code simply doesn't get highlighted. Because we don't recursively load dependencies for extensions, to test this, you will need to create a composer.local.json in $IP and add: { "extra": { "merge-plugin": { "include": [ "extensions/SyntaxHighlight_GeSHi/composer.json" ] } } } Then run `composer update`. Bug: T85794 Change-Id: I07446ec9893fae3d1e394f435d3d95cf8be6bc33
2015-06-16 03:52:58 +00:00
'udiff',
'urbiscript',
'v',
'vala',
'vapi',
'vb.net',
'vbnet',
Update pygments to 2.2 Notable changes: * Added new token types and lexing for magic methods and variables in Python and PHP. * Added a new token type for heredoc (and similar) string delimiters and lexing for them in C++, Perl, PHP, Postgresql and Ruby lexers. * Improved the CSS lexer. * Added Varnish config lexer Full changelog is found at: <https://bitbucket.org/birkenfeld/pygments-main/src/bc45808f83d5338e3116be91890e6ad15220ee45/CHANGES> Bug: T156573 Change-Id: I4dc1782f19881ba1294308e1cdea1b2e063f438a
2017-01-29 09:35:35 +00:00
'vcl',
'vclsnippet',
'vclsnippets',
Highlight using Pygments rather than Geshi GeSHi is unmaintained, lacks support for many popular modern languages, and suffers from deep architectural flaws, chief among them the inconsistent tokenization of different languages, each of which requires a custom stylesheet. Pygments is a well-maintained alternative. It is, by my count, the most popular syntax highlighting library around. It is BSD-licensed, actively maintained, and is widely used in PHP projects. To keep this easy to review, this change does not include update for l10n files, and it does not delete the geshi/ directory. I will do those in a separate patch. The chief change between this and the previous implementation is that errors result in the code block not being highlighted, as opposed to not being printed at all, having been replaced by an angry red error message. I think that is the right user experience. If you go to StackOverflow or GitHub and try to mark up your code block as being written in some language that their highlighter doesn't know about, you don't get an error message -- the code simply doesn't get highlighted. Because we don't recursively load dependencies for extensions, to test this, you will need to create a composer.local.json in $IP and add: { "extra": { "merge-plugin": { "include": [ "extensions/SyntaxHighlight_GeSHi/composer.json" ] } } } Then run `composer update`. Bug: T85794 Change-Id: I07446ec9893fae3d1e394f435d3d95cf8be6bc33
2015-06-16 03:52:58 +00:00
'vctreestatus',
'velocity',
'verilog',
'vfp',
'vgl',
'vhdl',
'vim',
Update pygments to 2.2 Notable changes: * Added new token types and lexing for magic methods and variables in Python and PHP. * Added a new token type for heredoc (and similar) string delimiters and lexing for them in C++, Perl, PHP, Postgresql and Ruby lexers. * Improved the CSS lexer. * Added Varnish config lexer Full changelog is found at: <https://bitbucket.org/birkenfeld/pygments-main/src/bc45808f83d5338e3116be91890e6ad15220ee45/CHANGES> Bug: T156573 Change-Id: I4dc1782f19881ba1294308e1cdea1b2e063f438a
2017-01-29 09:35:35 +00:00
'wdiff',
'whiley',
Highlight using Pygments rather than Geshi GeSHi is unmaintained, lacks support for many popular modern languages, and suffers from deep architectural flaws, chief among them the inconsistent tokenization of different languages, each of which requires a custom stylesheet. Pygments is a well-maintained alternative. It is, by my count, the most popular syntax highlighting library around. It is BSD-licensed, actively maintained, and is widely used in PHP projects. To keep this easy to review, this change does not include update for l10n files, and it does not delete the geshi/ directory. I will do those in a separate patch. The chief change between this and the previous implementation is that errors result in the code block not being highlighted, as opposed to not being printed at all, having been replaced by an angry red error message. I think that is the right user experience. If you go to StackOverflow or GitHub and try to mark up your code block as being written in some language that their highlighter doesn't know about, you don't get an error message -- the code simply doesn't get highlighted. Because we don't recursively load dependencies for extensions, to test this, you will need to create a composer.local.json in $IP and add: { "extra": { "merge-plugin": { "include": [ "extensions/SyntaxHighlight_GeSHi/composer.json" ] } } } Then run `composer update`. Bug: T85794 Change-Id: I07446ec9893fae3d1e394f435d3d95cf8be6bc33
2015-06-16 03:52:58 +00:00
'winbatch',
'winbugs',
Update pygments bundle to 2.1 Changelog: https://bitbucket.org/birkenfeld/pygments-main/raw/7614bf7/CHANGES Lots of new lexers: Emacs Lisp, Arduino, Modula-2 with multi-dialect support, Fortran fixed format, Archetype Definition language, Terraform, Jcl, Easytrieve, ParaSail, Boogie, Turtle, Fish Shell, Roboconf, Test Anything Protocol, Shen, Component Pascal, SuperCollider, Shell consoles (Tcsh, PowerShell, MSDOS), Elm and J, Crmsh, Praat, CSound, Ezhil, Thrift, QVT Operational, Hexdump, and CAmkES Configuration. Bug: T125581 Change-Id: Ie881af3d1dff23f08ccc9cbcf5f94a084fa561e1
2016-02-02 21:37:11 +00:00
'x10',
Highlight using Pygments rather than Geshi GeSHi is unmaintained, lacks support for many popular modern languages, and suffers from deep architectural flaws, chief among them the inconsistent tokenization of different languages, each of which requires a custom stylesheet. Pygments is a well-maintained alternative. It is, by my count, the most popular syntax highlighting library around. It is BSD-licensed, actively maintained, and is widely used in PHP projects. To keep this easy to review, this change does not include update for l10n files, and it does not delete the geshi/ directory. I will do those in a separate patch. The chief change between this and the previous implementation is that errors result in the code block not being highlighted, as opposed to not being printed at all, having been replaced by an angry red error message. I think that is the right user experience. If you go to StackOverflow or GitHub and try to mark up your code block as being written in some language that their highlighter doesn't know about, you don't get an error message -- the code simply doesn't get highlighted. Because we don't recursively load dependencies for extensions, to test this, you will need to create a composer.local.json in $IP and add: { "extra": { "merge-plugin": { "include": [ "extensions/SyntaxHighlight_GeSHi/composer.json" ] } } } Then run `composer update`. Bug: T85794 Change-Id: I07446ec9893fae3d1e394f435d3d95cf8be6bc33
2015-06-16 03:52:58 +00:00
'xbase',
'xml',
'xml+cheetah',
'xml+django',
'xml+erb',
'xml+evoque',
'xml+genshi',
'xml+jinja',
'xml+kid',
'xml+lasso',
'xml+mako',
'xml+myghty',
'xml+php',
'xml+ruby',
'xml+smarty',
'xml+spitfire',
'xml+velocity',
'xq',
'xql',
'xqm',
'xquery',
'xqy',
'xslt',
Update pygments bundle to 2.1 Changelog: https://bitbucket.org/birkenfeld/pygments-main/raw/7614bf7/CHANGES Lots of new lexers: Emacs Lisp, Arduino, Modula-2 with multi-dialect support, Fortran fixed format, Archetype Definition language, Terraform, Jcl, Easytrieve, ParaSail, Boogie, Turtle, Fish Shell, Roboconf, Test Anything Protocol, Shen, Component Pascal, SuperCollider, Shell consoles (Tcsh, PowerShell, MSDOS), Elm and J, Crmsh, Praat, CSound, Ezhil, Thrift, QVT Operational, Hexdump, and CAmkES Configuration. Bug: T125581 Change-Id: Ie881af3d1dff23f08ccc9cbcf5f94a084fa561e1
2016-02-02 21:37:11 +00:00
'xten',
Highlight using Pygments rather than Geshi GeSHi is unmaintained, lacks support for many popular modern languages, and suffers from deep architectural flaws, chief among them the inconsistent tokenization of different languages, each of which requires a custom stylesheet. Pygments is a well-maintained alternative. It is, by my count, the most popular syntax highlighting library around. It is BSD-licensed, actively maintained, and is widely used in PHP projects. To keep this easy to review, this change does not include update for l10n files, and it does not delete the geshi/ directory. I will do those in a separate patch. The chief change between this and the previous implementation is that errors result in the code block not being highlighted, as opposed to not being printed at all, having been replaced by an angry red error message. I think that is the right user experience. If you go to StackOverflow or GitHub and try to mark up your code block as being written in some language that their highlighter doesn't know about, you don't get an error message -- the code simply doesn't get highlighted. Because we don't recursively load dependencies for extensions, to test this, you will need to create a composer.local.json in $IP and add: { "extra": { "merge-plugin": { "include": [ "extensions/SyntaxHighlight_GeSHi/composer.json" ] } } } Then run `composer update`. Bug: T85794 Change-Id: I07446ec9893fae3d1e394f435d3d95cf8be6bc33
2015-06-16 03:52:58 +00:00
'xtend',
'xul+mozpreproc',
'yaml',
'yaml+jinja',
'zephir',
Update pygments to 2.2 Notable changes: * Added new token types and lexing for magic methods and variables in Python and PHP. * Added a new token type for heredoc (and similar) string delimiters and lexing for them in C++, Perl, PHP, Postgresql and Ruby lexers. * Improved the CSS lexer. * Added Varnish config lexer Full changelog is found at: <https://bitbucket.org/birkenfeld/pygments-main/src/bc45808f83d5338e3116be91890e6ad15220ee45/CHANGES> Bug: T156573 Change-Id: I4dc1782f19881ba1294308e1cdea1b2e063f438a
2017-01-29 09:35:35 +00:00
'zsh',
Use short array syntax Done by phpcbf over composer fix Change-Id: I043252a1cce9e51f158e0e27983ed4ae18fcfb42
2017-06-15 16:16:11 +00:00
];
Reference in a new issue Copy permalink