Fix unreadable code in Pharo Light theme #858
Merged
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
…so it uses the user's configured code style.
|
Tx hernan! |
|
In the latest P13 this PR isn't integrated yet, is that expected? |
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.
Fix an issue reported in pharo-project/pharo#16876 that causes all Microdown Smalltalk code to be unreadable in the Calypso class comments and documentation browser.
Now Microdown code style follows the user's code style settings. This is done by resetting the textAttributes variable in the Microdown Smalltalk text styler during initialization, so it uses the user's configured code style.