Fork me on GitHub
#parinfer
<
2017-07-31
>
henrik04:07:12

Trying out smart mode in Atom, and it’s looking good!

chrisoakman04:07:25

It's not completely done yet 😉

chrisoakman04:07:32

Shaun and I are both working on it right now.

henrik04:07:41

@chrisoakman I completely understand that 🙂

henrik04:07:28

I thought I’d try it out anyway

chrisoakman04:07:19

Nice to see early adopters! I know people are wanting to test it out.

henrik04:07:39

Yeah, I thought I might catch you a few bugs maybe. But perhaps it’s a bit too early, give us a shout when you want beta testers. 🙂

chrisoakman04:07:05

Will do :thumbsup:

chrisoakman04:07:28

I think Shaun is jumping into help because he wants to see it "out in the field" sooner than later.

chrisoakman04:07:06

I should have more time now. I was teaching a coding bootcamp class that just ended.

chrisoakman04:07:34

I'm also traveling for work this week, so would like to at least get something working before that trip.

chrisoakman05:07:38

@henrik If you want to be on the super-bleeding edge, give this a try: https://github.com/oakmac/atom-parinfer/pull/80

henrik05:07:20

Yep, the above problem is certainly gone.

shaunlebron05:07:04

thanks for trying it @henrik!

henrik05:07:25

No problem, thanks for all the hard work'

shaunlebron05:07:27

getting close, I really want tabStops in there, will get to it in the morning

shaunlebron05:07:38

tab stops are so helpful

henrik05:07:28

Yeah, I was just thinking about that one, since I saw you demoing it earlier. But overall, I’d say it works really well already. I’ll keep using it for now and see if I run into any more oddities.

shaunlebron06:07:10

thanks, looking forward to feedback

henrik10:07:10

I’ve been using it for a while now, and so far, no surprises.

henrik13:07:13

It’s not precisely the same situation though. In my case, it’s better that they stay on the same line. For example, I don’t want

[{:hello "world"}]
to turn into
[{:hello "world" ;; Comment :-)
}]
Rather,
[{:hello "world"}] ;; Comment :-)
… is the result I desire in this case.

shaunlebron14:07:02

@henrik thanks, i see that from time to time and I’m always taken aback by it

shaunlebron14:07:49

another good use case for smart mode to inspect the change and react accordingly

henrik14:07:11

To be honest, the most common use case for me would be that I’m clumsy 🙂

henrik14:07:39

I hit the semicolon when I try to hit colon, and accidentally comment out x number of brackets

henrik14:07:31

Other than that, a whole day of programming with v3 and I have nothing to complain about. It’s a great improvement over the last version.

shaunlebron14:07:49

come to think of it, I think they were also accidents when it happened to me

shaunlebron14:07:21

as long as it’s not destructive, it’s not too pressing, but a good thing for polish to reduce the surprise there

henrik14:07:41

Yeah, it’s not that hard to position the cursor at the end of the line when you DO want to make a comment.

shaunlebron14:07:44

good to hear!

henrik14:07:06

My general experience of using parinfer is that I get the feeling of my editor doing what I intend for it to do, rather than what I (in strict terms) tell it to do. In that sense it fits the general feeling of the project to mitigate the effects of the accidental commenting

shaunlebron14:07:59

at the beginning of the project, my intuition was that there was not enough information to understand user intention, so I leaned on modes for explicit intention—which part of the indentation-paren invariant do you want to control?

shaunlebron14:07:29

i’m much more optimistic now that user intention can be inferred from changes (mostly?)

shaunlebron14:07:23

thanks for sharing your thoughts on how parinfer relates to user intention, I’ll be keeping that in mind

shaunlebron14:07:34

smart mode made me a believer that user intention is encoded somewhere, just needs a creative person to wrangle it out

shaunlebron14:07:08

i.e. parinfer’s users