Added support for --output=terminal256 and upgraded to .NET 4.7.2 and… #1
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Added support for
--output=terminal256Upgraded to .NET 4.7.2 and latest IronPython along the way...
It really bites that IronPython does not support either donetcore or Python 3.x yet. Because without either of those two, this really cool solution can't be used in a dotnet core solution. Not your fault of course, but massively disappointing to me because the project I'm targetting is a dotnet core app. Sigh.
Specifically I can't find any way to generate a
pygments.dllthat is compatible with dotnet core. Would love any ideas...For now I will have to invoke pygmetize.exe directly.