Fork me on GitHub
#vim
<
2017-11-18
>
dominicm16:11:50

My local replant, with a fork of cider-nrepl (will upstream soon™) now supports stacktraces where you can jump to source. This is really useful, and is one level above those found in fireplace. Combined with vim-unimpaired, you can jump through a stack with [l and ]l which is pretty powerful imo.

dominicm16:11:00

There's probably quite a few hours of work left in making this good enough for general use, but once I have it, I'll start working on a custom eval for replant so that you can have this in response to evaluation errors.

dominicm17:11:02

Combined with vim-qf you can do :Keep aero and get only the aero frames.

dominicm17:11:08

I'm really excited about this

dominicm17:11:14

A few gotchas: The jar paths are really long, and there's very little I can do (I think I can knock off the /home/dominic part at best).

dominicm17:11:54

Oh, actually... I could define a conceal which would hide a lot of cruft... brb

juhoteperi18:11:00

@dominicm very nice!, what about aligning line numbers etc.?

jebberjeb19:11:36

RE: yesterday's discussion, embloginated https://medium.com/@jebberjeb/vim-clojure-tooling-redux-16ce62e4d727. Nothing too novel here, just really like the idea of how far you can get with :terminal in Neovim.

dominicm19:11:42

@juhoteperi not sure how I'd align it. I wonder how spaces in the filename are treated. I suspect it will open the file with spaces in. I'm only using the location list built into vim

dominicm19:11:11

Apparently you can modify a quickfix buffer, and it will remember what goes where. A shame that behaviour isn't exposed somehow

dominicm20:11:17

@jebberjeb that's really interesting to me.

dominicm22:11:40

hmm, this stacktrace stuff works with cljs, but doesn't contain much in terms of references. Not sure if it's always been like that or not though.