Anyone has some good function to format e.g. log-output as json-string or edn-string to pretty-formatted? I found something with jet at some point but somehow lost it again

Is anyone aware of some way to have function definitions open in a predefined window? The long story: I find that I'm often carefully studying one specific function f, and want to study definitions of functions called by f. What I currently do is :vsplit<CR>gd, but this has a lot of window management/navigation overhead. What I'd like to have is, while staying in f's window, some command/mapping I can trigger to jump to a definition in a predefined window. Kind of like vim-fireplace's :Source, but with a specified (normal) window as a target.

@clojurians-slack100 not really addressing your main issue here, but a small improvement is using :vert gd - vert splits then runs your command in the new split, there's also tab for doing the same thing but in a new tab instead of a split

there's also lefta etc. for opening the split in a specific relative direction

TIL lefta et al 🎉

@clojurians-slack100 you might be able to use "the preview window" for what you want - I haven't used this feature in anger

:pedit sets the contents of this special window

if your source lookup uses the tag system, then :ptag has the kind of behavior you describe

using a dedicated window (the preview window) and replacing the last thing you looked up

Hmmm. Possibly. But this is where a caveat comes in: I often need to go another level deeper, or edit, or otherwise navigate around from the definition I jumped to. Preview windows often don't work great for that level of interactivity. (That's why I mentioned "(normal) window" 😛)

it has a stack you can pop

hmm...

@clojurians-slack100 when I used :pedit it's a normal buffer display window, it's just special in that the next :pedit always replaces contents of that window

it's not a "preview" like "just read it, vim commands don't work"

Meh. Looks like this is also bumping up against the limits of coc.nvim: it doesn't seem to use/support tags

But thanks for the tips. You've given me some stuff to research 🙂

more things should use / leverage the tag system, so many vim commands work on tags...

Yeah. I use(d) it a lot when writing Python code