Fork me on GitHub
#parinfer
<
2016-03-06
>
sekao16:03:21

if anyone’s interested in trying parinfer in nightcode, i built and uploaded a snapshot: https://github.com/oakes/Nightcode/releases/tag/1.1.0-SNAPSHOT

sekao16:03:25

i wrote a new indent system from scratch that uses tools.reader to figure out the proper indent. maybe overkill but it seems ok so far

sekao16:03:53

i updated paren-soup as well, and it’s using the same indentation and undo/redo code as nightcode, so it’s an easy way to try the behaviors out: http://oakes.github.io/paren-soup/

sekao16:03:03

only downside to this change is that nightcode is like 12MB larger 😃 not sure why, maybe it’s the kotlin dependency. it’s worth it though

dominicm16:03:13

That's pretty neat.

dominicm16:03:22

I like the paren soup.

dominicm16:03:37

Be interesting to try that in vim running async or something.

solicode16:03:26

The size increase is surprising though. I thought Kotlin’s runtime + standard lib came out to be less than 1 MB

solicode16:03:35

Must be some other dependency?

escherize16:03:41

Hey guys, wanted to mention that we added a feature to cljsfiddle. http://cljsfiddle.com/#gist=6a609b6af5430a4be97d

escherize16:03:58

I'd like to add parinfer next - it's wonderful stuff

shaunlebron18:03:41

@sekao: just tried out the new nightcode and paren-soup versions

shaunlebron18:03:15

works well! surprised that you were able to share code between them

shaunlebron18:03:59

I was looking at doing this for the parinfer demo site with firebase

shaunlebron18:03:42

I’m guessing you do some Gist API calls on the backend to save snippets?

shaunlebron18:03:07

was hoping to use firebase to skirt the backend requirement

shaunlebron19:03:44

nevermind, just looked at cljsfiddle.gist. i’ll just do that then!

sekao19:03:12

@shaunlebron: yeah i was surprised too…i wrote it all in paren-soup first, then broke the code out into their own libraries and made them cljc files. one of my first experiences with clj/cljs code reuse, it was pretty cool

shaunlebron19:03:03

that’s cool, tag-soup and mwm, just perused them a bit

dominicm20:03:46

@escherize: Interesting that you went gitlab, was pretty confused I couldn't find it on github. I'm really interested to watch how gitlab shapes the github empire.

cfleming21:03:27

@dominicm: @escherize: I’ve considered moving the Cursive issues to Gitlab because their issue handling is a lot better and their dev process is more open, but I’m worried about this discoverability issue so I shelved the idea for the moment.