* Support text with angle brackets in diff text

This fixes issue with highlighting content with angle bracket (<, >) in
a diff. For example, `<span>` is no longer picked up as deleted, even
when it is at the start of string.

* Support diff text without leading space

* Add more supported examples for diff lexer

* Add override and define directives in make

This commit adds supports for `override` and `make` directives in GNU
Makefile.

* Add more keywords for GNU Makefile

* Fix highlight of functions outside of block

This fixes highlghting issues with functions such as `foreach` and
`eval`.

* Support secondary expansion and fix punctuation

This commit adds support for secondary expansion `$$` and corrects
tokens used for punctuation symbols such as `[{()}]`.

* Support unexport directive in make lexer

* First commit, add lexer, config and example files

* Removed comments from lexer file

* Fixed mismatched indentations warning in lexer file

* Fixed BOOLEAN highlight

* Update rml.rb

Add dataExp_with state, fixed rule for '>' symbol

* Fixed one state and indentation in lexer code

Fixed dataExp_with state and indentation warnings from rake tests

* Fixed indentation, variables and comments

Fixed code indentation, renamed variables names to snake-case, removed superfluous and closing comments. Added language entry in Languages.md file

Co-authored-by: Pietro Cattaneo <pietrocattaneo@MacBook-Pro-di-Pietro.local>

Signed-off-by: syuparn <s.hello.spagetti@gmail.com>

* Define missing namespace state for haxe lexer

This commit fixes an exception where namespace state is not defined.

- Standardise import, using and package statement
- Support import with alias
- Distinguish Keyword::Namespace token

* Support as keyword in import alias in Haxe

* Fix array being parsed as table header in TOML

This ensures table is pushed up to the root stack and not picked up
as value in the basic mix-in.

* Support spaces in table header in TOML

The existing HTTP lexer parses HTTP/2 requests, but not responses marked with HTTP/2. (However, it would accept HTTP/2.0.)

There is no specification for the textual representation of HTTP/2 traffic (as far as I can tell), but some tools generate response headers with only HTTP/2, which fail to be processed correctly by Rouge without this change.

With Ruby 2.6 being EOL, we should drop support for old versions to
reduce Rouge gem maintenance effort.