I would like to see the rxvt hints patch from the Awesome wiki added to rxvt-unicode ebuild. Quote from the wiki "When using urxvt (rxvt-unicode) without hints you can get artifacts on the buttom of the screen." There is a screenshot on the wiki that will display the problem. I have tested the patch with rxvt-unicode:9.09 and confirmed that the problem is still there and the patch is working. URL to the patch and some more info -> http://awesome.naquadah.org/wiki/Urxvt_Hints
Created attachment 255207 [details, diff] Urxvt hints patch
Please don't CC maintainers when you cannot assign bugs.
Don't remove maintainers either. :)
heh :) Jeroen, we could add a force-hints USE flag for it, what do you think?
Created attachment 255283 [details, diff] ebuild patch that disables smart-resize hmm, there's a configure option called "smart-resize". Lasse, could you try rebuilding rxvt-unicode without the patch, with this option disabled? If it works, we can add a USE flag for this instead of an unsupported patch.
(In reply to comment #5) > Created an attachment (id=255283) [details] > ebuild patch that disables smart-resize > > hmm, there's a configure option called "smart-resize". > > Lasse, could you try rebuilding rxvt-unicode without the patch, with this > option disabled? If it works, we can add a USE flag for this instead of an > unsupported patch. > Apparently smart resize is by default off with --enable-everything. I did however test with both --enable and --disable with no change to my issue. Quote from http://pod.tst.eu/http://cvs.schmorp.de/rxvt-unicode/doc/rxvt.7.pod#Character_widths_are_not_correct "--enable-smart-resize (default: off) Add smart growth/shrink behaviour when resizing. This should keep the window corner which is closest to a corner of the screen in a fixed position."
*** Bug 348382 has been marked as a duplicate of this bug. ***
I'm waiting for upstream to actually respond to the thread in the URL, but it has released two new versions without a hint (haha) of a patch. Could somebody give that thread a poke, please, seeing as there is interest in this patch, and my being reluctant to deviate to far from upstream's course.
(In reply to comment #8) > I'm waiting for upstream to actually respond to the thread in the URL, but it > has released two new versions without a hint (haha) of a patch. Could somebody > give that thread a poke, please, seeing as there is interest in this patch, and > my being reluctant to deviate to far from upstream's course. > I don't think upstream will apply the patch as the code change, even if it solves the problem, is not any good. But i don't see why it should be a problem to add it as an optional patch with a use flag, several other ebuilds got patches that isn't applied or supported by upstream.
Patch added, enabled by the 'force-hints' USE flag. Thanks for reporting :)
