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

[BUG] Some NVChad Plugins for neovim does not work if config is in ~/dotfiles/.config/nvim #749

Closed
1 task done
mrjxtr opened this issue Feb 21, 2025 · 1 comment
Closed
1 task done
Assignees
Labels
bug Something isn't working to be confirmed Issue is currently under review and has not been released

Comments

@mrjxtr
Copy link
Contributor

mrjxtr commented Feb 21, 2025

Describe the bug

Some NVChad Plugins for Neovim do not work if config is in ~/dotfiles/.config/nvim.

I add mkdir ~/.config/bro, add my Nvim/NVChad config there and use NVIM_APPNAME="bro" feature to run Neovim from that directory, everything works. but not if I run it in ~/dotfiles/.config/nvim

I understand that this is a "Symbolic Link" to ~/.config/nvim made during the ml4w install...

so my question is this...

  1. Could there be an issue on how the symlink was made that is causing this bug?
  2. Can I safely delete the symlink and just use the ~/.config/nvim without the symlink? Will this cause more issues in the ML4W ecosystem?

Steps to reproduce

  1. Delete the nvim config file from ~/dotfiles/.config/nvim
  2. Clone my nvim/nvchad config git clone https://github.com/mrjxtr/nvim in ~/dotfiles/.config/
  3. Open nvim.
  4. After all the lazy plugins finish install, close nvim and reopen

Expected behavior

When opening Nvim, the NVDash page should be showing, but it does not show even after load_on_startup = true

M.nvdash = {
    load_on_startup = true,
}

Screenshots

Expected behavior

Image

Distribution

Arch Linux

If Other, specify

No response

Additional context

No response

Code of Conduct

  • I agree to follow this project's Code of Conduct
@mrjxtr mrjxtr added the bug Something isn't working label Feb 21, 2025
@mylinuxforwork mylinuxforwork added the to be confirmed Issue is currently under review and has not been released label Feb 22, 2025
@mrjxtr
Copy link
Contributor Author

mrjxtr commented Feb 23, 2025

[UPDATE] There is nothing wrong with the symlink. You just need to be in the latest nvcahd UI plution "3.0" and open directories using the "nvim" command. Should also work with using an alias.

@mrjxtr mrjxtr closed this as completed Feb 23, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working to be confirmed Issue is currently under review and has not been released
Projects
None yet
Development

No branches or pull requests

2 participants