ST3 coming? about colorhighlighter HOT 9 CLOSED

The plugin is completely open-source, so it might, but i dont think i want to do it myself right now, since i dont even use ST3: it's not that different, and im to lazy to update it from ST2 :)

from colorhighlighter.

I'm using Kronuz ColorHighlighter fork and it's working great on ST3. Give it a try, @JerseyMilker .

from colorhighlighter.

Okay thank you. Kronuz's fork works great, thank you! Too bad it's not available through Package Control... @Monnoroch, would you be open to merging Kronuz's branch with yours and re-releasing for Package Control? Or should I approach Kronuz to see if he might be willing to release his ST3 ColorHighlighter fork on Package Control?

from colorhighlighter.

I have also installed Kronuz's fork on ST3 and works like charm! 💃

from colorhighlighter.

The problem is that his fork breaks the ST2 support. I would love to do the merge, but i just can't do that right now.

from colorhighlighter.

Fair enough :) Are you open to someone like Kronuz releasing his fork as ST3 package for Package Control?

from colorhighlighter.

The problem is that his fork breaks the ST2 support. I would love to do the merge, but i just can't do that right now.

I wonder if we could setup a "ST2" branch and use the master branch for "ST3"? Or vice versa? One of the branches could just use git to pull that branch into the /Packages folder until things can be resolved later.

I've always been a fan of having one main repo for things; makes for less confusion.

@Monnoroch this probably won't help to motivate you, but I have an upgrade guide here:

ST3: Setup

I was in the same boat as you a few months back ... I wasn't looking forward to the upgrade. Now that I'm using ST3, I'm really liking the new version of the app. I wrote down the above steps so I could upgrade my other machines so that they all match. Anyway, maybe it will help to motivate you?

Again, the thought of having a ST2 branch and ST3 (master) branch does sound tidy.

Anyone here know if Package Control can register branches of a repo? If it can, I'd suggest:

1. master branch == ST2 (Package Control labeled for ST2).
2. st3 branch == ST3 (Package Control labeled for ST3); this would be @Kronuz ColorHighlighter fork.

This type of setup would allow for the st3 branch to be merged into master down the road, once ST2 has become obsolete.

Am I talking crazy here? 😆

from colorhighlighter.

ST3-related open issues: #36 #37 #33

from colorhighlighter.

Dont know about package control branches support. If it does, id love to do as you suggest.

from colorhighlighter.