Michael
Michael
> Currently you're only matching English headers. They might not be in English as Git supports a few languages. You'd have to look that up. For this, you are referring...
Should we merge *Conflict.sublime-syntax* into the Diff syntax like #4047?
> Normal diffs won't ever contain conflict markers, would they? No, but after I filed "Conflict?" into my broad organization of diff types, I'm much more willing to concede merging...
I've brought *Conflict.sublime-syntax* back in, ~~along with a conservative side-by-side highlighter. A more risky side-by-side syntax at https://github.com/michaelblyons/SublimeSyntax-Defaults/pull/10~~ ***Edit:** Deleted side-by-side now that we have overrideable beginning-of-line.*
Rework of Git Log to use Git Diff contexts at https://github.com/michaelblyons/SublimeSyntax-Defaults/pull/11
> let us know when/if you need any review or feedback 😁 Haha. Sorry if you're flooded in notifications. The PR is a lot better after you and DeathAxe's reviews....
There are places where I have considered newlines in stacked scopes, but I am not planning to add an empty line between meta and includes. PackageDev scoping is sufficient to...
Hooray! Thanks, everyone.
I tried to send someone to the community docs for this info and realized this PR wasn't incorporated yet. :sweat_smile:
https://github.com/sublimetext-io/docs.sublimetext.io/pull/134