Greetings,
I recently submitted a bug on Arch linux, as I found that after a system-wide update urxvt hung with 100% CPU usage and I had to force kill.[1] I thought it was a package error, but it turns out that something about 9.26 (vs. 9.22 which was my previous version) didn't like one of my .Xdefaults settings. I wasn't sure which one, but got it working eventually. I attached the one that broke along with what is now working. The urxvt maintainer at Arch proposed that the offending settings were: ``` URxvt*tab-bg URxvt*tab-fg URxvt*tabbar-bg URxvt*tabbar-fg ``` ...and that I was missing the 'tabbedex' prefix: ``` URxvt*tabbedex.tab-bg ``` I noticed in my .Xdefaults (made some time ago) that I likely was confused about . vs. * at the time, so I looked into this and my recent understanding is that . should match a specific setting heirarchy. On the other hand, I thought * would fuzzy match anything that followed.[2] If this is the case, it's not clear to me that I'd have to insert tabbedex, as * should match any combo? ``` Urxvt.[something or nothing.]tab-bg ``` After learning this "bug" was ultimately a config file issue, I thought it might still be good to report, as I would generally expect something like a goofed color setting to fall back on a default or simply error out and not start vs. hanging. In any case, I'm passing this along for reference. Thanks for taking a look! Best regards, John [1] https://bugs.archlinux.org/task/70952 [2] https://unix.stackexchange.com/questions/388582/xresources-xdefaults-period-or-asterisk
Xdefaults-working
Description: Binary data
Xdefaults-bad
Description: Binary data
_______________________________________________ rxvt-unicode mailing list [email protected] http://lists.schmorp.de/mailman/listinfo/rxvt-unicode
