-
Notifications
You must be signed in to change notification settings - Fork 71
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
making backup doesnt support all linux config paths #172
Comments
good call! I assumed the The solution may be use this function alacritty-themes/src/helpers/index.js Line 85 in 4519540
alacritty-themes/src/helpers/index.js Line 61 in 4519540
do you want to fix it? |
Thanks! But as you said, creating backup files in home direcotry is not really a neat solution. I think fixing this bug needs an oponionated solution which is beyond me.🙂 |
a quick and good solution could be, even if the |
I just fixed the alacritty path, please download the latest version of alacritty-themes to get it working on your end 👍 Thanks for reporting it |
🎉 This issue has been resolved in version 5.0.1 🎉 The release is available on: Your semantic-release bot 📦🚀 |
Descibe the bug
If alacritty config file is not
$HOME/.config/alacritty/alacritty.yml
, (in my case it is$HOME/.alacritty.yml
) it will throw an errorSteps to reproduce
npm i -g alacritty-themes
alacritty-themes
Expected Behavior
Running normally, without errors
Operating System
Arch Linux (Manjaro)
Screenshots
I've looked around the source code a bit. Looks like the problem is from createBackup function. On Linux, when it checks if the config exist, it will check both
$HOME/.config/alacritty/alacritty.yml
and$HOME/.alacritty.yml
. But when it creates a backup file it will always use$HOME/.config/alacritty/alacritty.yml
The text was updated successfully, but these errors were encountered: