I broke the auto theming in neovim by re-installing lazy. How can I restore that without doing a fresh install of Omarchy?

[SamRoehrich]

Pretty much the title
With a fresh LazyVim install how can I get the neovim theme sync without re-installing everything?

[dotsilva]

Hello, can you paste here the output of

ls ~/.config/nvim/lua/plugins/

I am verifying if in your folder there is a symlink to the file where the themes live, when you follow the steps to install lazyvim typically you do a backup (cause it an actual step), your symlink will be there, so i think to fix it you just can restore the symlink. Even if there is not a backup, you can create another symlink.

[dotsilva]

You're welcome. If you're talking about the theme changing automatically without you needing to reopen neovim, it actually working, but only happens if you're not in the start screen of neovim.

[SamRoehrich]

The autoswitching does not work right now but that symlink command helps a lot, thank you.

[dotsilva]

It works if after I change the theme I run that command. In all other scenarios the theme does not update.

this is the state of my nvim.bak so it looks right, but when I update the theme and restart nvim I see my old theme until I rerun the symlink command.

wait, if you mean you always need to type the cp command to the theme change, its not working at all, i think you need to recreate it. I search about it.

[dotsilva]

I understood, the symlink is attached to a folder when created, we need to create another one:

ln -sf ~/.config/omarchy/current/theme/neovim.lua ~/.config/nvim/lua/plugins/theme.lua

Let me know if its working know, i got this syntax on stack overflow.

[SamRoehrich]

That did it!!!! Thank you @dotsilva

[malik-na]

@dotsilva I need to make a similar symlink for walker, could you help?

[dotsilva]

@dotsilva I need to make a similar symlink for walker, could you help?

Hi, regard the symlink: ln -sf > this creates a symlink while overwriting an existent one if there is one already, its not necessary i think (the f part, the -s is necessary), but i used it to prevent any problem with the other symlink in the other folder (just my own speculation)

the first path is the file/directory targeted by the symlink

the second path is the place where the symlink will be

hope this helps you, but if you need more help and it its in the scope of what i know or what i can discover i would gladly help o/