Bug#1123877: xterm: display issue with the U+0FE0 character

Thomas Dickey <[email protected]> Fri, 20 Feb 2026 03:42:47 -0500

Newsgroups	gmane.linux.debian.devel.x
Message-ID	<aZgeh7qlkNFQ1h3t__44105.3104166471$1771577139$gmane$org@prl-debianold-64.jexium-island.net>

On Fri, Feb 20, 2026 at 02:51:05AM +0100, Vincent Lefevre wrote:
> Control: reopen -1
> Control: found -1 407-1
> 
> On 2025-12-23 14:10:51 +0100, Vincent Lefevre wrote:
> > I've found this issue after an error in copy-pasting...
> > 
> > Note: For the test with the triple-click, make sure that
> > "a" and ">" are in different character classes.
> > 
> > qaa% printf '<a\u0FE0>\n'
> > <a࿠>
> > 
> > which appears as "<a>" (3 ASCII characters) in xterm. Then
> > triple-click over the "a" character. This gives "<a>>" in
> > reverse video, i.e. the last character is repeated.
> > 
> > And slowly moving a window over the xterm one from left to right
> > transforms the "<a>" into "<a >" (with a space between the "a" and
> > the ">").
> 
> Nothing has changed in xterm 407-1: both issues are still there.

odd.  It definitely worked for me when I was testing the change.

The change in #407 was for a case where the box was drawn and then
immediately overwritten because the width was seen as zero because
wcwidth could return zero either because of a valid combining
character or because it was missing from the Unicode database.

The initial report stated

	This U+0FE0 does not exist in the Unicode database here, but in any
	case, it should be handled in a consistent way.

so I'll keep that goal.

-- 
Thomas E. Dickey <[email protected]>
https://invisible-island.net

signature.asc (application/pgp-signature, 659 B)