Move Kotlin package#9391
Conversation
Package ReviewChannel DiffRemoved (none), changed Kotlin, added (none). Review for Kotlin 2026.04.24.13.41.52 |
|
(Alternatively, @vkostyukov if you want to maintain it and cut a new tag in your repo please let me know) |
|
I'm totally ok with transferring the package, although @vkostyukov is of course welcome to object. Let's give that about 2-3 weeks. If we're doing that, we should als move to tag-based releases and that will also ensure your work gets picked up by existing installations. I would also propose to make some changes to the readme. Maybe reference the previous package so that people can go back if they need to. And typically a link to language documentation, and stuff like how-to-contribute etc. Like, what are the yaml tests for and how does one work with those? I get the sense that LLMS should be pretty good at this stuff, especially if you start from good syntax tests, and give it good context. Which might also be something you'd want to put in the readme so others can contribute fixes in a way that fit your approach here. |
|
Oh, once we're ready to merge, it would be good to first update the depending packages to be forwards-compatible. |
Package ReviewChannel DiffRemoved (none), changed Kotlin, added (none). Review for Kotlin master-c353694-2026.04.24.18.45.09 |
|
Since this package provides a syntax definition with |
Package ReviewChannel DiffRemoved (none), changed Kotlin, added (none). Review for Kotlin master-c353694-2026.04.24.18.45.09 |
|
Updated the json to restrict to ST4075, I think I did it correctly but please give it a lookover. Also added some meat to the README, esp. around the contributing part As for the other packages with
|
Repo: https://github.com/guille/sublime-kotlin
My package is a Kotlin syntax. Rather than have a "Better Kotlin" package I figured this made more sense.
Two disclaimers:
I would understand if the change is rejected. I initially wasn't going to submit it because I don't think a lot of people use ST for Kotlin but it's been pointed out that Sublime Merge would also benefit from a better syntax.
The only "breaking" change beyond better highlighting is the scope name changes from
source.Kotlintosource.kotlin. The only places I can imagine that would cause issues is in LSP-Kotlin and AFileIcon. If this is accepted I'd submit patches there too.Comparison
Before
After:
