buffer appearing in terminal about ui HOT 13 CLOSED

@KELs7 thanks for your effort! wait, for a day or two i'll try to do this without winfixbuf

from ui.

M.term = {
  winopts = { winfixbuf = true },
}

seems like winfixbuf is the only way @KELs7 , just add the above code in your chadrc!

Thanks! But you forgot to add that you have to remove the dev property from { "NvChad/ui", dev = true } in ~/.config/nvim/init.lua . It was producing errors

from ui.

obviously @KELs7 , that change was temporary and only for testing!

from ui.

This is not a problem with NvChad. It's a Neovim issue. Take a look at stickybuff

from ui.

This is not a problem with NvChad. It's a Neovim issue. Take a look at stickybuff

It seems this was fixed in Neovim itself. See here. Not sure how to take advantage of the fix.

from ui.

This is not a problem with NvChad. It's a Neovim issue. Take a look at stickybuff

Oh ok thanks

from ui.

I am guessing

vim.bo[opts.buf].winfixbuf = true

somewhere in M.display can fix it.
Can someone test for me? I don't know how to work with nvchad locally. term plugin is a binary in base64 folder.

from ui.

@KELs7 to make changes locally you can do this

and in your plugins table

{  "NvChad/ui", dev = true }

git clone https://github.com/NvChad/ui/ ~/projects/ui

from ui.

@siduck thank you for the direction

from ui.

Using vim.wo[win].winfixbuf = true fixes it.
placed it below this line

from ui.

Probably there should be a way to avoid showing that error message and also having to press continue

from ui.

That error is coming from tabufline/module on this line

from ui.

M.term = {
  winopts = { winfixbuf = true },
}

seems like winfixbuf is the only way @KELs7 , just add the above code in your chadrc!

from ui.