-
Notifications
You must be signed in to change notification settings - Fork 2.9k
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
Restart config monitor on file reload #7981
Comments
you need to touch imported files and not the main one to reload them. |
If I modify (or touch) the toml file being imported (say theme.toml), it does not auto reload the config (as I believe it should). Instead, I need to touch the top level config (alacritty.toml) for it reload the changes I made in theme.toml |
Any symlinking involved? It works just fine for me. |
My entire
But inside the
|
Nvm, I managed to reproduce without symlinks. |
Is it accurate to say you added the import after starting Alacritty? Config imports are only monitored if the import is present at startup. |
Yes, that seems to be the issue. If I restart alacritty now changes to my theme files are auto reloaded. |
I think there's two reasonable options here, both of which should work fine:
|
My config imports a theme file but live_config_reload doesn't work and doesn't work if I comment out the import?? |
Making changes to a configuration file that is imported by the main alacritty.toml file do not trigger an automatic config reload.
In order to get the changes without restarting alacritty I normally just do something like
touch ~/.config/alacritty/alacritty.toml
.System
OS: Linux
Version: alacritty 0.13.2 (bb8ea18)
The text was updated successfully, but these errors were encountered: