On Tue, May 11, 2021 at 08:00:24AM +0200, Philipp Marek wrote:
> > That's more likely a problem with the X server than xterm
> > (the menus are via Xaw, which is pretty stable).
>
> So the menus being cut off on the right and the bottom is on purpose?
>
>
> > For instance,
> > you might be using Wayland...
>
> No, I don't think so:
>
> 1156 ? Ssl 0:17 /usr/bin/sddm
> 1199 tty7 Ssl+ 161:33 \_ /usr/lib/xorg/Xorg -nolisten tcp -auth
> /var/run/sddm/{ef674451-7b94-4f32-8c33-3e49df7fdecc} -background none
> -noreset -displayfd 17 -seat seat0 vt7
>
> And I don't have any other garbage on the display either...
Xaw (e.g,. libxaw7:amd64) draws the menus, but uses X resources.
In a quick check (looking at the debugging trace), I suppose that
xterm's event-loop may handle exposure events for the menus(*), but
xterm doesn't know what's in the menus, in that level of detail.
It's possible that you have some font resource (such as a proportional
font) which confuses it, causing it to write outside its window.
But that would be apparent in xterm (thinking that a wildcard font
resource which affects one would affect both).
Given that, I'm expecting that the answer is that the X server
(for some less-used device) is not handling the window properly.
(*) the debugging trace shows me the window-id, but not the creator...
--
Thomas E. Dickey <dickey@invisible-island.net>
https://invisible-island.net
ftp://ftp.invisible-island.net
Attachment:
signature.asc
Description: PGP signature