KATANAND
KATANAND
Should the README point to *2025* roadmap? https://github.com/typstyle-rs/typstyle/blob/a9e3c8bedab2c5f6e18266d391205572b293c582/README.md?plain=1#L184 Thanks for your work!
> Hi, Thanks for pointing out! Would you mind open a quick PR to fix it? On this occasion i would like to throw in a few questions if you...
yeah, same for me
The first question that comes to mind: Do you have something like `set -as terminal-features ",alacritty*:RGB"` in your tmux config? You can check [ArchWiki page on tmux](https://wiki.archlinux.org/title/Tmux#Setting_the_correct_term) for more details
Due to me being not savvy enough to understand this fully, i might have done something wrong. Here are the steps i took: `git clone qtile && git apply 5228.patch...
sorry. i don't really know what i am doing)) ```bash $ git clone ... && git apply ... && cd qtile $ uv venv && source .venv/bin/activate && uv pip...
> I think what you've got there is right. Does your log have stuff like: > > ``` > set backlight perms on /sys/class/backlight/intel_backlight/brightness > ``` > > ? >...
> I think this is the bug: the udev script exit(1)s and fails to chown the brightness file. Too bad you didn't get a log though -- I did push...
just in case, i've checked /tmp/qtile_udev.log a few times during this period and it looks the same as it used to
> So I'm wondering: maybe it's better we write this small amount of code as a standalone bash script/rust program instead of including it here, so we can include it...