Animesh Sahu
Animesh Sahu
Actually problem even gets increased due to 5 connection retries, this makes the startup of the server very slow as well as chances of this bug to happen. I'd suggest...
Can we just move the `init_async_part` at the top of `server::initialize_server` and handle any error to stop the thread handle (instead of `?` at end of result)? And reduce connection...
I had a random thought, can we just apply a lock/mutex for `eww [open|open-many|daemon|kill|reload]` commands from the start line of `main()` to the end of main? with a timeout so...
Random thought came to my mind because `eww open bar && eww open bar` never had this problem i.e. when one waits for the other to finish. Only when launching...
Oh right, it forks the process and returns the parent before complete initialization 🤔🤔. But we can still pass the responsibility to the child fork to unlock the lock for...
True, we can potentially poll for `lsblk` or `ip link show` to get required interfaces for these 2 magic var, this might be a topic for future if more variables...
If we can `awk` or `sed` probably most of the text based manipulations can be done easily as well. +1, perfect idea! Edit: vararg pipes can also be useful, seems...
https://github.com/Animeshz/eww/blob/275c67d74d84b7a8cbe397ec83abe599a2330188/crates/eww/src/app.rs#L219-L220 These (flagging when any property change) breaks the counting, there has to be some better way to take account of the referenced variables within variable parameters somewhat like there...
https://gitlab.gnome.org/GNOME/gtk/-/issues/3012 https://people.gnome.org/~ebassi/docs/_build/Gtk/4.0/property.Widget.overflow.html Seems like GTK does support it, but programmatically & not with css.