Add to Package Control

[Frizlab]

Can this plugin be added to Package Control? I am currently using the Emacs-like modelines plugin, but I’d love to have a SublimeText-owned package for this.

[deathaxe]

This ST2-only package is registered at Package Control.

see: https://github.com/sublimehq/package_control_channel/blob/3f950f0a4fa309020ea2dbf4151867d8b5408714/repository/m.json#L2063-L2071

[Frizlab]

Oh. It’s ST2-only, that’s why 😑
Any plans on modernizing to ST3/4?

[michaelblyons]

You're welcome to submit a PR and update it. Edit: There's #8 #6 already. Does that work for you?

Can you link the thing you're using and describe some examples of the problem you're trying to solve? e.g. If you can set the syntax based on the files' location, there are probably better things out there.

[Frizlab]

I have Dockerfiles, named Dockerfile.something, that do not start with either an import nor from statement, and whose syntax are thus not automatically set to Dockerfile.
I’m using a modeline at the end of the Dockerfile to have the proper syntax.

I think you meant #6? I have not tried it. I will, but would prefer something in Package Control, preferably from the SublimeText team if it makes sense.

[michaelblyons]

I have Dockerfiles, named Dockerfile.something, that do not start with either an import nor from statement,

I use AutoSetSyntax (honorable mention to ApplySyntax) to set the syntax for trickier situations. (One example: ~/.ssh/config versus .git/config both have the same filename.)

Side tip: If you're using Dockerfile Syntax Highlighting as the package for those, I might suggest you give the Containerfile package a try.

I think you meant #6? I have not tried it.

Yes. Apologies, I meant #6.

but would prefer something in Package Control, preferably from the SublimeText team if it makes sense.

The @SublimeText organization on GitHub does not make the editor, if that's who you mean. That's @sublimehq.

I don't mind creating a new tag series for newer ST versions for this package, but only if the PR actually works. There are some comments that suggest it needs further work, possibly fixed by @MerlinDMC's fork.

[MerlinDMC]

WOW ... that's a blast from the past.

While I don't use SublimeText anymore the commits I did 12 years ago as far as I can remember were for making it ST3/PY3 compatible.

While I would love to have upstreamed it a decade ago 😆 I don't have time to get back to test the old repository with SublimeText at the moment.
Feel free to fetch the changes and get it upstreamed.
If you need me to give permission for the minimal changes I added you hereby have it Do What You Want with it.

[Frizlab]

I use AutoSetSyntax (honorable mention to ApplySyntax) to set the syntax for trickier situations.

I did not know about this one. I had a look, but I’m partisan to “explicit is better,” so I’d still prefer a modeline :)

I might suggest you give the Containerfile package a try.

Yes, good idea. For some reason I still default to Dockerfile, but I do prefer Containerfile for the obvious reasons.

The @SublimeText organization on GitHub does not make the editor

Ooops my bad. Makes sense.

But only if the PR actually works

I’ll have a look and update it if needed.

[michaelblyons]

I’m partisan to “explicit is better,” so I’d still prefer a modeline

Very fair. I have a different philosophy, but it's fine that you want to do it this way, and this repo seems like the right place for it.

a blast from the past.

Haha, yes indeed. Merlin, I'm not expecting you to do any further work than you did 12 years ago. 😛 Just don't delete your repo!

I’ll have a look and update it if needed.

Good luck!

[Frizlab]

I did #9.

It works for me: the syntax is properly set to Containerfile with this line:

# sublime: x_syntax Containerfile