[quarnster]

Aha, so that's why there are 100's of new people starring it... ;)

Hello, thanks for the interest. I hope some of you will take the time to contribute in the form of pull requests.

I just updated README.md with a screenshot, here's a direct link: http://i.imgur.com/VIpmjau.png

[uniclaude]

I really appreciate the stance you're taking with issues and pull requests. It takes balls to get a project out there, and being upfront about what you're going to accept as contributions is great. Not only because you demonstrate honesty and make things clear, but also because it is a good way not to lose your time.

I doubt I'm going to leave Vim anyways, but I really wanted to share my opinion on this point.

Congratulations and good luck.

[csbrooks]

Has anyone looked at getting it building for Windows? What would the major obstacles be?

[jpgvm]

Could you clarify the build steps please.

Especially the bit down the bottom requesting that Python 3 be built with special configure flags.

[derekchiang]

Thanks a lot for doing this project! I have been hoping for an open-source alternative for ST for a while.

As a side note, could you clarify the build section where it says we need to modify cgo.go? I'm not exactly sure what to do there. I'm using Ubuntu 13.10.

[drbawb]

Haven't gotten this to run yet because my copy of Python does not meet the criteria he listed in the Readme (`Python 3 must be compiled without sigaltstack enabled.`)

However I got it to build on Arch Linux.

First of all: modifying `cgo.go` didn't work for me. Not sure why: but it's included to late in the build process, `abstract.go` bombs out on the compilation.

These flags worked for me just fine on Arch Linux: `// #cgo pkg-config: libffi python-3.3`

That's assuming you have `.pc` files for libffi and python on your system. (Which might not be the case if you're building it from scratch.)

[flippyhead]

Yay, I'm excited to see where this goes!