Skip to content

feat (schemes): Add Everforest color scheme#822

Closed
morph626 wants to merge 3 commits into
SublimeText-Markdown:st4-developfrom
morph626:st4-develop
Closed

feat (schemes): Add Everforest color scheme#822
morph626 wants to merge 3 commits into
SublimeText-Markdown:st4-developfrom
morph626:st4-develop

Conversation

@morph626

@morph626 morph626 commented Jul 4, 2026

Copy link
Copy Markdown

Added a fork of @sainnhe's Everforest color scheme (originally for Vim and VSCode) with Monokai-inspired extra highlighting for Markdown including the new python admonitions:

Dark (medium contrast) w/ extra markdown highlighting

Screenshot_Markdown_Dark

Light variant

Screenshot_Markdown_Light

Admonition support

Screenshot_Admonitions

@deathaxe

deathaxe commented Jul 4, 2026

Copy link
Copy Markdown
Member

Color schemes in this package target Markdown syntax only and exist only for compatibility reasons.

Provided color schemes appear to apply rules for many syntaxes. Should those be published as separate package?

Comment thread schemes/Everforest Dark.sublime-color-scheme Outdated
Comment thread schemes/Everforest Dark.sublime-color-scheme Outdated
@morph626

morph626 commented Jul 5, 2026

Copy link
Copy Markdown
Author

Color schemes in this package target Markdown syntax only and exist only for compatibility reasons.

Provided color schemes appear to apply rules for many syntaxes. Should those be published as separate package?

Oh, I didn't realise! I will remove the unrelated scopes.

morph626 and others added 2 commits July 6, 2026 16:20
- Corrected 0 to '' for 'font_style' where 'font_style' needed to be cleared
- Removed all scopes specific to a language other than markdown
@deathaxe

deathaxe commented Jul 6, 2026

Copy link
Copy Markdown
Member
  1. MarkdownEditing specific color schemes start with MarkdownEditing- naming.
  2. Language specific tokens may be at least useful for proper highlighting of fenced code blocks. The major point however is - instead of removing them - why not adding a new separate "Everforest" color scheme to Package Control, if rules for most languages are present anyway?
  3. Color schemes in this package exist for backward compatibility and are barely (not) maintained. There's not much interest in adding more, because it is better practice to create global color schemes, which work for all use cases (writing prose in Markdown/RestructuredText/AsciiDoc/Textile/...) or coding (C/C++/Python/...).

@morph626

morph626 commented Jul 6, 2026

Copy link
Copy Markdown
Author

Aaarh sorry, I missunderstood and thought it was a code base convention thing. I take your point and will scrap this PR in favour of its own package. Thanks for taking the time, and just wanted to ad that I've been using MarkdownEditing for ages and it is wonderful how active you guys are.

@morph626 morph626 closed this Jul 6, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants