-
-
Notifications
You must be signed in to change notification settings - Fork 418
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
[BUG] Reloaded config not applying #1283
Comments
Edit: The issue disappeared when I used the |
Hello, with last commit if i update the css, the widget upload the config without a problem, but the widget doesnt close as the video shows: 412645363-f5d2b592-ae94-4b86-b2f9-5228d9ece510.mp4 |
Pretty sure 29fa158 is the cause of this. It fixes reloading, but opens a new window and does not close the old one. |
Yep.. hope the author of the PR fix it.. |
Checklist before submitting an issue
Description of the bug
I am following the quickstart guide from the documentation and encountered the issue of changes to the configuration not applying to the displayed widget.
Here is my configuration file at
$HOME/.config/eww.yuck
:If I run
./eww daemon; ./eww open example
, the widget shows up as expectedThe issue:
However, when I make any changes to the config file, for example by changing
"Hello world"
to"test"
, the displayed widget doesn't change at all. I also tried changing the height, width, etc., to no avail. I tried fixing this issue by manually calling./eww reload
, but still nothing in the displayed widget changes.I called
./eww logs
can confirmed that eww thinks it was reloading the config file:After rebooting my system, the issue persists. I also tried reloading sway config, but that didn't help either. Since eww thinks it reloaded the config, I believe the issue is with displaying the updated widget.
Temporary workaround:
Restarting the eww daemon by
./eww kill; ./eww daemon; ./eww open example
renders the updated widget.Reproducing the issue
No response
Expected behaviour
Eww displaying the updated widget.
Additional context
No response
Platform and environment
I made sure to build with
cargo build --release --no-default-features --features=wayland
The text was updated successfully, but these errors were encountered: