Fork me on GitHub
#proton
<
2016-01-28
>
austincrft03:01:58

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

dvcrn06:01:59

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

martinklepsch09:01:29

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

martinklepsch09:01:46

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

dvcrn10:01:07

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

dvcrn10:01:13

do you mean that?

martinklepsch10:01:18

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

martinklepsch10:01:41

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

martinklepsch10:01:05

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

martinklepsch14:01:10

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

martinklepsch14:01:21

looks familiar to anyone maybe? simple_smile

martinklepsch14:01:38

the directory it's starting in seems fine

austincrft14:01:08

That's an error in the proto-repl package

martinklepsch14:01:42

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

austincrft14:01:42

I think it has to do with Windows using different brackets

austincrft14:01:26

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

martinklepsch14:01:21

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

geksilla16:01:50

@martinklepsch did you launch atom from terminal?

geksilla16:01:18

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

austincrft16:01:52

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