In reply to @mfussenegger:matrix.org
I've no idea how I'd expect that to behave. I don't mind closing it as working as intended

You can do this:

local f = vim.lsp.buf.hover
vim.lsp.buf.hover = function(config)
  config = config or {}
  config.border = 'rounded'
  return f(config)
end

Hi all, quick question - if I wanted to profile the performance of Neovim busted unittests, is there a preferred method? My criteria of "good profiler to choose from is"

• Ability to nest profilers (e.g. a "describe-with-a-describe" would have its own dedicated profiler")
• Flamegraph output

I haven't found any profiler that does this flamegraph out-of-box. But what about nesting? The built-in Vim profiler doesn't appear to be nestable. I hear LuaJIT 2.1+ has a built-in profiler. If I use that will it still capture Vimscript functions that are called via Lua properly? If anyone knows about the most comprehensive, nestable profilers for Neovim lua I'd appreciate your advice. Thank you!

In reply to @realchairforce:matrix.org
haha even with the "WARNING: this is a gigantic hack" banner at the top?