search

kollhof / sublime-cypher

Syntax highlighting for Neo4j's Cypher query language in SublimeText.
Other
37 stars 26 forks source link

Sublime Text 3 Support #10

Open nicosantangelo opened 9 years ago

nicosantangelo commented 9 years ago

Hey!, do you have any plans to port this to ST3?

I'm currently working with Cypher and having to use Plain Text in ST3 is not pretty :(.

If you do plan to do the port and want some help, let me know!

kollhof commented 9 years ago

Hi Nicolás,

I have not used cypher for quite some time now and other things are keeping me rather busy at the moment. Feel free to fork the repo though.

Jan

On Wed, Sep 17, 2014 at 2:44 AM, Nicolás Santángelo < notifications@github.com> wrote:

Hey!, do you have any plans to port this to ST3?

I'm currently working with Cypher and having to use Plain Text in ST3 is not pretty :(.

If you do plan to do the port and want some help, let me know!

— Reply to this email directly or view it on GitHub https://github.com/kollhof/sublime-cypher/issues/10.

brian-gates commented 9 years ago

:+1:

I'd do this myself, but I've never done any ST3 package work. I imagine it's fairly simple.

Where would one get started?

nicosantangelo commented 9 years ago

The differences between the ST3 and ST2 API aren't that big, the important thing is to modify the code to be able to run on Phyton 3 and Python 2.

Sadly most of the times you'll have to check in which version of Sublime are you running, like this:

is_sublime_text_3 = int(sublime.version()) >= 3000

I would recommend that you get sublime-cypher on your ST3 Packages folder, and from there try to resolve the issues one by one.

brian-gates commented 9 years ago

Welp, I'm out! lol.

danielcooperxyz commented 9 years ago

I managed to get it working on ST3, I didn't see any glaring problems in the code after a quick scan, but will check back if I find anything during use.

@brian-gates to get it working I downloaded the code as a zip and put the contents (excluding non-windows files) into: C:\Users\[Username]\AppData\Roaming\Sublime Text 3\Packages\Cypher

After restarting Sublime it appeared in the Syntax menu. Obviously I take no responsibility for things breaking though, naturally.

brian-gates commented 9 years ago

:+1: I'll give it a try!

nicosantangelo commented 9 years ago

@d4nc00per The command can't work on ST3, every call to print is using Python2 syntax

danielcooperxyz commented 9 years ago

Ok, I didn't spot those. I only wrote a simple create and delete script using this, as I'm new to cypher and I had no crashes.

avindra commented 9 years ago

Has anyone managed to get this running in ST3?

Yomguithereal commented 8 years ago

Hello everyone. Has this progressed since June? Can I do something to help?

brian-gates commented 8 years ago

:+1: On Mon, Nov 30, 2015 at 6:33 AM Guillaume Plique notifications@github.com wrote:

Hello everyone. Has this progressed since June? Can I do something to help?

— Reply to this email directly or view it on GitHub https://github.com/kollhof/sublime-cypher/issues/10#issuecomment-160646511 .

avindra commented 8 years ago

Switch to Atom my friends. Long live Atom !

nicosantangelo commented 8 years ago

@Yomguithereal Maybe checking the progress of #12 and giving a hand closing that PR ? ( I stopped using Cypher since I created the issue )

kollhof commented 8 years ago

Hey guys, I have stopped maintaining this repo. It would be great if someone would fork it and take ownership. I am happy to put a link to the new home into the README.

nicosantangelo commented 8 years ago

Maybe a transfer/contributor is easier? Because the problem with a fork is that someone has to update PackageControl and move the issues over.

kollhof commented 8 years ago

Adding a contributor would work, but transferring would still mean having to raise a PR against PackageControl(but thats pretty simple). Forking means more independence from my repo.

Yomguithereal commented 8 years ago

If that's fine with you, I can try to fork the repo and try to build a Sublime Text 3 package. But I cannot promise I can make the query part work since this is really the syntax highlighting I am currently lacking now.