When I tried to remove SublimeLinter on Mac I deleted the package, cache, every part of it in Application Support but it seems I can’t get rid of it in SublimeText 3.
I open ST and I instantly get a message in a new tab from PackageControl telling me that SublimeLinter installed successfully and all the folders and files are created again. Couldn't find any solution online. Thanks in advance for your help!
You need to uninstall it via Package Control. Hit Command ⌘Shift ⇧P to open the Command Palette, then type pcr and select Package Control: Remove Package. Scroll down the list, or type sublimelinter, hit Enter, and restart. You should be all set after that.
This worked for me guys, I deleted the windows app version of Python because there was two paths when I typed "Where Python" on CMD. Then after I deleted Anaconda and reinstalled it, it fixed itself.
Related
I am practicing Django in atom text editor and install Platformio-ide-terminal package but after installation when I click to the + sign on the bottom left it is showing me blank console
my expected result is console with some directories but it is showing me blank space with a blinking cursor
Update, August 20, 2019
The issue was fixed in Atom v1.40.1
Old answer
The said package is currently not working with Atom v1.39, since it includes a major update for the underlying Electron framework.
You can try and rebuild the package's native modules. To do so, run apm rebuild inside the ~/.atom/packages/platformio-ide-terminal folder.
If that doesn't work, one workaround is to downgrade Atom to v1.38.x and wait for a fix.
For futher infos on the problem, you can follow this discussion or subscribe to the issue on GitHub.
try to reinstall the Platformio de terminal it works in my case.
I've looked around but I've only found answers for past versions. I have a new version of WebStorm and I want to open my projects from the command line, but wstorm . and webstorm . doesn't seem to work.
I've tried going to Tools > Create Command Line Launcher... and I get this:
I go to ToolBox's WebStorm Settings and I'm met with this:
Generate shell scripts is turned on, but the but the commands still do not work in my terminal.
Am I missing something? Am I supposed to add in a Shell scripts location? I'm not entirely sure I understand.
It's actually very easy. First you open up Webstorm, and press SHIFT twice. This will bring up a search box, where you type: Create Command Line Launcher. You will see a search result from Tools will be highlighted, click on it, and it will suggest the default path. Just click on Ok. Your command line launcher is now ready, so you can open terminal, cd to your project root folder, and type webstorm ./ to launch webstorm.
If the Create Command Line Launcher option is not working, try the following:
If you are on MacOS, try adding the path as instructed in their official page. And if you are on Linux, just uninstall the current version and reinstall as a snap package using sudo snap install webstorm --classic. This way, you can launch it from the terminal just by typing webstorm
After opening a ticket with Jetbrains support, the default path is /usr/local/bin. Adding this worked.
You can use open-ide tool. It allows you to define all of your editors and to open any folder with your editor straight from terminal
Error message showing is :
The specified target component - nb-base/8.0.1.0.201408251540 was not
found in the registry. The installer can continue as if the target
component was specified. Click yes to continue, No to exit the
installer.
I have tried a lot to uninstall my NetBeans8.0.2 but were unable. After lot of googling found out a solution. I think I should have and entry in stackoverflow.
Best way to remove Netbeans can be done using following steps
Remove the Netbeans folder from program file
Delete the .nbi(hidden) folder from your C:\User{Current User}
Go to control panel and remove it
It works for me hope it will you too!
Actually Devashish's answer is (partly) correct. If you click link provided by him, you will see that the problem (most likely) is because the install was done by a different user than the user who is uninstalling. (In my case, I added an admin user after the Netbeans install, so all computer changes now pass through the admin user)
Here is what I did to complete the install:
Find a .nbi folder under C:\Users\folder. This folder has .nbi folder under it
Open a command prompt and Go to NetBeans folder which has uninstall.exe
Run this command in the command prompt:
uninstall.exe --userdir c:\Users\folder\\.nbi
folder is the folder you found in step 1.
This uninstalled for me. Hope it helps you.
Go to C:\Users{User}\AppData\Roaming\NetBeans
Delete "lock" file
Uninstall NetBeans
Please follow the link to have a solution:
https://netbeans.org/bugzilla/show_bug.cgi?id=251943
The comment 5 has easiest solution:
Run Command Prompt in Administrator mode and run the following command :
uninstall.exe --userdir c:\Users\Administrator.nbi
Does not seem to work in my Win 10 environment. I've also tried
.\uninstall.exe --userdir c:\Users\Administrator\.nbi
.\uninstall.exe --userdir c:\Users\Administrator.nbi
'NetBeans 8.0.1'\uninstall.exe --userdir c:\Users\eric_2\.nbi
.\'NetBeans 8.0.1'\uninstall.exe --userdir c:\Users\eric_2\.nbi
.\'NetBeans 8.0.1'\uninstall.exe --userdir c:\Users\eric_2.nbi
You get the point. I'm running the WindowsPowerShell as an Administrator.
Someone here must have successfully deleted it even with the error message from the OP. I just have to find out who!
Eric
After struggling here and there, I:
Opened c:\Users\XXX\AppData\Roaming\NetBeans\8.2\lock where XXX was the user name. Then, I renamed lock. (The name didn't matter.)
Then, I went back and uninstalled NetBeans.
By the way, I had to delete Java separately.
I was having the exact same problem as above.
Prior to the "symptoms", I installed the application in a newly created folder on the C drive (Not the Program Files default installation directory).
I then changed the name of the folder directory where the executable was installed to enable a third-party script to launch the NetBeans executable as the script required no spaces in the path. In any case, in attempting to uninstall the application again, I got the above error.
I tried running the command as outlined above (namely) running the command prompt with the following:
C:\Netbeans\NetBeans 8.0.2>uninstall.exe --userdir C:\Users\mark.burl.nbi
it launched the uninstall but the same error popped up.
I then undertook the following and the problem was solved for me:
I manually deleted the NetBeans executable folder.
I then reinstalled NetBeans to the default Program Files location.
I then uninstalled NetBeans again no problem.
From PowerShell as administrator I removed all directories here described and finally enter regedit and search for all occurrences of “NetBeans (x86)”. And delete all of them then restart and after that everything is clear
You need to do the following:
Go to C:\Users{User}\AppData\Roaming\NetBeans
Delete the folder named after your Netbean version you want to uninstall
Uninstall NetBeans
Finally i found the reason. i.e while installing NetBeans i used our IT Team Admin credentials (assume user-1 ). But i am uninstalling with my credentials(assume user-2).
So, you can't uninstall. Follow below steps.
1.Go to C:\Program Files\NetBeans 8.0.1> you will find uninstall.exe file.
2.Find who is installed your netbeans for me user-1 (Admin).(You can find all users here C:\Users )
3.Then search for .nbi folder you can get at C:\Users\{user-1}\.nbi
Note: here user-1 is who installed your NetBeans initially.
finally open cmd prompt and run the command below given.
C:\Program Files\NetBeans 8.0.1>uninstall.exe --userdir C:\Users\{user-1}\.nbi
referred from https://stackoverflow.com/a/45387962/10971996
I had the same problem and no matter how hard I tried it won't uninstall until I installed it all over again then uninstalled.
Stop/ pause protection for your anti-virus. Then click on un-install. It will work for sure.
I installed Visual Studio Code 1.1 with the C/C++ extension,
opened my C++ project and tried to use "Go to definition" in vain.
The "Go to definition" is not working at all.
Example, go to definition of a class member:
int i = m_myVar;
(I opened a simpler project with one file and it was working for this one)
In the end, what I want is good indexation of my big project, is there a way to install Intellisense?
I had a the same issue: F12 and Ctrl + Click and Right Click "Go To Definition" wasn't working.
The fix for me was:
Go to Extensions
Click "Disable All Installed Extensions"
Close and Reopen VS Code
Back to Extensions and "Enable All Extensions"
Essentially enable/disable all extensions fixed the issue.
I recently came across this same issue and after trying all of the suggested solutions I could find with no success, I found this article:
https://code.visualstudio.com/docs/setup/linux#_visual-studio-code-is-unable-to-watch-for-file-changes-in-this-large-workspace-error-enospc
Basically my project grew too large and VS code was no longer able to track all files, which messed up the "go to definition" functionality.
After following the steps on the link to increase the maximum number of files to be tracked, the issue was resolved.
The correction is pretty simple (tested on Ubuntu 18.04):
Add this line:
fs.inotify.max_user_watches=524288
to the end of the file /etc/sysctl.conf
After saving, run the following command:
sudo sysctl -p
Hopefully this will be useful to someone else, this has been bothering me for the last few days.
I had a similar problem except with Python and google searches for solutions kept bringing me back to this post so I figured I'd post my solution here in the hopes that it might help other people.
I was working on a remote cluster through VScode Remote and was getting similar errors to the original question(all 'go to ___' functionality was unavailable and was even getting a 'too large to track' error) and I thought I had to increase the number of watches, which didn't end up helping.
All I needed to do was install a python interpreter on the remote VScode server. This fixed my problem.
I believe vscode 1.1 (well, 1.1.1 actually) + the C++ extension (cpptools) is as much Intellisense as we can get for now.
You should load your big project with the "open folder" function to make vscode know about the other files.
https://blogs.msdn.microsoft.com/vcblog/2016/03/31/cc-extension-for-visual-studio-code/ warns about letting the indexing finish first (red icon in lower right corner during indexing) and mentions the current limitations on the source code parsing.
It wasn't working on my laptop as well after installing a few VSCode extensions. I decided to close and re-open VSCode with administrator permission and suddenly it sorted out.
I have been trying to fix this for a long time. In the end, what worked for me was simply reinstalling VSCode, then installing the latest C/C++ extension (v0.18.1). Then, in your .vscode/c_cpp_properties.json file, under includePath, add your include folder which has all your header files.
I tried the methods mentioned in this thread none of them seemed to work for me. A simple solution that worked for me is that I closed the current workspace and created a new workspace, added the folders which I required(same as the old workspace), and saved the new workspace. Waited for a couple of minutes to index and IntelliSense is able to find definitions now.
I am using VSCode 1.52.1 on Ubuntu 20.04.
In my case, for whatever reason,c_cpp_properties.json has become set to Disabled in ~/.config/Code/User/settings.json.
Manually changing it to Enabled solved the problem.
Fixed mine by UNCHECKING C_Cpp > Default > Limit Symbols To Included Headers
Your mileage may vary. Good luck!
Have you saved your workspace? Or did you just open a folder with File->Open Folder? This question already has many answers, but none of them address this case, which was my issue.
The question is not specific enough for me to know if you are having the exact same symptoms as my case.
If:
You have not saved your workspace. vscode doesn't say "(workspace)" at the top of the window.
None of the goto functions are working, but instead report: "No ___ found for ____"
The tag parser database icon in the bottom right is always there but only reports "Parsing open files", rather than telling you how many files have been parsed.
Then:
Try saving your workspace.
If you have multiple versions of a language on your PC, specify the exact language you are using in the VScode(in my case, I am using Python, so I must specify the version to the python Interpreter in VS Code)
If you could not do it whatsoever, then uninstall all the other versions that you don't use and then if you go to VS Code, it will ask the version to be used, and you would have only one version, so when you select the version, the "Go To Definition" will be activated.
I was having a similar issue with java on Ubuntu 20.04 using OpenJDK version 11 (openjdk-11-jdk in apt). At first I didn't have the JRE installed, so I installed it and it still didn't work.
Afterwards, I went to the CTRL + SHIFT + P menu and then to Java: Configure Java Runtime, there I saw in the Java Tooling Runtime tab that /usr/lib/jvm/java-11-openjdk-amd64 was selected, changed it to /usr/lib/jvm/java-1.11.0-openjdk-amd64 just to see if it would work, and after a restart it did. I'm not sure why this is, but I hope it may help somone else.
For python ensure your code analysis settings are correct. In my case the languageServer was accidentally set to 'None'. Reverting it to 'default' or 'pylance' did the trick.
Just to inform if none of above works then
In my case i was using Kite extension in my VS code, I just disabled it and it worked. I think kite extension is blocking this feature.
OS: Linux Ubuntu 22.04
if you encountered with following error:
"The .NET Core SDK cannot be located. .NET Core debugging will not be enabled. Make sure the .NET Core SDK is installed and is on the path."
Normally Vscode remains unable to locate .Net sdk. need to set path manually.
sudo ln -s /snap/dotnet-sdk/current/dotnet /usr/local/bin/dotnet
restart omnisharp & restart vscode
No need to do anything. Just close and re-open. It will work.
I also faced similar problem. In my mac os cmnd + 'click' is used to 'go to definition' then it suddenly stoped working. If that is the case then please follow these steps:
restart vs code
restart pc
uninstall all extensions and reinstall again followed by a pc restart.
I had a similar issue with the extension C/C++ installed. I solved it by downloading an older version of the extension and upgrading to the last version. Somehow it solved the problem...
I'm trying to install iCloud on my Windows XP Pro (SP3) PC. Officially it's supported only for Vista and later, but this hack is widely claimed to work:
Open iCloudSetup.exe file and unzip its files including
Navigate to and open the iCloud.msi with Orca.
In the left table select LaunchCondition. Then change in the right table “VersionNT> = 600” to “VersionNT> = 200” and Save.
Run modified iCloud.msi and install.
Run iCloud Control Panel, located in the Windows Control Panel, and set up as you want.
I tried that promising solution in vain. It seemed to successfully install iCloud, but whenever I try to run it I get
this obscure error
After much fruitless searching I've not found out how to proceed from there and would appreciate advice please.
That trick worked with only the firs versions of iCloud Panel, the v1.0.
For the v2.1 doing the trick the installer ran ok, but when trying to run the iCloud Panel it showed the error you're refering to.
I had some computers running with that older version without any problem.
Try downloading the v1.0 version here:
http://icloud-control-panel-for-windows.uptodown.com/descargar/22412
If you want to try the trick with the v2.1 you have the installer here:
http://icloud-control-panel-for-windows.uptodown.com/
Remember you need to extract the MSI from the exe to do the trick. After running the exe check the %TEMP% folder to get the MSI file.