Clojurians Log v2

vim-fireplace https://github.com/tpope/vim-fireplace/blob/master/doc/fireplace.txt#L234-L238

For Conjure users: https://github.com/walterl/conjure-locstack

Love the alternate name!

But the docs of vim-unimpaired say that [l doesn't do any jumps and instead it decodes or encodes as a list: https://github.com/tpope/vim-unimpaired I think you have some other plugin that gives you this mapping. I'd also like to not view the stack trace in the popup window but to jump to the deepest node. Do you think it's a good idea?

n ]l <Plug>(unimpaired-lnext) 🤷‍♂️

> "Do you think it's a good idea?" Not sure how useful that'll be, since in most cases it will be your process or REPL entry point. I've rarely had to look past the top (first) few frame in a stack trace.

> I've rarely had to look past the top (first) few I was thinking about being able to jump to the deepest stack trace line -- i.e. the one that actually threw.

That's the first/top frame. ]l/`:lnext` gets me there, although it's often somewhere in unlocatable (Java) code. Maybe LocStack should focus the location list when it pops up, like vim.diagnostic.setloclist() does.

Ah I see how ]l works then. But then I still need to calculate the location list. Ok. I thought if it could jump to the first location automatically and then showing no popup 🤔 But I don't know if this can work.

It probably could, but I tend to avoid automatic and "unexpected" jumps like that. Especially for an operation that takes this long. Maybe it can be added as an option.

Oh right. In my older conjure clj-test jump plugin it also was taking time to do it. What would be more magic is that the jumps would be added. Then it would be hard to understand where they come from.

Don't you think the location list is a better fit for this purpose, than the jump list?

I don't know. I'm new to :lnext concept. I'll try to use it and then I'll be able to comment here. But yes, I remember I'm constantly frustrated by "hm, how could I jump to the next stack frame line without needing to find the stack trace and figure out stuff"

Nice. I can see the stack trace at the bottom but also move around by pressing 5]l. And I don't need to focus the stack trace anymore. That's pretty good.

Yeah, the loclist (and quickfix list) is pretty useful.

Do you use vim-unimpaired with quicklist? How?

]q and [q

I don't understand what ]q does. It jumps to a random location in a different file somehow. [b is useful when you open some random buffer but you want to have what you had before.

See :copen and :help quickfix

The quickfix is awesome when doing refactoring. Makes it really easy to step through a bunch of locations, and will even adjust the target location when adding/removing lines in a file

:LocStack is now >10x faster. It can also now load stack traces from registers (`:LocStackReg`), meaning you can yank and load stack traces from logs.

What I like about this plugin is that I don't need to save the current file to jump. I'll have to investigate that because I have my own plugin that suffers from this. Thanks.

That's very cool! thanks for the link @clojurians-slack100

Not the link, the plugin 😄

> "What I like about this plugin is that I don't need to save the current file to jump." This may be an accidental side effect of LocStack trying a bit harder to find a location when the stacktrace nREPL op doesn't return one. It looks up the file for the ns.

No, I think this is a side-effect of that separate buffer and how it implements the jump. I looked at your code and you don't do the jump command yourself, you just give the lines to another buffer. When I try to jump to a different file using my own plugin then it complains that the current file isn't saved. Probably this is a config option.

Oh, the jumping is done by vim's built-in location list. vim-unimpaired then makes navigation between those entries as easy as [l and ]l vim