search

subhaze / sublime_codekit

Sublime Text plugin to run CodeKit 2 commands
35 stars 1 forks source link

Enable/disable plugin on a per project basis #8

Closed redgluten closed 8 years ago

redgluten commented 10 years ago

First thanks a lot for the great work. I really find it useful on my everyday work.

On certain projects I’m not able to use Codekit because I have to use the Grunt or Gulp team workflow so it would be handy to be able to tell Sublime Text to disable the plugin for this specific project.

Now : is it a Sublime Text feature or a sublime_codekit feature? I’m not sure but I guess you do. :)

subhaze commented 10 years ago

It could really go either way.

A property called disabled_codekit_commands could be checked for in sublime settings, which would allow for either a global disabling of the plugin or per project if added to the project settings file.

Another way could be this plugin automatically handling enable/disable based on whether a config.codekit file is found within the folder tree of the currently edited file.

redgluten commented 10 years ago

That second option sounds pretty good to me. No configuration is always better. :)

subhaze commented 9 years ago

Sounds like a plan, I'll see about getting this in soon. Also, glad to hear this is helping your workflow and I appreciate the feedback, thanks!

subhaze commented 8 years ago

This should be fixed via commit https://github.com/subhaze/sublime_codekit/commit/426afb6b69a476a985ddae471d1e6ebc041b36f5 (forgot to add this issue to commit)