Hi Miles,
Miles Alan writes:
Interesting - thanks for reporting. I'd be curious what WM_TRANSIENT_FOR
is set to in pinentry's case. The case I'm trying to address is resizable
SDL applications which, as mentioned earlier, wholesale set WM_TRANSIENT_FOR
to the root window. I'm not sure on the
commit c3e47c1f4474061b8c37937247c17c6f11b7e18c
Author: Michael Forney
AuthorDate: Tue Mar 22 17:14:53 2022 -0700
Commit: Michael Forney
CommitDate: Tue Mar 22 17:20:51 2022 -0700
Fix LICENSE name
The license text matches (and has always matched) what is known as
the
On Tue, Mar 22, 2022 at 06:06:30PM +0100, Stein Gunnar Bakkeby wrote:
> With the first patch the text is still allowed to bleed into the right hand
> side padding as long as it fits.
>
> I worked around that by reducing w with 2 * lpad and adding lpad to x
> before returning.
Ahh, sorry my bad.
On Tue, Mar 22, 2022 at 06:06:30PM +0100, Stein Gunnar Bakkeby wrote:
> With the first patch the text is still allowed to bleed into the right hand
> side padding as long as it fits.
>
> I worked around that by reducing w with 2 * lpad and adding lpad to x
> before returning.
Yeah, that's what
With the first patch the text is still allowed to bleed into the right hand
side padding as long as it fits.
I worked around that by reducing w with 2 * lpad and adding lpad to x
before returning.
Overall it makes sense. I'd assume the code in dwm would be identical.
I was thinking that the
>
> But I still see the
> prompt getting incorrectly cut off and the ellipsis still don't get
> rendered in case of font change.
I see, you mean in the edge case that there is a font change, but there is
not enough space to add a single utf8 character for that font.
You can just move the
