Fancy Diagnostic Signs not working when viewing kickstart's init.lua

[b4shful]

Before Reporting an Issue

• I have read the kickstart.nvim README.md.

• I have read the appropriate plugin's documentation.

• I have searched that this issue has not been reported before.

• [CHECK] By checking this, I confirm that the above steps are completed. I understand leaving this unchecked will result in this report being closed immediately.

Describe the bug

Sorry for not much info I am tight on time rn.

Tagging @gelocraft as original author

In #1335 diagnostic signs were added to init.lua (there was an older version commented out in there, but this PR removed that one and added a new version which was not commented).

I was trying this patch out and noticed that strangely, these new diagnostic signs appear everywhere for me EXCEPT for my kickstart init.lua file.

[To be clear, diagnostic signs are working, but #1335 changes them from their default letters like E, W, I and H to proper symbols for each. This change works everywhere else I've tried, but in the kickstart init.lua file it only displays the letters and not the symbols]

To Reproduce

1. Make sure you have a nerd font enabled and selected in your terminal!
2. Create a new lua file somewhere, e.g "test.lua"
3. Add an error e.g type prin("Hello World") instead of print("Hello World")
4. Observe the new error signs (instead of letters) [thus we confirm the feature usually works]
5. Open kickstart's init.lua file
6. Create an error in the file
7. Observe the default letter sign (red "E") instead of new error sign symbols [therefore the feature isn't working for init.lua]

Desktop

• OS: Arch Linux
• Terminal: Foot

Neovim Version

v0.10.4

[b4shful]

@gelocraft From the screenshots #1335 it looks like you might be using a different config folder structure, but could you by any chance temporarily switch from that to the standard one and see if you can reproduce this?

[gelocraft]

hi have u set your vim.g.have_nerd_font = true ? because the diagnostic sign icons would only work if the value of vim.g.have_nerd_font is set to true

[gelocraft]

@b4shful u can find it by searching /vim.g.have_nerd_font in your init.lua and set that to true if the default value is false

[b4shful]

Yes, it's set to true.

But also, I stated in this issue that the new signs are showing completely fine in every file EXCEPT for init.lua, so therefore my vim.g.have_nerd_font has to be =true otherwise I wouldn't see the new diagnostic signs at all.

[gelocraft]

Yes, it's set to true.

But also, I stated in this issue that the new signs are showing completely fine in every file EXCEPT for init.lua, so therefore my vim.g.have_nerd_font has to be =true otherwise I wouldn't see the new diagnostic signs at all.

Maybe your Lsp stops working for some reason when opening kickstart.nvim's init.lua file? can u show or attach your lsp.log file here?

[gelocraft]

In case u don't know where the lsp.log file is located, you can find its dirname by running :lua print(vim.fn.stdpath("state"))

[gelocraft]

I tried reproducing this issue and got this lsp log from luals when opening kickstart's init.lua

[START][2025-02-27 23:08:10] LSP logging initiated
[ERROR][2025-02-27 23:08:10] ...lsp/handlers.lua:562    "Your workspace is set to `/home/gelocraft`. Lua language server refused to load this directory. Please check your configuration.[learn more here](https://luals.github.io/wiki/faq#why-is-the-server-scanning-the-wrong-folder)"
[START][2025-02-27 23:11:16] LSP logging initiated
[ERROR][2025-02-27 23:11:16] ...lsp/handlers.lua:562    "Your workspace is set to `/home/gelocraft`. Lua language server refused to load this directory. Please check your configuration.[learn more here](https://luals.github.io/wiki/faq#why-is-the-server-scanning-the-wrong-folder)"

@b4shful I think the problem you are facing is not related to diagnostic config but from Lsp?

[gelocraft]

i don't know why luals is crashing when opening kickstart's init.lua.

[b4shful]

I tried reproducing this issue and got this lsp log from luals when opening kickstart's init.lua

[START][2025-02-27 23:08:10] LSP logging initiated
[ERROR][2025-02-27 23:08:10] ...lsp/handlers.lua:562    "Your workspace is set to `/home/gelocraft`. Lua language server refused to load this directory. Please check your configuration.[learn more here](https://luals.github.io/wiki/faq#why-is-the-server-scanning-the-wrong-folder)"
[START][2025-02-27 23:11:16] LSP logging initiated
[ERROR][2025-02-27 23:11:16] ...lsp/handlers.lua:562    "Your workspace is set to `/home/gelocraft`. Lua language server refused to load this directory. Please check your configuration.[learn more here](https://luals.github.io/wiki/faq#why-is-the-server-scanning-the-wrong-folder)"

@b4shful I think the problem you are facing is not related to diagnostic config but from Lsp?

No, this error is not what I am talking about.

However, I can say that the one you've shown occurs because the Lua language server refuses to start from the user's home directory. It's the LSP being clever by assuming something like "no one is intentionally creating a Lua project directly in their home directory, so we should error if this happens". The LSP is starting with Neovim's working directory, which in your case is probably set to your home directory (you probably didn't expect this - see my explanation below for why).

Your Neovim instance's working directory doesn't necessarily align with the file you're opening. Neovim gets the current working directory from your shell. In other words, by default (unless you have configured it to automatically set the working directory, or are using a project management plugin) it will open in the directory you called nvim from.

If you cd to the neovim config directory before running nvim init.lua you will find that the error you have seen goes away.

[gelocraft]

If you cd to the neovim config directory before running nvim init.lua you will find that the error you have seen goes away.

I've actually tried doing this but still get the same error from kickstart.nvim's init.lua.

I'm using NVIM_APPNAME=kickstart.nvim to start kickstart.nvim because I have my own configuration.

My local kickstart.nvim is located into ~/.config/kickstart.nvim and my main neovim config is located in ~/.config/nvim

[gelocraft]

No, this error is not what I am talking about.

I think your problem with diagnostics is still related to Lsp because when the Lsp crashes the diagnostics signs won't show anymore. And I think your Lsp is crashing that's why I'm asking you to attach your lsp log message here :)

[b4shful]

My LSP is not crashing.

when the Lsp crashes the diagnostics signs won't show anymore

The diagnostic signs are showing but only the default ones (letters instead of symbols). Apologies if this was unclear in my original issue, although I did mention this in the reproduction steps:

For any other file I said:
"4. Observe the new error signs (instead of letters) [thus we confirm the feature usually works]"
For the init.lua file I said:
"7. Observe the default letter sign (red "E") instead of new error sign symbols [therefore the feature isn't working for init.lua]"

I will edit my issue to emphasise this part.

[gelocraft]

The diagnostic signs are showing but only the default ones (letters instead of symbols). Apologies if this was unclear in my original issue

Re: Set the value of vim.g.have_nerd_font to true to show the nerd font signs and not the default

[gelocraft]

@b4shful may i know how do u use kickstart.nvim? are u cloning the main repo into ~/.config/nvim or just copying the init.lua file from the main repo?

[b4shful]

I clone the repo into ~/.config/nvim.