Fork me on GitHub
#parinfer
<
2018-08-22
>
shaunlebron03:08:30

> pressing backspace at the beginning of the next line should fix it. parinfer exposes tabstop locations for this reason

shaunlebron03:08:11

e.g. in atom, pressing shift-tab will fix it, but backspace can be made to do likewise

shaunlebron03:08:57

> we don’t have access to the metadata about how certain forms should be indented. Which I wonder about what we could do if we pass that to parinfer. I want to resist the pressure to turn parinfer into an auto-formatter

shaunlebron03:08:40

> many cases aren’t ambiguous, and even if it worked conservatively (didn’t do anything weird in ambiguous cases), it would be neat. I’m willing to look at cases if they’re laid out

shaunlebron03:08:09

I suppose you’re right that stickiness may not be that annoying

onetom08:08:26

@pez where is the source code for that version of the extension u uploaded? just want to make my team mates not worried about installing some trojan 😉

pez08:08:28

master from that repo, even.

1
shaunlebron19:08:43

implemented some elastic tabstop functions to see how it works: https://beta.observablehq.com/@shaunlebron/elastic-tabstops

shaunlebron20:08:45

it might be a bit much to expect clojure users to start using tabs in source files

shaunlebron20:08:32

unless inferring tab characters from existing files to provide a guess becomes reasonable

shaunlebron20:08:43

either way, was nice to study this to get a better idea of the space that both tools occupy