lspsaga float window / popup rendered

[rodhash]

Is it expected to render the floating like this?

This is a nofile buftype, I tried the following snippet but apparently no effect:

        overrides = {
          -- Overrides for different buftypes, see :h 'buftype'
          buftype = {
            nofile = { enabled = false },
          },
        },

Thanks

[MeanderingProgrammer]

This plugin does render floating windows by default if they are markdown files, like LSP hover docs. The config you have is the way to disable this behavior.

From your screenshot nothing in that floating window looks rendered by this plugin. I imagine if you disable this plugin / remove it from your config entirely, the floating window will continue to look the same. If that's not the case LMK and I can take a closer look.

[MeanderingProgrammer]

Well I found out what's going on but don't have a solution.

This plugin attaches to buffers when the FileType event is triggered.

lspsaga just so happens to set the filetype as markdown before setting the buftype as nofile: https://github.com/nvimdev/lspsaga.nvim/blob/main/lua/lspsaga/hover.lua#L130-L135. I'm not sure if this will always happen as the iteration order of tables is not guaranteed, but in practice the iteration order seems to match the order things are defined.

So when this plugin runs on the lspsaga buffer the filetype is markdown and the buftype is still set to the empty string, as if it were a normal buffer. As a result this plugin does end up running on the lspsaga buffers.

I'm not sure what property I can rely on that will be set at the time this plugin runs.

[rodhash]

lspsaga just so happens to set the filetype as markdown before setting the buftype as nofile: https://github.com/nvimdev/lspsaga.nvim/blob/main/lua/lspsaga/hover.lua#L130-L135. I'm not sure if this will always happen as the iteration order of tables is guaranteed, but in practice the iteration order seems to match the order things are defined.

Yeah I noticed sometimes the lspsaga buffer was not highlighted, it feels too happen very randomly

[MeanderingProgrammer]

Figured out a way to make the behavior consistent. Added the ability to set overrides based on the buflisted property: 873bdee.

Update the plugin then add the following to your config:

require('render-markdown').setup({
    overrides = {
        buflisted = { [false] = { enabled = false } },
    },
})

Since buflisted is guaranteed to be set before the filetype this will consistently disable the plugin for the lspsaga buffers.

[rodhash]

Awesome! Seems to be working great!

[rodhash]

Thanks a lot for the quick response / update! Tested already for quite a few times and it's working perfectly.