Closed mvirenius closed 10 years ago
This will more than likely be because it can't find your Vagrantfile, open up the quick window (Ctrl-`) and see if there are any vagrant related error messages in there.
I checked the Console window and I didn't find any Vagrant related or any other error messages there. I also know that the plugin should throw an error if the Vagrantfile isn't found.
My directory structure is following:
.vagrant data (shared folder containing the project files) Vagrantfile
I've added some extra debug to the plugin to help with this, if you add "debug": true
to your user preferences and then open up the console window again and try to run any of the Vagrant commands. The plugin should be updated automatically when you start ST3, but you can always force it through Package Control.
Might be an idea to make sure your vagrant file is committed, this will help work out where your problem is so i can provide you a proper fix.
After updating the plugin, it now detects my Vagranfile and allows me to use other commands too. Thank you!
It must have been the fix I added for ST3 support. I'm glad it's working.
I'm using the latest build of the Sublime Text 3 (3047). I installed the plugin, but I can't use other commands than "Vagrant init", which I don't want to use, because box has been already initialized.
Any suggestions?