*pending
I don't have much time either and as starting to learn GO I think tests are a good place. The issue is the watcher_test.go from packages fails on OS X but passes on Linux (Ubuntu to be precise) so I thought it may be due to differences in path handling. However now I think the issue may be with the File callbacks. Need to keep digging
Once all the tests are passing, do we have some sort of CI going on?
Sorry if it's a dumb question, but I've been reading the docs for the rjeczalik/notify package trying to make sense of the missing callbacks in OS X Darwin. Does anyone know how can I tell wether the eventswe should be getting are Kevents, FSEvents (InotifyEvent seems to be only for linux) or can point me to some more info on the web? Forgive me if this is "obvious" by looking at the code I'm new to GO and fairly new to "high level" apps
I have been on Go for a while and wanted to contribute to a real world project
I stumbled on the limeText project and wish to contribute
Hope I am welcomed to do so :)
I think I've found a way to solve it. But needs reviewing
looks good to me
There is probably a
brew command to install it
Also, what is with Bountysource screwing up all the issues?
But many, if not most of the issues have broken formatting
I'm inclined to just drop Bountysource, since it doesn't seem to work as an incentive :)
We have some money donted to the org which we could put up as bounty on issues
There are just too many issues to choose from
I also have a Go/QML terminal emulator which works okay for simpler terminal sequences, with fun features like 256 color support that would be easily integrated into LimeText
And sidebar tree stuff is mostly done IIRC
I've just been stuck trying to fix qml-go