config file is completely ignored

[adrian-gierakowski]

Describe the bug

No matter what I put in ~/.config/lazygit/config.yml it does not have any effect.

To Reproduce

Steps to reproduce the behavior:

create ~/.config/lazygit/config.yml with following content:

gui:
  sidePanelWidth: 0.6
  expandFocusedSidePanel: true
  showFileTree: false

run lazygit: the above config does not take effect

Expected behavior

Config should be loaded

Screenshots

If applicable, add screenshots to help explain your problem.

Version info:

• Run lazygit --version and paste the result here

commit=, build date=, build source=nix, version=0.56.0, os=linux, arch=amd64, git version=2.51.2

• Run git --version and paste the result here

git version 2.51.2

Additional context

Add any other context about the problem here.

when I set LG_CONFIG_FILE, config gets loaded correctly:

LG_CONFIG_FILE=~/.config/lazygit/config.yml

I did check that LG_CONFIG_FILE is not set in my shell:

> set -u; echo $LG_CONFIG_FILE
bash: LG_CONFIG_FILE: unbound variable

Not sure if there are any other env vars which could affect loading of config.

I would be grate if some DEBUG logging was added in the code which loads the config to facilitate debugging cases like this.
Also, a flag --printResolevedConfig, which would show final config (as opposed to default which --config prints) would be useful.

Note

Please try updating to the latest version or manually building the latest master to see if the issue still occurs.

[stefanhaller]

You can type 1, e in lazygit to find out what the currently active config file is.

[adrian-gierakowski]

You can type 1, e in lazygit to find out what the currently active config file is.

thanks! it turns out it was loading config from the legacy path (~/.config/jesseduffield/lazygit/config.yml) and ignoring ~/.config/lazygit/config.yml

I'd say it's a bug. It should either load both, issue a warning that one of them is ignored.

[stefanhaller]

I wouldn't call that a bug; it's documented to behave this way. Loading both could be just as confusing if you don't realize there's another config file that contains settings you are not aware of.

I suppose we could start deprecating the old location, print a warning if it used, and then remove support for it after a while.

[adrian-gierakowski]

yeah, I believe warning it the way to go

[ChrisMcD1]

I suppose we could start deprecating the old location, print a warning if it used, and then remove support for it after a while.

Yeah, I've burned myself by not realizing that one of my computers has the old file still, and I just go direct to editing ~/.config/lazygit/config.yml, and not seen it applied!

[stefanhaller]

This was never a problem for me because I just don't care where lazygit stores its config file. I never try to remember its path.

I think we should address this by advertising more that the way to edit the config is to press 1e in lazygit, instead of documenting where the file is stored.

[adrian-gierakowski]

This was never a problem for me because I just don't care where lazygit stores its config file. I never try to remember its path.

I think we should address this by advertising more that the way to edit the config is to press 1e in lazygit, instead of documenting where the file is stored.

Regardless of improvements to documentation, I believe that lazygit should check both legacy and new path and give a warning if both are detected.