-
Notifications
You must be signed in to change notification settings - Fork 61
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
lazygit fails to open on first launch due to the assumption that config.yml exists #455
Comments
I would have just submitted a PR, but I'm not entirely sure how to mitigate the issue. EDIT - I suppose the ideal way would be to feed it into home-manager's |
I was about to say that I couldn't replicate this, but then I realized that the config file is always being created for me via home-manager's install before a run can be tried. Out of curiosity, how are you installing lazygit? |
I experienced this issue a few months ago (https://discord.com/channels/907385605422448742/1089733914328838294/1318055416684482590) because I deleted my (empty) lazygit config file for some forgotten reason, and home-manager actually wasn't recreating it... |
We support this here via importYAML It uses IFD which isn't great, but if there are no other alternative to applying the configuration in a mergeable (with other user settings) way, I'd say it's fine |
Like this. |
Actually, looking at the commit history, it looks like this is how it was being done prior to #304. |
Currently, the lazygit module assumes
config.yml
exists in its default location when it sets$LG_CONFIG_FILE
, but that file doesn't get created until first launch, and if the aforementioned variable contains a file that doesn't exist, it fails to launch.The text was updated successfully, but these errors were encountered: