NetBSD Problem Report #60398
From he@smistad.uninett.no Thu Jul 2 21:47:03 2026
Return-Path: <he@smistad.uninett.no>
Received: from mail.netbsd.org (mail.netbsd.org [199.233.217.200])
(using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)
key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256
client-signature RSA-PSS (2048 bits) client-digest SHA256)
(Client CN "mail.netbsd.org", Issuer "R13" (not verified))
by mollari.NetBSD.org (Postfix) with ESMTPS id 81F1A1A923A
for <gnats-bugs@gnats.NetBSD.org>; Thu, 2 Jul 2026 21:47:03 +0000 (UTC)
Message-Id: <20260702214700.9F00543FA48@smistad.uninett.no>
Date: Thu, 2 Jul 2026 23:47:00 +0200 (CEST)
From: he@NetBSD.org
Reply-To: he@NetBSD.org
To: gnats-bugs@NetBSD.org
Subject: Line drawing in xterm does not work as expected
X-Send-Pr-Version: 3.95
X-From4GNATS: "he@NetBSD.org via gnats" <gnats-admin@NetBSD.org>
>Number: 60398
>Category: xsrc
>Synopsis: Line drawing in xterm does not work as expected
>Confidential: no
>Severity: non-critical
>Priority: medium
>Responsible: xsrc-manager
>State: feedback
>Class: sw-bug
>Submitter-Id: net
>Arrival-Date: Thu Jul 02 21:50:00 +0000 2026
>Closed-Date:
>Last-Modified: Sat Jul 18 08:25:01 +0000 2026
>Originator: Havard Eidnes
>Release: NetBSD 11.99.4
>Organization:
I try...
>Environment:
System: NetBSD st.urc.uninett.no 11.99.4 NetBSD 11.99.4 (GENERIC) #0: Sat Dec 6 13:05:05 UTC 2025 mkrepro@mkrepro.NetBSD.org:/usr/src/sys/arch/amd64/compile/GENERIC amd64
Architecture: x86_64
Machine: amd64
>Description:
The "dua" program from the "dua-cli" package and Jonathan
Perkins' new "bob" package bulk manager from pkgtools/bob
both try to draw using utf-8 line drawing characters in the
terminal.
In an xterm from NetBSD 10.1, I need to bring up the font
menu with "ctrl+right-click" and select "UTF-8 Encoding",
and then a "dua i" invocation produces a nicely framed
drawing with utf-8 line drawing characters.
The same can be done on NetBSD 9.3.
However, if I do the same with xterm from either 11.0_RC5
or 11.99.4, I do not get the same result. The line drawing
characters are all (horizontal or vertical) replaced with
a character 'a' with a '^' on top of it.
This is reproducible with
printf "\xe2\x94\x82\n"
which produces a vertical line drawing character on 9.3
or 10.1, but produces the aforementioned combined 'a'/'^'
on the xterm from the newer OS variants.
Similarly
printf "\xe2\x94\x80\n"
produces a horizontal line drawing character on the older OSes'
xterms, but the aforementioned 'a'/'^' combination character
in the xterm from the newer OS variants.
Locale setting does not appear to make any difference in
the result.
Copying the xterm from a 10.1 system and running it on an
11.99.4 system and running "due i" inside it produces nice
line drawing characters.
So ... this appears to be an xterm issue. Either it now
insists on more settings (unknown to me) to allow UTF-8
coded data, or it has a new bug.
>How-To-Repeat:
See above.
>Fix:
Wouldn't that be nice!
>Release-Note:
>Audit-Trail:
State-Changed-From-To: open->feedback
State-Changed-By: riastradh@NetBSD.org
State-Changed-When: Thu, 02 Jul 2026 23:38:41 +0000
State-Changed-Why:
1. Can you please start a fresh xterm in each version of NetBSD you
tried, started however you normally start xterms, and share the
output of `locale' in each fresh xterm?
2. Can you share any .Xdefaults or .Xresources file you have?
3. Can you share the output of `xrdb -q'?
4. Can you share the output of `appres XTerm'?
When I try running `LC_CTYPE=C xterm' vs `LC_CTYPE=C.UTF-8 xterm', on
netbsd-9 and netbsd-10 userlands, I am able to reproduce exactly what
you described: with LC_CTYPE=C, xterm shows a-with-circumflex; with
LC_CTYPE=C.UTF-8, xterm shows vertical bar.
From: Havard Eidnes <he@NetBSD.org>
To: gnats-bugs@netbsd.org, riastradh@NetBSD.org
Cc: xsrc-manager@netbsd.org, netbsd-bugs@netbsd.org, gnats-admin@netbsd.org
Subject: Re: xsrc/60398 (Line drawing in xterm does not work as expected)
Date: Fri, 03 Jul 2026 14:15:32 +0200 (CEST)
> 1. Can you please start a fresh xterm in each version of NetBSD you
> tried, started however you normally start xterms, and share the
> output of `locale' in each fresh xterm?
I usually don't mess with things I don't have to, so they all
have
$ locale
LANG=""
LC_CTYPE="C"
LC_COLLATE="C"
LC_TIME="C"
LC_NUMERIC="C"
LC_MONETARY="C"
LC_MESSAGES="C"
LC_ALL=""
$
I also have Alt-B and Alt-F committed to muscle memory as usable
line editing characters in tcsh, and if I'm not terribly mistaken,
those are no longer usable in a locale containing UTF-8, and are
instead interpreted as Something Else.
> 2. Can you share any .Xdefaults or .Xresources file you have?
>
> 3. Can you share the output of `xrdb -q'?
These come down to basically the same:
$ xrdb -q | egrep -i xterm
XTerm*ScrollBar: true
XTerm*scrollbar*thickness: 7
XTerm*multiScroll: true
XTerm*saveLines: 1000
XTerm*scrollInput: false
XTerm*scrollKey: true
XTerm*visualBell: true
XTerm*cursorColor: violet red
xterm.waitforwm: false
XTerm*background: bisque
XTerm*foreground: black
XTerm*deleteIsDEL: true
XTerm*ptyInitialErase: true
XTerm*ttyModes: erase ^?
XTerm*numLock: false
XTerm*backarrowKeyIsErase: true
XTerm*backarrowKey: true
$
> 4. Can you share the output of `appres XTerm'?
$ appres XTerm
*tekMenu*vtshow*Label: Show VT Window
*tekMenu*tektextsmall*Label: Small Characters
*tekMenu*vtmode*Label: Switch to VT Mode
*tekMenu*tektextlarge*Label: Large Characters
*tekMenu*tekpage*Label: PAGE
*tekMenu*tekreset*Label: RESET
*tekMenu*tektext2*Label: #2 Size Characters
*tekMenu*tekhide*Label: Hide Tek Window
*tekMenu*tekcopy*Label: COPY
*tekMenu*tektext3*Label: #3 Size Characters
*tekMenu.Label: Tek Options
*MenuButton*borderWidth: 0
*menubar.borderWidth: 0
*mainMenu*redraw*Label: Redraw Window
*mainMenu*oldFunctionKeys*Label: Old Function-Keys
*mainMenu*interrupt*Label: Send INT Signal
*mainMenu*8-bit control*Label: 8-Bit Controls
*mainMenu*logging*Label: Log to File
*mainMenu*sunFunctionKeys*Label: Sun Function-Keys
*mainMenu*hangup*Label: Send HUP Signal
*mainMenu*print-immediate*Label: Print-All Immediately
*mainMenu*sunKeyboard*Label: VT220 Keyboard
*mainMenu*terminate*Label: Send TERM Signal
*mainMenu*backarrow key*Label: Backarrow Key (BS/DEL)
*mainMenu*print-on-error*Label: Print-All on Error
*mainMenu*hpFunctionKeys*Label: HP Function-Keys
*mainMenu*kill*Label: Send KILL Signal
*mainMenu*num-lock*Label: Alt/NumLock Modifiers
*mainMenu*toolbar*Label: Toolbar
*mainMenu*print*Label: Print Window
*mainMenu*scoFunctionKeys*Label: SCO Function-Keys
*mainMenu*quit*Label: Quit
*mainMenu*alt-esc*Label: Alt Sends Escape
*mainMenu*print-redir*Label: Redirect to Printer
*mainMenu*fullscreen*Label: Full Screen
*mainMenu*tcapFunctionKeys*Label: Termcap Function-Keys
*mainMenu*meta-esc*Label: Meta Sends Escape
*mainMenu*dump-html*Label: XHTML Screen Dump
*mainMenu*securekbd*Label: Secure Keyboard
*mainMenu*suspend*Label: Send STOP Signal
*mainMenu*dump-svg*Label: SVG Screen Dump
*mainMenu*allowsends*Label: Allow SendEvents
*mainMenu*delete-is-del*Label: Delete is DEL
*mainMenu*continue*Label: Send CONT Signal
*mainMenu.Label: Main Options
*tek4014*fontLarge: 9x15
*tek4014*font2: 8x13
*tek4014*font3: 6x13
*tek4014*fontSmall: 6x10
*SimpleMenu*menuLabel.font: -adobe-helvetica-bold-r-normal--*-120-*-*-*-*-iso8859-*
*SimpleMenu*menuLabel.vertSpace: 100
*SimpleMenu*Sme.height: 16
*SimpleMenu*BackingStore: NotUseful
*SimpleMenu*HorizontalMargins: 16
*SimpleMenu*Cursor: left_ptr
*SimpleMenu*borderWidth: 2
*fontMenu*allow-bold-fonts*Label: Bold Fonts
*fontMenu*font2*Label: Tiny
*fontMenu*utf8-title*Label: UTF-8 Titles
*fontMenu*font-linedrawing*Label: Line-Drawing Characters
*fontMenu*font3*Label: Small
*fontMenu*allow-color-ops*Label: Allow Color Ops
*fontMenu*font-doublesize*Label: Doublesized Characters
*fontMenu*font4*Label: Medium
*fontMenu*allow-font-ops*Label: Allow Font Ops
*fontMenu*font-loadable*Label: VT220 Soft Fonts
*fontMenu*font5*Label: Large
*fontMenu*allow-mouse-ops*Label: Allow Mouse Ops
*fontMenu*font-packed*Label: Packed Font
*fontMenu*fontdefault*Label: Default
*fontMenu*font6*Label: Huge
*fontMenu*allow-tcap-ops*Label: Allow Termcap Ops
*fontMenu*render-font*Label: TrueType Fonts
*fontMenu*font1*Label: Unreadable
*fontMenu*font7*Label: Enormous
*fontMenu*allow-title-ops*Label: Allow Title Ops
*fontMenu*utf8-mode*Label: UTF-8 Encoding
*fontMenu*fontescape*Label: Escape Sequence
*fontMenu*allow-window-ops*Label: Allow Window Ops
*fontMenu*fontsel*Label: Selection
*fontMenu*utf8-fonts*Label: UTF-8 Fonts
*fontMenu.Label: VT Fonts
*vtMenu*keepSelection*Label: Keep Selection
*vtMenu*autowrap*Label: Enable Auto Wraparound
*vtMenu*titeInhibit*Label: Enable Alternate Screen Switching
*vtMenu*altscreen*Label: Show Alternate Screen
*vtMenu*keepClipboard*Label: Keep Clipboard
*vtMenu*reversewrap*Label: Enable Reverse Wraparound
*vtMenu*activeicon*Label: Enable Active Icon
*vtMenu*sixelScrolling*Label: Sixel Scrolling
*vtMenu*selectToClipboard*Label: Select to Clipboard
*vtMenu*autolinefeed*Label: Enable Auto Linefeed
*vtMenu*softreset*Label: Do Soft Reset
*vtMenu*privateColorRegisters*Label: Private Color Registers
*vtMenu*cursesemul*Label: Enable Curses Emulation
*vtMenu*scrollbar*Label: Enable Scrollbar
*vtMenu*appcursor*Label: Enable Application Cursor Keys
*vtMenu*hardreset*Label: Do Full Reset
*vtMenu*visualbell*Label: Enable Visual Bell
*vtMenu*appkeypad*Label: Enable Application Keypad
*vtMenu*clearsavedlines*Label: Reset and Clear Saved Lines
*vtMenu*bellIsUrgent*Label: Enable Bell Urgency
*vtMenu*scrollkey*Label: Scroll to Bottom on Key Press
*vtMenu*tekshow*Label: Show Tek Window
*vtMenu*scrollttyoutput*Label: Scroll to Bottom on Tty Output
*vtMenu*jumpscroll*Label: Enable Jump Scroll
*vtMenu*poponbell*Label: Enable Pop on Bell
*vtMenu*tekmode*Label: Switch to Tek Mode
*vtMenu*allow132*Label: Allow 80/132 Column Switching
*vtMenu*reversevideo*Label: Enable Reverse Video
*vtMenu*cursorblink*Label: Enable Blinking Cursor
*vtMenu*vthide*Label: Hide VT Window
*vtMenu.Label: VT Options
*form.Thickness: 0
*VT100.utf8Fonts.font4: -misc-fixed-medium-r-normal--13-120-75-75-c-80-iso10646-1
*VT100.utf8Fonts.font2: -misc-fixed-medium-r-normal--8-80-75-75-c-50-iso10646-1
*VT100.utf8Fonts.font6: -misc-fixed-medium-r-normal--20-200-75-75-c-100-iso10646-1
*VT100.utf8Fonts.font5: -misc-fixed-medium-r-normal--18-120-100-100-c-90-iso10646-1
*VT100.utf8Fonts.font3: -misc-fixed-medium-r-normal--14-130-75-75-c-70-iso10646-1
*VT100.utf8Fonts.font: -misc-fixed-medium-r-semicondensed--13-120-75-75-c-60-iso10646-1
*VT100.utf8Fonts.font7: -adobe-courier-medium-r-normal--24-240-75-75-m-150-iso10646-1
*VT100.font4: 7x13
*VT100.font2: 5x7
*VT100.font6: 10x20
*VT100.font5: 9x15
*VT100.font3: 6x10
*VT100.font1: nil2
*VT100.font7: -adobe-courier-medium-r-normal--24-240-75-75-m-150-iso10646-1
XTerm*scrollbar*thickness: 7
XTerm*scrollKey: true
XTerm*ptyInitialErase: true
XTerm*backarrowKey: true
XTerm*background: bisque
XTerm*visualBell: true
XTerm*multiScroll: true
XTerm*ttyModes: erase ^?
XTerm*foreground: black
XTerm*cursorColor: violet red
XTerm*ScrollBar: true
XTerm*saveLines: 1000
XTerm*numLock: false
XTerm*scrollInput: false
XTerm*deleteIsDEL: true
XTerm*backarrowKeyIsErase: true
*saveLines: 1024
*IconFont: nil2
*allowWindowOps: false
*pointerMode: 0
$
> When I try running `LC_CTYPE=C xterm' vs `LC_CTYPE=C.UTF-8
> xterm', on netbsd-9 and netbsd-10 userlands, I am able to
> reproduce exactly what you described: with LC_CTYPE=C, xterm
> shows a-with-circumflex; with LC_CTYPE=C.UTF-8, xterm shows
> vertical bar.
If I start xterm on netbsd-9 and netbsd-10 without any LANG or
LC_CTYPE in the environment, bring up the font menu and select
"UTF-8 Encoding", I get line drawing characters for the UTF-8
sequences for those characters in that xterm.
If I do the same on netbsd-11, I do not. Evidently with that
version, xterm *must* be started in an environment / locale setting
which includes UTF-8 for that to work, and in that case the font
menu entries related to UTF-8 are greyed out in the newly started
xterm.
So ... in the new xterm version, the dynamic choice of "UTF-8
Encoding" no longer appears to be possible.
So ... in a sense I now have a workaround.
Regards,
- Havard
From: Valery Ushakov <uwe@stderr.spb.ru>
To: gnats-bugs@netbsd.org
Cc:
Subject: Re: xsrc/60398 (Line drawing in xterm does not work as expected)
Date: Fri, 3 Jul 2026 16:06:54 +0300
FWIW, I have a slightly old 11 beta machine (2025-10-06).
<uwe@omena:~> (1023) locale
LANG=""
LC_CTYPE="en_US.UTF-8"
LC_COLLATE="C"
LC_TIME="C"
LC_NUMERIC="C"
LC_MONETARY="C"
LC_MESSAGES="C"
and xterm from that machine draws
printf '\xe2\x94\x82\n'
as a vertial line U+2502 "BOX DRAWINGS LIGHT VERTICAL"
Nothing interesting in the xrdb (besides colors/font, etc).
-uwe
From: mlelstv@serpens.de (Michael van Elst)
To: gnats-bugs@netbsd.org
Cc:
Subject: Re: xsrc/60398 (Line drawing in xterm does not work as expected)
Date: Fri, 3 Jul 2026 15:10:28 -0000 (UTC)
he@NetBSD.org (Havard Eidnes) writes:
>If I do the same on netbsd-11, I do not. Evidently with that
>version, xterm *must* be started in an environment / locale setting
>which includes UTF-8 for that to work, and in that case the font
>menu entries related to UTF-8 are greyed out in the newly started
>xterm.
If you start xterm with a UTF-8 locale, then UTF-8 encoding is enabled
and the menu entry is greyed out, so you cannot disable it at run-time.
If you start xterm with a non-UTF-8 locale, then UTF-8 encoding is
disabled and you can enable it at run-time.
That's true here for netbsd-10, netbsd-11 and -current.
No idea how you can disable UTF-8 encoding and grey out the menu entry
at the same time.
What you can do is to enable UTF-8 encoding and grey out the menu entry
(i.e. turn on UTF-8 by some means) and wrap your command or shell
in luit. xterm will do that automatically e.g. with the -lc option.
Then your UTF8 line drawing characters will fail als luit tries to
translate them according to your 8bit locale.
From: mlelstv@serpens.de (Michael van Elst)
To: gnats-bugs@netbsd.org
Cc:
Subject: Re: xsrc/60398 (Line drawing in xterm does not work as expected)
Date: Fri, 3 Jul 2026 16:07:30 -0000 (UTC)
he@NetBSD.org (Havard Eidnes) writes:
>So ... in the new xterm version, the dynamic choice of "UTF-8
>Encoding" no longer appears to be possible.
Ok. I can reproduce that.
xterm still behaves the same regarding the menu. I.e. in non-UTF8
mode, there is still a menu to enable it and the option is then also
checked.
But this menu choice has no consequence. xterm will still not use
UTF-8 encoding.
From: Valery Ushakov <uwe@stderr.spb.ru>
To: gnats-bugs@netbsd.org
Cc:
Subject: Re: xsrc/60398 (Line drawing in xterm does not work as expected)
Date: Fri, 3 Jul 2026 19:34:16 +0300
On Fri, Jul 03, 2026 at 16:10:04 +0000, Michael van Elst via gnats wrote:
> Ok. I can reproduce that.
>
> xterm still behaves the same regarding the menu. I.e. in non-UTF8
> mode, there is still a menu to enable it and the option is then also
> checked.
>
> But this menu choice has no consequence. xterm will still not use
> UTF-8 encoding.
We are at 397, and this might be a bug that was introduced in 390 and
fixed in 407, if I correctly read
https://xterm.dev/changelog-xterm/#xterm_407
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1124802
(I'm just skimming, so I may be mistaken). The workaround - from that
debian bug - is to
tput rs2
after switching via manu to utf-8
-uwe
From: mlelstv@serpens.de (Michael van Elst)
To: gnats-bugs@netbsd.org
Cc:
Subject: Re: xsrc/60398 (Line drawing in xterm does not work as expected)
Date: Fri, 3 Jul 2026 22:52:15 -0000 (UTC)
gnats-admin@NetBSD.org ("Valery Ushakov via gnats") writes:
> https://xterm.dev/changelog-xterm/#xterm_407
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1124802
Yes,
| improve switching to/from UTF-8 mode by saving, restoring and resetting the G0-G3 array (Debian #1124802).
that's it.
From: RVP <rvp@SDF.ORG>
To: gnats-bugs@netbsd.org
Cc:
Subject: Re: xsrc/60398 (Line drawing in xterm does not work as expected)
Date: Fri, 3 Jul 2026 23:35:48 +0000 (UTC)
On Fri, 3 Jul 2026, Michael van Elst via gnats wrote:
> he@NetBSD.org (Havard Eidnes) writes:
>
> >So ... in the new xterm version, the dynamic choice of "UTF-8
> >Encoding" no longer appears to be possible.
>
>
> Ok. I can reproduce that.
>
> xterm still behaves the same regarding the menu. I.e. in non-UTF8
> mode, there is still a menu to enable it and the option is then also
> checked.
>
> But this menu choice has no consequence. xterm will still not use
> UTF-8 encoding.
>
This, in ~/.Xresources, also works:
```
XTerm*locale: false
XTerm*utf8: true
```
This turns on UTF-8 mode by default; and toggling it via the menu also seems
to work (ie. printf $'\u2502\n' prints differently in an xterm started with
LC_ALL=C).
But really, if you want UTF-8 chars. to be interpreted, you should just run
with a UTF-8 locale (and a font with wide Unicode coverage) so that xterm DTRT.
-RVP
From: mlelstv@serpens.de (Michael van Elst)
To: gnats-bugs@netbsd.org
Cc:
Subject: Re: xsrc/60398 (Line drawing in xterm does not work as expected)
Date: Sat, 4 Jul 2026 06:17:21 -0000 (UTC)
gnats-admin@NetBSD.org ("Michael van Elst via gnats") writes:
>The following reply was made to PR xsrc/60398; it has been noted by GNATS.
>From: mlelstv@serpens.de (Michael van Elst)
>To: gnats-bugs@netbsd.org
>Cc:
>Subject: Re: xsrc/60398 (Line drawing in xterm does not work as expected)
>Date: Fri, 3 Jul 2026 22:52:15 -0000 (UTC)
> gnats-admin@NetBSD.org ("Valery Ushakov via gnats") writes:
>
> > https://xterm.dev/changelog-xterm/#xterm_407
> > https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1124802
>
>
> Yes,
>
> | improve switching to/from UTF-8 mode by saving, restoring and resetting the G0-G3 array (Debian #1124802).
>
> that's it.
>
Here is a point fix with only that change:
Index: external/mit/xterm/dist/ptydata.c
===================================================================
RCS file: /cvsroot/xsrc/external/mit/xterm/dist/ptydata.c,v
retrieving revision 1.1.1.12
diff -p -u -r1.1.1.12 ptydata.c
--- external/mit/xterm/dist/ptydata.c 9 Mar 2025 23:17:11 -0000 1.1.1.12
+++ external/mit/xterm/dist/ptydata.c 4 Jul 2026 06:13:12 -0000
@@ -345,6 +345,12 @@ switchPtyData(TScreen *screen, int flag)
mk_wcwidth_init(screen->utf8_mode);
TRACE(("turning UTF-8 mode %s\n", BtoS(flag)));
+ if (flag) {
+ saveCharsets(screen, screen->ansi_save_gsets);
+ resetCharsets(screen);
+ } else {
+ restoreCharsets(screen, screen->ansi_save_gsets);
+ }
update_font_utf8_mode();
}
}
@@ -654,6 +660,25 @@ Panic(const char *s, int a)
}
#if OPT_WIDE_CHARS
+void
+saveCharsets(TScreen *screen, DECNRCM_codes * target)
+{
+ (void) screen;
+ (void) target;
+}
+
+void
+restoreCharsets(TScreen *screen, const DECNRCM_codes * target)
+{
+ (void) screen;
+ (void) target;
+}
+
+void
+resetCharsets(TScreen *screen)
+{
+ (void) screen;
+}
#ifdef ALLOWLOGGING
void
Index: external/mit/xterm/dist/ptyx.h
===================================================================
RCS file: /cvsroot/xsrc/external/mit/xterm/dist/ptyx.h,v
retrieving revision 1.22
diff -p -u -r1.22 ptyx.h
--- external/mit/xterm/dist/ptyx.h 9 Mar 2025 23:18:48 -0000 1.22
+++ external/mit/xterm/dist/ptyx.h 4 Jul 2026 06:13:12 -0000
@@ -2917,6 +2917,9 @@ typedef struct {
Char vt52_save_curss;
DECNRCM_codes vt52_save_gsets[NUM_GSETS2];
#endif
+#if OPT_WIDE_CHARS
+ DECNRCM_codes ansi_save_gsets[NUM_GSETS2];
+#endif
/* Testing */
#if OPT_XMC_GLITCH
unsigned xmc_glitch; /* # of spaces to pad on SGR's */
From: "Michael van Elst" <mlelstv@netbsd.org>
To: gnats-bugs@gnats.NetBSD.org
Cc:
Subject: PR/60398 CVS commit: xsrc/external/mit/xterm/dist
Date: Sat, 18 Jul 2026 08:20:30 +0000
Module Name: xsrc
Committed By: mlelstv
Date: Sat Jul 18 08:20:30 UTC 2026
Modified Files:
xsrc/external/mit/xterm/dist: ptydata.c ptyx.h
Log Message:
Point fix to repair UTF-8 menu selection (from xterm 407)
See PR xsrc/60398.
To generate a diff of this commit:
cvs rdiff -u -r1.1.1.12 -r1.2 xsrc/external/mit/xterm/dist/ptydata.c
cvs rdiff -u -r1.22 -r1.23 xsrc/external/mit/xterm/dist/ptyx.h
Please note that diffs are not public domain; they are subject to the
copyright notices on the relevant files.
>Unformatted:
(Contact us)
$NetBSD: query-full-pr,v 1.51 2026/08/10 02:28:17 riastradh Exp $
$NetBSD: gnats_config.sh,v 1.10 2026/05/13 22:00:09 riastradh Exp $
Copyright © 1994-2026
The NetBSD Foundation, Inc. ALL RIGHTS RESERVED.
Home