Syrsly

I removed the parse functionality after several hours experimentation, but I ultimately just used the "raw" query and escaped it. Performance hit was minimal.

I take it back, the performance hit was substantial after a while.

It's easy to figure out on your own if you know how to code, as @michield said, but perhaps we should consider making these changes for people who don't really...

This happens whenever Atom auto-updates and I open something in WinSCP because WinSCP has to link to the specific version's exe. It's almost like a notice that the editor updated...

He could use the open source old version and modify it as needed.

Is this a joke ticket? Perhaps commentary on the state of Atom since it's being unjustly sunset? One of two things will happen: 1. Atom community edition will take over....

> > > Convert it into the array or serialised format, send it to the backend and update it by deserialising. :) I can confirm that this not only works...

The warnings and errors no longer appear to be present in the latest rolling release.