I've been using Atom for years on my Mac. I know it has been end-of-lifed by its dev team. I haven't installed anything new on it like plugins for many months. After the latest MacOS update, I get this popup when trying to open it:
Does anyone know if there is a way to tell if my copy has somehow become corrupted, or if this is a false positive?
Many thanks!
OK I found out that github revoked the Apple code signing certificate and is now enforcing that. I found the answer on the Atom blog. So, I was able to download an older version and it works well.
thanks for the info, i think it's the best time to find alternatives on text editors since Atom has been officially sunset (Sublime text?)
If you want the current installation to continue working:
$ xattr -cr /Applications/Atom.app
I'm not sure what the security risks of this are.
You might consider the Pulsar fork of the Atom project: https://pulsar-edit.dev/
I can't fully vouch for it because I'm just starting to use it, but it looks and feels the same to me.
Related
I have decided to update my development PC to use PhpStorm-2017.1, but before I update, I do not want to end up wasting 1-2 days re-configuring, if there are any potential issues that can hinder my work.
Will my current license work on the new version?
Will my project settings integrate with the update? (Symfony)
Will my plugins settings be kept? (Symfony)
Any other thing I need to figure out?
Answers to your questions:
1) Yes, the new installed version will automatically pick up your current license.
2) When you update, only the software is updated. The configuration files are not touched and settings are brought across as they were on the previous version.
3) Same answer as answer # 2
4) Not really. Just download the latest version from their website and install it as you would normally.
upgrading to phpstorm 2017.1 was smooth for me, (once they released some later fixes for things like the REST tool etc)
As for your plugins, it'll depend on what plugins they are, and whether there would be BC breaks. Look up the plugin documentation and check to see if there's a version for 2017.1.
For what its worth, the symfony plugin works fine.
You can try official control panel of JetBrains https://www.jetbrains.com/toolbox/app/
Manage product updates with ease
The pace of technologies and software updates is ever-accelerating. Stay up-to-date without compromising your productivity with the Toolbox App: easily maintain several versions of the same tool, install updates, and roll them back instantly if needed.
Could be useful to patch instead of complete update:
Faster updates
When updating, Toolbox App downloads and applies a patch (or even a set of patches) instead of the full package download, thus saving you time & bandwidth.
Official response form JetBrains:
It's hard to tell whether your plugins will work with 2017.1 since there are always some changes in API that may affect some of your plugins. So it's easier just to install 2017.1 and see how it goes. Installation won't broke your existing PhpStorm 2016.2 and its settings.
I believe there have been no changes in license server so if you have right on 2017.1 there shouldn't be any problems.
P.s. Thank you every one for your responses. I will be going with the official answer.
I am trying to save a simple HTML file in GitHub's Atom text editor, but I get the following error:
Unable to save file 'C:\Users\Alexander\Desktop\Looking good website\products.html'
EBUSY: resource busy or locked, open 'C:\Users\Alexander\Desktop\Looking good website\products.html'
This seems to be a known issue when I check the atom git repo. See here.
Now somehow even though there are multiple issues opened with the same problem on the atom git repo I don't see a solution.
How do I solve this error?
I am not sure how to replicate this issue but initially the file was saving fine, but now suddenly I have this problem and I don't see any obvious solution.
screenshot :
Can somebody help please?
Re-creation of error ::
Error in Atom :
What i see in process explorer::
For some reason Atom doesn't want to save files, that you have currently open in your Windows Explorer. At least that was the issue on my workspace.
I was able to solve this issue by closing all applications using the file. I was viewing a webpage locally, so I killed the browser and windows explorer then Atom let me save the file.
Hate to necro an old thread but I just ran into this myself and believe I have found the problem; the Preview Pane in Windows Explorer.
Either deselect the file in Explorer after opening or turn off the preview pane altogether.
Get Process Explorer from LINK and use Ctrl+F to find the process keeping the file open (see MS support link)
Then tell me what you see, and I'll expand the answer :)
My anti-virus (Bitdefender) thought atom.exe was an unsafe application so it kicked on Ransomware protection.
Hope this helps somebody
I’ve been having the same issue, and I found what was causing it for me.
I had Windows Defender Ransomware Protection enabled on my computer, and I was trying to save to a protected folder. Even though I had whitelisted the atom app, and didn’t receive the usual warning from Windows, it was preventing me from writing to the location. Disabled Ransomware protection, and suddenly Atom can save there again.
Not sure if you’re in the same boat, but maybe give it a try if you have Ransomware Protection enabled. Or maybe some other anti-virus with the same feature?
Can someone explain me how should I install sts like some years back when I run some bash script and sts was installed ? With this new era when I just download sts and extract it to directory and run it I have a lot of problem. For example sometimes I can not open wsdl or xsd file in default editor and I need to use just text editor and so on. Here are error log of my sts:
http://pastebin.com/ePk7LnL2
I am using sts 3.6.3 download from this source: sts3.6.3
It looks like you installed additional plugins and it this looks like this caused a dependency issue between installed bundles. This disables certain bundles under the hood and that might cause the issues you describe.
I would recommend to download the latest STS 3.6.4 version and start with a test installation from scratch. Use that vanilla STS install to see what is working out-of-the-box and what not. If there is something not working, please file a bug at https://issuetracker.springsource.com/browse/STS. If everything works as expected, install add-ons step-by-step to figure out which install breaks something else.
That way we can find out what is going wrong and how to fix that specific problem then.
Hope this helps!
I've got a (what I assume to be) rather simple question regarding the installation of cvxopt on Windows. I'm following this "guide" http://cvxopt.org/install/index.html. But I've got stuck on the part where you're supposed to
Copy libblas.a and liblapack.a to the src directory.
I think it's fair to say to I'm very lousy at these kind of things and that I've got no idea of what I'm doing. So I would be greatly helpful if someone could tell me where I could find these. I guess it has something to do with:
make lapacklib && cp liblapack.a ..
and
make && cp blas_WIN.a ../libblas.a
But I can't really make anything of this...
Thanks in advance!
cvxopt is included in WinPython. Even if you won't use WinPython directly, it's probably the easiest way to get cvxopt on Windows: After installing WinPython, you can copy the cvxoptfolder from the Lib\site-packagesdirectory into the corresponding one of your Python distribution.
Edit:
It's again available under the unofficial windows binaries.
Unfortunately the cvxopt 1.1.7 currently distributed with the unofficial windows binaries has issues with the current winpython 2.7.6.4 (or maybe has issues on its own). In my experience you could encounter many weird problems like code throwing math domain errors or arithmetic errors where things used to work perfectly fine on winpython 2.7.6.2 and the cvxopt 1.1.6 included there. I do not think that it is a problem with cvxopt 1.1.7 since it works fine on linux, rather of the specific binary packaging or maybe incompatibility of such packaging with the latest winpython.
If you are encountering such issues, maybe you can stay with winpython 2.7.6.2 that is the last version shipping a working cvxopt.
Some of you may have already read my unanswerd question "Node Gallery won't show images with Plupload" AND this query is a follow on, because I think if I solve this issue, I will have found the solution to my previous one, as I missed out a step!
I am trying to patch the Plupload module with the plupload_url.patch, on my laptop running a 64 bit version of Windows 7, but every method I try fails; I think it says the file format isn't supported! So far I have tried GnuWin32 (but I think the clues in the name there), and also the JDiff Plugin for jEdit! So, has anyone been in this situation, or do of a working solution? Any advice would be greatly appreciated!
I do have a VirtualBox installation of Ubuntu if there are no other alternitives, but I'd prefer not to use that because transfering files from the Guest OS is a pain in the ass!
If I understand correctly, the problem is that you can't apply the patch and want to know how to do so.
Here's an explanation of path files which may help: http://drupal.org/node/367392
Also see if http://drupal.org/node/14231#comment-22770 and http://drupal.org/node/100527#comment-176252 helps.