Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

nvchad does not reload correclty #70

Open
drishal opened this issue Nov 7, 2024 · 5 comments
Open

nvchad does not reload correclty #70

drishal opened this issue Nov 7, 2024 · 5 comments

Comments

@drishal
Copy link

drishal commented Nov 7, 2024

so I am having a small issue where the changes are not actually being applied in the nvchad after a home manager switch. For example
if my chadrc is this

local M = {}

M.base46 = {
	theme = "everforest"
}

return M

the theme still remains as onedark, but if I remove a t from everforest and readd it to force a write manually in ~/.config/nvim/lua/chadrc.lua then it actually loads the everforest theme

hm config:

    programs.nvchad = {
      enable = true;
      chadrcConfig= ''
      ${builtins.readFile ../../config/nvim/nvchad/chadrc.lua}
      '';
      hm-activation = true;
      backup = false;
    };

chardrc:

---@type ChadrcConfig
local M = {}

M.base46 = {
	theme = "everforest",
}

return M
@Bot-wxt1221
Copy link
Member

I don't use chadrc. It was simply placed to ~/.config/nvim/lua. Is that right?

@drishal
Copy link
Author

drishal commented Nov 8, 2024

I don't use chadrc. It was simply placed to ~/.config/nvim/lua. Is that right?

yes correct

@Bot-wxt1221
Copy link
Member

Bot-wxt1221 commented Nov 8, 2024

Then I don't know why it doesn't work. You may want to ask upstream.

@drishal
Copy link
Author

drishal commented Nov 8, 2024

Then I don't know why it doesn't work. You may want to ask upstream.

I feel like nvchad might need a force reload ? 🤔
I think it's not able to read the change unless and until I manually open the actual file in .config/nvim/lua and trigger a save

@MOIS3Y
Copy link
Contributor

MOIS3Y commented Dec 17, 2024

@drishal for the latest versions of nvchad, the guys from upstream have made quite a lot of changes.
You can try removing everything related to nvchad from

~/.local/share/nvim 
~/.local/state/nvim ~/.cache/nvim/

Please restart nvim

If it doesn't help, check

~/.config/nvim/lazy-lock.json

Maybe it refers to an old version of nvchad and it’s worth updating it.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants