[Config] text.done seems to trim the icon

[lopi-py]

fidget is trimming the right side of the icon, seems to only render the first character of text.done

Config

require("fidget").setup({
    text = {
        spinner = "arc",
        done = require("icons").check,
    },
})

icons.lua

[j-hui]

I'm unable to reproduce this problem using ASCII text. I see all characters rendered using done = "DONE":

I suspect that this is either an issue with Unicode, or with your font/terminal (I've encountered similar issues in the past where icons appear cut off). Can you paste the icon in this issue? What font/terminal emulator are you using?

[lopi-py]

Can you paste the icon in this issue? What font/terminal emulator are you using?

• Icon: " "
• Font: MesloLGS NF(nerd font)
• Terminal: Windows Terminal(cmd.exe profile)

[lopi-py]

it works with letters, but if I put an icon, just takes the first character

[j-hui]

I'm unable to reproduce this error (on Alacritty running on NixOS with a completely different font):

I'm sorry but I'm not sure I can be of much help here.

That being said, there's definitely something fishy happening with that icon. I don't seem to be able to render it properly in my config:

Sorry this isn't ideal. Hopefully someone else will pick this up.. in the meantime, does the original check mark icon work for you?

[lopi-py]

Yes, the original check mark works

[lopi-py]

#23 fixed this but only if window.blend is set to 0

[j-hui]

That's really odd. There's something very fishy going on with how background highlights are working; disabling winblend seems to be a workaround but I'll have to investigate more.

[lopi-py]

Maybe could be a neovim problem, but I'm not sure

[Iskustvo]

Hi @lopi-py,

I'm pretty sure that the issue you described has nothing to do with this plugin, nor Neovim in general.
It's most likely issue with font or the terminal which you are using.
I have the same issue and so far I was avoiding it by adding one space after each icon, but when you need to interactively go over it (like in trouble.nvim) this really falls apart quickly 😄

Don't know which terminal you are using, but I'm on st and I can tell you that it doesn't work for me, while alacritty does.
Luckily, I found opened PR regarding the patch which claims to fix it, so we might get it truly fixed for st as well.