Example in README.md: Lightline.vim could not load colorscheme gruvbox. (While running without `sudo`) about nixvim

[MattSturgeon]

@GaetanLepage is our gruvbox maintainer while our lightline module has been largely untouched since it was added 4 years ago.

The plugins.lightline.colorscheme option currently defaults to colorscheme:

nixvim/plugins/statuslines/lightline.nix

Lines 19 to 24 in e48ce78

	colorscheme = mkOption {
	type = with types; nullOr str;
	default = config.colorscheme;
	description = "The colorscheme to use for lightline. Defaults to .colorscheme.";
	example = "gruvbox";
	};

However I'm not 100% sure if the gruvbox module sets the colorscheme option 🤔

maybe this issue is ready for close?

Regardless of how well lightline and gruvbox integrate, if the example in the README is broken this is still a valid issue.

[jirafey]

#1575

[MattSturgeon]

I see gruvbox when using nvim without sudo but I don't when using it with sudo

Also in repositories I have access to, the gruvbox colorscheme is applying with both sudo and non-sudo nvim command. However the error with lightline still appears on non-sudo nvim command

This is probably related to how home-manager sets up your environment, I'm not 100% sure ottomh. Usually, sodo will inherit your environment though (unless using things like sudo -i)

As for lightline, that's strange. We'll have to investigate as it looks like something is broken either upstream in the plugin or in our modules.

[jirafey]

I see gruvbox when using nvim without sudo but I don't when using it with sudo
Also in repositories I have access to, the gruvbox colorscheme is applying with both sudo and non-sudo nvim command. However the error with lightline still appears on non-sudo nvim command

This is probably related to how home-manager sets up your environment, I'm not 100% sure ottomh. Usually, sodo will inherit your environment though (unless using things like sudo -i)

As for lightline, that's strange. We'll have to investigate as it looks like something is broken either upstream in the plugin or in our modules.

it is rather in my config, i will post the whole thing here soon, i need to fix some issues now.

[jirafey]

@MattSturgeon
https://github.com/jirafey/nixconfig/tree/b3b5cbfc0dd755355c87dfd092c24c6584a700c0

I would look for some issues with the permissions of the user/sudo

This is a very new config and that is probably why it does not work yet. I probably will abandon nixvim but I am willing to help debug this issue.

[MattSturgeon]

I don't see any obvious issues in your config. I suspect this is an issue on our end.

I've not used lightline myself, but my config with lualine seems to be working ok with catppuccin.

[ech0r]

manually adding gruvbox under extraPlugins worked for me:

    programs.nixvim = {
	enable = true;
        defaultEditor = true;
        extraPlugins = with pkgs.vimPlugins; [
        	gruvbox
        ];
	colorschemes.gruvbox.enable = true;
        plugins.lightline.enable = true;
    };

[MattSturgeon]

This seems to be the same issue as this discussion, see my response there: #1575 (reply in thread)

tl;dr, since 871e331 our gruvbox module installs gruvbox-nvim which is different to gruvbox. I wonder if lightline only supports the latter and not the one we normally install?

[jirafey]

This seems to be the same issue as this discussion, see my response there: #1575 (reply in thread)

tl;dr, since 871e331 our gruvbox module installs gruvbox-nvim which is different to gruvbox. I wonder if lightline only supports the latter and not the one we normally install?

hey if there is any help needed from me, let me know, maybe this issue is ready for close?

[MattSturgeon]

if the example in the README is broken this is still a valid issue.

#2078 didn't address the README example, so I'll re-open this.