-
Notifications
You must be signed in to change notification settings - Fork 743
Comparing changes
Open a pull request
base repository: rouge-ruby/rouge
base: v3.18.0
head repository: rouge-ruby/rouge
compare: v3.19.0
- 12 commits
- 58 files changed
- 4 contributors
Commits on Apr 17, 2020
-
Add generic parameter keywords to Kotlin lexer (#1504)
Kotlin allows three keywords to be used inside a list of generic parameters: `in`, `out` and `reified`. In addition, it supports the use of `:`. This commit adds support for these elements to the Kotlin lexer.
Configuration menu - View commit details
-
Copy full SHA for 2b704db - Browse repository at this point
Copy the full SHA 2b704dbView commit details
Commits on Apr 20, 2020
-
Add Rake task to generate keywords for LLVM lexer (#1505)
The list of keywords that is recognised in the current LLVM lexer is not as complete as in some other syntax highlighting libraries (such as Pygments). This commit adds a Rake task that checks a source file in the public LLVM repo and generates a keyword file that is loaded on request when the LLVM lexer is used.
Configuration menu - View commit details
-
Copy full SHA for 42637b4 - Browse repository at this point
Copy the full SHA 42637b4View commit details -
Use qualified method name for calls to Kernel#load (#1503)
Rouge currently loads various components of the library using `Kernel#load`. In certain conditions, this can cause issues where `load` is redefined at the global level. To ensure maximum compatibility with other libraries, this commit replaces all calls to `load` with qualified calls to `Kernel::load`. It also updates one call to `Object.send` with a call to `Object::send` for consistency.
Configuration menu - View commit details
-
Copy full SHA for 2e9c3cd - Browse repository at this point
Copy the full SHA 2e9c3cdView commit details
Commits on May 12, 2020
-
Fix escape sequences in Python's strings (#1508)
Version 3.18.0 of Rouge included a new mechanism for handling strings in the Python lexer. One of the consequences of that change was that raw strings would break if they included 'invalid' escape sequences. This is a mistake as raw strings do not have 'invalid' escape sequences. This commit fixes this error by changing the approach that the Python lexer takes to escape sequences more generally. Rather than dividing recognised and unrecognised escape sequences into 'valid' and 'invalid', it simply treats unrecognised escape sequences as ordinary strings. The result of this is that all escape sequences in raw strings produce `Str` tokens. In other types of strings, recognised escape sequences produce `Str::Escape` tokens and unrecognised escape sequences produce `Str` tokens.
Configuration menu - View commit details
-
Copy full SHA for ead03fa - Browse repository at this point
Copy the full SHA ead03faView commit details -
Add CommonJS file glob to JavaScript lexer (#1511)
This commit adds the `*.cljs` fille glob to the JavaScript lexer. Node.js treats files ending in the `.cjs` extension as CommonJS modules. Co-authored-by: Michael Camilleri <mike@inqk.net>
Configuration menu - View commit details
-
Copy full SHA for 8e26a63 - Browse repository at this point
Copy the full SHA 8e26a63View commit details -
Allow Unicode in Python identifiers (#1510)
Python supports the use of Unicode in identifiers. This commit uses POSIX bracket expressions that match against Unicode characters rather than the more common character classes that only match ASCII characters. Co-authored-by: Michael Camilleri <mike@inqk.net>
Configuration menu - View commit details
-
Copy full SHA for 9f1f582 - Browse repository at this point
Copy the full SHA 9f1f582View commit details -
Fix RuboCop grouped expression warning in Python lexer (#1513)
The use of a ternary in code added to the Python lexer as part of the #1508 pull request results in a RuboCop warning concerning parentheses and grouped expressions. This commit fixes that warning.
Configuration menu - View commit details
-
Copy full SHA for 1e32f3c - Browse repository at this point
Copy the full SHA 1e32f3cView commit details -
Improve handling of numbers in Kotlin lexer (#1509)
This commit improves the handling of numbers in the Kotlin lexer. Specifically, it: 1. adds support for underscore separators; 2. adds support for binary literals; 3. removes invalid support for the lowercase "l" suffix; and 4. adds support for unsigned literals.
Configuration menu - View commit details
-
Copy full SHA for 03be225 - Browse repository at this point
Copy the full SHA 03be225View commit details -
Allow empty prefix in Turtle lexer (#1494)
An empty prefix (`:` as distinct from `<prefix>:`) is permitted in Terse RDF Triple Language. However, the current lexer requires at least one character before the `:`. This commit removes that requirement.
Configuration menu - View commit details
-
Copy full SHA for 6266fc7 - Browse repository at this point
Copy the full SHA 6266fc7View commit details -
Support the 'a' keyword in SPARQL lexer (#1493)
The case-sensitive keyword `a` is a valid keyword in SPARQL. At present, the SPARQL lexer does not recognise it as such. This commit fixes that error (the rule is similar to the one used in the Turtle lexer).
Configuration menu - View commit details
-
Copy full SHA for c68336e - Browse repository at this point
Copy the full SHA c68336eView commit details -
Update keyword-generation Rake tasks (#1500)
A number of the Rake tasks that generate lists of built-in keywords for particular languages have bugs. These range from actual errors (as in the case of the Lua task) to deprecation warnings (in the case of tasks using `Kernel#open` to open URIs). This commit fixes these bugs and includes freshly generated lists of the built-in keywords that have changed.
Configuration menu - View commit details
-
Copy full SHA for 76430f3 - Browse repository at this point
Copy the full SHA 76430f3View commit details -
Configuration menu - View commit details
-
Copy full SHA for dca76dd - Browse repository at this point
Copy the full SHA dca76ddView commit details
This comparison is taking too long to generate.
Unfortunately it looks like we can’t render this comparison for you right now. It might be too big, or there might be something weird with your repository.
You can try running this command locally to see the comparison on your machine:
git diff v3.18.0...v3.19.0