classabbyamp
classabbyamp
I was able to reproduce this with both cxx-qt/rust and the minimal-qt-app Leon provided, on xorg (i3wm) with qt 6.6.0 and qt6ct 0.8. Upgrading to qt6ct 0.9 fixed the issue
this looks like the fix: https://github.com/trialuser02/qt6ct/commit/d56a7eb283a225a4ebf0e579907529f89201df30
> Ranges for custom assignment of codepoints to glyphs is AFAIK only available on Kitty, right? Or do we have other TEs allowing that as well? not sure, I've used...
any updates on this? I'm working on packaging this for void linux, and we generally keep with the upstream naming, but if the name is going to change I'd prefer...
there would be no effect, probably, because [`usize` is a `u64` already on 64-bit systems](https://doc.rust-lang.org/src/core/num/mod.rs.html#1192)
Right, so switching usize to u64 would incur no penalty to existing 64bit and have the added benefit of supporting 32bit
+1, i think = makes a lot of sense as a version specifier
https://github.com/void-linux/void-packages/blob/master/Manual.md#updates > `disabled` can be set to disable update checking for the package, in cases where checking for updates is impossible or does not make sense. This should be set...
wait, it's not erroring because of no distfiles, it's erroring because xlint https://github.com/void-linux/void-packages/actions/runs/7078728385/job/19264541980?pr=36419#step:7:9
this looks like it would fix my issue (#499), but it just exits without doing anything: ``` $ LD_LIBRARY_PATH=./lib/ bin/xbps-alternatives/xbps-alternatives -dRlg vim [DEBUG] XBPS: 0.60 API: 20200423 GIT: a9c3af43 [DEBUG]...