On Jun 10 08:41:46, marc.espie.openbsd@gmail.com wrote:
> On Wed, Jun 10, 2026 at 12:39:50AM +0200, Kirill A. Korinsky wrote:
> > On Tue, 09 Jun 2026 22:09:00 +0200,
> > Marc Espie <marc.espie.openbsd@gmail.com> wrote:
> > > 
> > > I've recently started using urxvt instead of xterm everywhere,
> > > in major part because xterm was losing glyphs, and after a few months
> > > of not figuring out why (and asking the guys in charge of X11 and drm
> > > I didn't get any useful answer for my setup) I decided to switch.
> > >
> > 
> > I not completley understand what do you mean as "losing glyphs" but if you
> > mean text on resize of screen...
> 
> No, it's just some glyphs on my xterm that would randomly not show. With
> absolutely zero error messages and randomness. And it would happen after
> a while, that could be some random e that would not show. Quite infuriating.

Sorry, I don't get it: do you mean an everyday ascii 'e'
in a textual output would not show in an xterm?
I have never seen that.

The font xterm is using (as in xterm -fn) doesn't necessarily
have a glyph for each and every unicode character, but they
all cover ascii, right?

	Jan


> 
> > When, it actually was fixed by me and patches was included into 406 and 407
> > release.
> 
> Maybe it's that, I'll try an xterm or two, though I've gotten used to
> urxvt by now.
> 
> > So, if it is your case, I think xterm from -current should make your happy.
> 
>