8000 bug: Installation does not work on Manjaro with nvim 0.11.0 · Issue #1974 · folke/lazy.nvim · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content

bug: Installation does not work on Manjaro with nvim 0.11.0 #1974

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.

Sign up for GitHub

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

Jump to bottom
Open
4 tasks done
Raymi306 opened this issue Apr 12, 2025 · 3 comments
Open
4 tasks done

bug: Installation does not work on Manjaro with nvim 0.11.0 #1974

Raymi306 opened this issue Apr 12, 2025 · 3 comments
Labels
bug Something isn't working

Comments

@Raymi306
Copy link
Raymi306 commented Apr 12, 2025 •
edited
Loading

Did you check docs and existing issues?

  • I have read all the lazy.nvim docs
  • I have updated the plugin to the latest version before submitting this issue
  • I have searched the existing issues of lazy.nvim
  • I have searched the existing issues of plugins related to this issue

Neovim version (nvim -v)

0.11.0

Operating system/version

Manjaro KDE Plasma
Kernel Version: 6.12.21-4-MANJARO (64-bit)

Describe the bug

Attempting to install Lazy on Manjaro with nvim 0.11 results in an error.

Steps To Reproduce

I tried both the github release tarball and whatever flavor the AUR provides and confirmed both had LuaJIT support and that both were versions 0.11

:checkhealth only shows warnings for missing providers, all other items are green

I removed .config/nvim entirely.

I copied only the two files listed in https://lazy.folke.io/installation in to the correct locations (structured setup).

When starting nvim:

Note that I tried both init.vim lua require and init.lua, the logs that I had hanging around were from the init.vim run but were effectively identical

Error detected while processing /home/andrew/.config/nvim/init.vim:
line    4:
E5108: Error executing lua /home/andrew/.config/nvim/lua/config/lazy.lua:25: module 'lazy' not found:
        no field package.preload['lazy']
        no file './lazy.lua'
        no file '/usr/share/luajit-2.1/lazy.lua'
        no file '/usr/local/share/lua/5.1/lazy.lua'
        no file '/usr/local/share/lua/5.1/lazy/init.lua'
        no file '/usr/share/lua/5.1/lazy.lua'
        no file '/usr/share/lua/5.1/lazy/init.lua'
        no file './lazy.so'
        no file '/usr/local/lib/lua/5.1/lazy.so'
        no file '/usr/lib/lua/5.1/lazy.so'
        no file '/usr/local/lib/lua/5.1/loadall.so'
stack traceback:
        [C]: in function 'require'
        /home/andrew/.config/nvim/lua/config/lazy.lua:25: in main chunk
        [C]: in function 'require'
        [string ":lua"]:1: in main chunk

Expected Behavior

Lazy should work with 0.11.0 on Manjaro
@Raymi306 Raymi306 added the bug Something isn't working label Apr 12, 2025
@dpetka2001
Copy link
Contributor

lazy.nvim was probably not cloned correctly. That's usually a problem with your git version/configuration in your OS.

@Raymi306
Copy link
8DF6 Author
Raymi306 commented Apr 14, 2025 •
edited
Loading

I can clone other repositories without incident, is there something in particular I should investigate?
I'm not familiar with lua, I think additional logging might help.
If this is a git problem, that has nothing to do with the error above, and it seems like that could be caught earlier so a helpful message can be provided.

@Raymi306
Copy link
Author
Raymi306 commented Apr 15, 2025 •
edited
Loading

So.
I printed the variable "lazypath", and I see:
/home/andrew/.local/share/nvim/lazy/lazy.nvim

Notably, if we look at the error message I posted above, this path is not being tried by "require"

*edit:

I checked the run time path and it WAS there, not sure why the error message was weird. Went into the directory where the git repo was and ran git status. Everything was deleted. git reset --hard appears to have fixed my problems, I also removed the directory and let the install script try to clone things again and that succeeded too

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
bug Something isn't working
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@dpetka2001 @Raymi306
0