I've installed a couple of Sublime Text 3 packages recently and have noticed that some of the commands that should be available via the package do not show in the command palette, though other commands for the same package do.
Specifically, I installed the package PHPCompanion and all of the commands show in the pallette but insert_php_constructor_property:
Or the package PHP Getters and Setters, none of the commands are available.
I'm actually not even sure where to start as far as troubleshooting this. Most of the links I've found so far say "uninstall the package and reinstall it" (which I've done) and "make sure the packages aren't in your Ignore Packages preference properties" (which I've confirmed).
Is there something else I can do to figure out why the commands are not available?
I figured out how to fix the issue (though I still don't know what the issue was).
I deleted the Sublime Text app and installed a new version from the sublime home page. After launching the new version the commands started showing up.
Note that I only deleted the app itself, I did not delete the Application Support or Preference files. This means all of my previously installed packages, themes, and even session were all still in place.
Hopefully this helps anyone else that runs into the same issue.
Related
I am trying to install the Local History package in Sublime 3. I am behind a proxy and so far have not been able to get package control to work so I am installing the package by pulling the repo into my packages directory.
When I installed it the first time I had Sublime Text 3 open and was surprised to see that the Local History commands appeared with out a restart. However, they did not seem to work so I restarted Sublime Text. Package gone.
I have reinstalled it, and stopped and started Sublime multiple times and for whatever reason everytime Sublime starts it removes the entire Local History package from my packages directory.
I have several packages installed in Sublime Text 3 and they all work without issue. This is the first time I have encountered this issue. Any ideas what may be going on?
Go to Preferences -> Settings-User and check if Local History is listed under ignored_packages. If that's the case the package fails to load. Normally deleting Packages/User/Package Control.cache directory solves the problem.
I've just recently started using gulp.js in my projects and I've been trying to learn and use terminal a lot more.
When I run npm commands from the mac terminal default console everything works great however when I run the same commands in PhpStorm the command is not found.
I've followed PhpStorm's guides on installing and integrating the NodeJS plugin etc but I cant seem to get any of the commands to work through it even though its in my usr/local/bin and was installed globally etc.
When I SSH to vagrant though I can use the npm commands etc. Would anyone happen to be able to suggest anything?
This one is quite old but I came across the same problem.
What I did was enter the terminal settings under tools > terminal, go to Application Settings, and change the Shell path to the one you need.
Click the ... button and select the one that suits you.
My setup
I already installed gocode with the command go get github.com/nsf/gocode.
I use Pathogen to manage my Vim plugins. I installed vim-gocode with git clone git#github.com:Blackrush/vim-gocode.git.
What I’m seeing
The :Fmt command works ok, but I can’t autocomplete my golang code. It reports an error like in this image:
Can someone help me?
Please ensure you have YCM or neocomplete installed. You need some additional binaries to get all features. Following on the vim-go repo tells you how to install them.
All necessary binaries should be installed (such as gocode, godef, goimports, etc.). You can easily install them with the included :GoInstallBinaries command, by running command in your vim.
Note: I´ve searched for sublime here at the forum first, in order to post a question, because I wasn´t sure if this question was adequate for this specific forum and wanted to compare it with other posts. If it shouldn´t be here, please tell me so, and I´ll gladly close it here and open it in any other stackoverflow´s forum. Thanks.
I´ve just installed sublime3. After that I´ve installed package control.
But even when I try and install some packages using package control not all packages get installed, even when I get the "successfully installed" message at the bottom of the window.
To install a new package I go to preferences/package control/install package, and after getting the "successfully installed message" I go to /list packages and it´s not there.
I realised that maybe that´s because some packages are not compatible with sublime 3 (even there it shouldn´t be the successfully installed message there).
So, I´ve tried the latest sublime3 version of emmet, but it seems that´s not working (I´ve tried some shortcuts without any success). So I´ve watched Chris Coyer screencast to check out if I´ve missed something, but it still won´t work.
I´ve tried installing it manually: I´ve went to C:\Program Files\Sublime Text 3\Packages (I´ve installed the x64 package, but for some reason it´s not installed into \Program Files (x86)).
And then I copy/paste the unzipped folders of /emmet-sublime-master and /PyV8 (I´ve tried naming the folder just emmet).
And still, it won´t work. This kinda happened to me with a lot of packages, I´ve installes several of them, and when I go to preferences/package control/list packages, I get only 3 of them.
I came across this issue as well. This thread (https://github.com/wbond/package_control/issues/874) directed me to delete the entry for Package Control under "Ignored Packages" in my User Settings File. Once that was deleted, I restarted, and it worked as expected.
In SublimeText go to Preferences -> Settings. In the opened file Preferences.sublime-settings remove Package Control from ignored_packages list (see below). Save the file and restart Sublime.
{
"font_size": 11,
"ignored_packages":
[
"Vintage",
"Package Control" <---- REMOVE
]
}
For me, Package Control was already removed from ignored_packages, so that didn’t help. But the Sublime Text console held messages which indicated the problem. (Press Ctrl+` to open the console.)
PermissionError: [Errno 13] Permission denied: '/home/myuser/.config/sublime-text-3/Cache/Package Control/merged-ca-bundle.crt'
And changing ownership on the Package Control directory allowed me to use Package Control again:
chown -R myuser:myuser '/home/myuser/.config/sublime-text-3/Cache/Package Control/'
For me, after try to remove and reinstall the Sublime and verified the ignored_packages, I installed python and restart the sublime. So it worked.
In Terminal:
sudo apt install python python3
I am using Ubuntu 20.04.
This morning, I started getting that message when I attempt to open a file in Vim. Vim is my editor of choice for config files, git commit messages and the like, but is not my day to day code editor. I clearly did something to invite this message, but I have no idea what. I did recently uninstall an older version of XCode from /Developer-3.2.6, but that's the only thing that comes to mind that seems even tangentially related.
I'm running OSX Lion. Is Excuberant ctags part of the base install? I know I didn't install it intentionally, but if it's not native, then maybe it came along with something else? Any ideas about how to either get the plugin back or remove references to it so I don't get the warning message?
Thanks.
For Ubuntu and derivatives:
sudo apt-get install exuberant-ctags
With yum:
sudo yum install ctags-etags
FWIW I had the same error message on Ubuntu, I simply installed ctags and everything hunky dory. Thanks :)
That looks a lot like the message the taglist plugin emits when it can't find a ctags program. If you run :scriptnames, do you see plugin/taglist.vim in the list of sourced files? If you do, then you'll probably want to remove that and doc/taglist.txt under the same directory structure.
If you are using Gvim in a Windows system, you should download a ctag Windows program (that is ctag.exe) and put the ctag.exe in the vim74 file dir, then reboot Gvim, and it will find it and use it! I hope this is helpful.
Take a look at this: http://vim-taglist.sourceforge.net/installation.html
Thanks, guys. I ended up reinstalling XCode and it looks like the problem has gone away. I have no idea how I got it into whatever state it was in, but it's back now and everything looks to be back to normal.
I encountered the same issue after upgrading to Mountain Lion. I fixed it by reinstalling the CLI tools from XCode preferences > Downloads. I had the CLI tools installed before upgrading. Not sure what happened, but it works now.
I encountered this issue on a host, but I didn't have permission to install any packages.
But i did find out the gctags was present on that system.
I created a softlink for the gctags binary in a location that was included in my PATH environment variable.
$ln -s /usr/bin/gctags ~/bin/ctags**
You can do the same if you find etags binary in your system, and have no way to install any packages.