Fork me on GitHub
#vim
<
2019-05-04
>
Olical15:05:20

@dharrigan I think you're the same David I was pairing with at the Clojure Bridge training the other night :thinking_face: (possibly mistaken) happy to give you a tour of Conjure next week!

dharrigan15:05:05

I am the same 🙂

dharrigan15:05:28

Sure, look forward to it. See you soon!

Olical16:05:18

Kinda small announcement I guess, Conjure v0.12.0 has pretty errors with folded stack traces https://github.com/Olical/conjure/releases/tag/v0.12.0 And I basically have a v0.13.0 already that includes self prepling. So if you try to eval without any prepls connected Conjure will connect to it's own JVM and eval there for you as an interim solution. Not recommended for long term dev but great for just trying something out! You can give it a go with the latest commit https://github.com/Olical/conjure/commit/cc3bfa5777c2650d58100fefca82457c287b43d0

❤️ 8
dominicm16:05:01

Where do you put the stacks in vim?

Olical16:05:37

I take the Throwable->map (or Error->map in CLJS) output, zprint it and then fold it in the buffer.

Olical16:05:46

Using foldlevel 0 and fold markers

Olical16:05:00

So you can just expand the folds as and when you need them.

Olical16:05:10

And still / search across their content which might be handy.

dominicm16:05:08

Oh, there's like an output buffer or something?

Olical16:05:22

Yep! I keep a big ol log buffer that trims itself when it gets too long.

Olical16:05:54

Considering maybe adding other ways to see eval output but I like this big unified buffer right now. Having history and context has come in REALLY handy at work. I can go and see old evals, search things etc.

Olical16:05:40

The README / docs etc will be something I tidy up at v1.0.0, didn't want to keep making the docs outdated as I developed it 😬

dominicm16:05:50

I really like my quickfix for stacks

dominicm16:05:00

Being able to navigate through call sites is useful.

Olical16:05:33

Yeah, that could probably be added since I have the stack data. Not something I've used personally very much but I can see the value.

dominicm16:05:12

It was quite unanticipated how useful it became

Olical16:05:13

To me that's not what it's for but maybe as an optional thing. Quick fix should be one error per line, like limiting or compile errors. IMO, anyway. But this is a matter of taste really.

Olical16:05:34

I think I'm just used to it as a lint thing

Olical16:05:56

When fireplace used quick fix it really annoyed me because my other limiting plugins would wipe it and there was no way to see the stack

Olical16:05:12

Hence my approach of "preserve EVERYTHING". Nothing is lost or hidden, I hope.

Olical16:05:31

Linting plugins *