Hanssen

My solution for this problem is wrapping the `cargo` executable. `/usr/local/bin/cargo`: ```sh #!/bin/sh CARGO_PATH=/usr/bin/cargo if test ! -z ${RUST_ANALYZER}; then CARGO_TOML_PATH=$(${CARGO_PATH} locate-project --workspace --message-format=plain 2> /dev/null) if test ! -z...

Same here, built from commit b4fdc0be52d7c3e48e932698bafc3f69dbd45b3b (CI: update nix install action). The hyprpaper detected the monitor changed event but didn't apply the configuration to the new monitor.

https://github.com/hyprwm/hyprpaper/blob/66b3ba8d9faa6b6a8894ecc03ac61667d344b8bc/src/helpers/Monitor.hpp#L9 I tried a few times and found that the new `description` field is the problem. New monitor detection works on [3bfaac0](https://github.com/hyprwm/hyprpaper/commit/3bfaac09f58ce31c33e1a56e7eaa606a87fe4c32) but stops working after adding this property only....

https://github.com/hyprwm/hyprpaper/blob/66b3ba8d9faa6b6a8894ecc03ac61667d344b8bc/src/render/LayerSurface.cpp#L35 The event listeners are correctly registered for all monitors, but the event handler: https://github.com/hyprwm/hyprpaper/blob/66b3ba8d9faa6b6a8894ecc03ac61667d344b8bc/src/events/Events.cpp#L81 is not called for my external monitor.

> can you create some updating mechanism to not redownload whole code after new release and rewrite all parameters and cookies and loses users statistics, but just launch some script...

> actualy i act like you said, but sometimes you change config.json also with release (like now in 4.0.0 you add Gemini), so you anyway need to refill this file...

> Thx so much for your contribution! And special thanks for trying to solve the markdown problem! Please fix the problem with importing the `md2tgmd` package and then I'll look...

> Maybe u need to put `md2tgmd.py` inside `src` directory? (it's a common structure of python packages) I guess so. But `md2tgmd` is not my project, I'm trying to avoid...

> I see... Maybe we can just include this file separately without pip 🙃  I tried to build it from scratch, and it succeeded. Not sure what's the problem.

``` > python --version Python 3.11.6 > pip --version pip 23.2.1 from /home/hanssen/Programs/GPT-Telegramus/venv/lib/python3.11/site-packages/pip (python 3.11) ```