proton

https://github.com/dvcrn/proton
2016-01-28T03:19:58.000184Z

Oh, okay. My README will be pretty trivial anyway.

dvcrn 2016-01-28T06:02:59.000185Z

@austincrft: looks good to me so far! Just the readme link fix and I’ll merge it :simple_smile:

martinklepsch 2016-01-28T09:59:29.000187Z

@dvcrn: I used atom the whole day yesterday, didn't bother setting up REPL yet but it's working ok-ish in general

martinklepsch 2016-01-28T09:59:46.000188Z

it's a bit laggy occasionally, is that similar for you?

dvcrn 2016-01-28T10:00:07.000189Z

the only problem I have is on initial save. Some plugin blocks the save event and I couldn’t find out which one yet

dvcrn 2016-01-28T10:00:13.000190Z

do you mean that?

martinklepsch 2016-01-28T10:03:18.000191Z

not really. I got the impression that it's more "constantly than that"

martinklepsch 2016-01-28T10:03:41.000192Z

I'll try seeing if I can come up with a better description

martinklepsch 2016-01-28T10:04:05.000193Z

def. appreciate all your work on this 👍 more beginner friendly editing environments matter! :simple_smile:

martinklepsch 2016-01-28T14:08:10.000194Z

getting this when trying to start a proto-repl: Error starting repl: Error: spawn lein ENOENT

martinklepsch 2016-01-28T14:08:21.000196Z

looks familiar to anyone maybe? :simple_smile:

martinklepsch 2016-01-28T14:10:38.000197Z

the directory it's starting in seems fine

2016-01-28T14:12:08.000198Z

That's an error in the proto-repl package

martinklepsch 2016-01-28T14:12:42.000201Z

I found that but I'm on mac and I think the fix has already been released as well?

2016-01-28T14:12:42.000202Z

I think it has to do with Windows using different brackets

2016-01-28T14:13:26.000203Z

Oh, if you're on Mac I have no idea.

martinklepsch 2016-01-28T14:22:21.000204Z

found it. I had lein installed via Nix which required special modification of $PATH and I guess node doesn't pick this up properly (not sure about that) — in any case specifying the path the the lein executable manually worked

geksilla 2016-01-28T16:30:50.000205Z

@martinklepsch did you launch atom from terminal?

martinklepsch 2016-01-28T16:30:58.000206Z

@geksilla: nope

geksilla 2016-01-28T16:31:18.000207Z

to be sure that PATH is correct you need to launch atom from terminal

geksilla 2016-01-28T16:32:40.000208Z

https://github.com/atom/atom/issues/3018

2016-01-28T16:51:52.000210Z

@dvcrn: Oh yeah, I fixed the links in the README.