Date: Sun, 18 Mar 2018 10:22:59 -0400 From: Thomas Dickey <dickey@his.com> To: Bob Willcox <bob@immure.com> Cc: freebsd-x11@freebsd.org Subject: Re: xterm displaying two chars for one, 2nd looks to be a space Message-ID: <20180318142259.GA5224@prl-debian8-64.jexium-island.net> In-Reply-To: <20180318140337.GM71303@rancor.immure.com> References: <20180318140337.GM71303@rancor.immure.com>
next in thread | previous in thread | raw e-mail | index | archive | help
--YiEDa0DAkWCtVeE4 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Sun, Mar 18, 2018 at 09:03:37AM -0500, Bob Willcox wrote: > Hi All, >=20 > I just did an new install of the latest Freebsd 12.0-CURRENT: >=20 > FreeBSD anakin.immure.com 12.0-CURRENT FreeBSD 12.0-CURRENT #1 r331115: S= un Mar 18 06:58:19 CDT 2018 bob@anakin.immure.com:/usr/obj/usr/src/amd6= 4.amd64/sys/ANIKIN amd64 >=20 > and have installed xorg-7.7_3. My window manager is ctwm-4.0.1,1 and xter= m is > xterm-331. >=20 > Now for my problem: when I start up an xterm in X from ctwm I get two > characters for every one entered, with the second one being a space. >=20 > For example, when typing in hello in an xterm window it displays as >=20 > h e l l o It could do that if the font-metrics say it's that wide, even if (almost) none of the glyphs actually say that. =20 > However, if I specify a font with '-fn 10x20' on the xterm invocation I d= on't > get the gratuitous spaces. that's consistent with my remark above. Also, it's possible (I suppose) that the change to use Unicode 10 last spring is aggravating the problem, but I'd have to study an example to see exactly why. =20 > When installing xterm I get the pkg-message.wchar message displayed: >=20 > =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D > You installed xterm with wide chars support. This introduces some limitat= ions > comparing to the plain single chars version: this version of xterm will u= se > UTF-8 charset for selection buffers, breaking 8-bit copy/paste support un= less > you are using UTF-8 or ISO8859-1 locale. If you want 8-bit charset select= ions to > work as before, use "eightBitSelectTypes" XTerm resource setting. >=20 > For further information refer to the SELECT/PASTE section of xterm(1) man= ual > page. > =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D >=20 > So, I attempted to disable wide-character support in xterm by turning off= the > WCHAR option via make config, but it isn't staying off. Rerunning make co= nfig > shows that it's back on again and rebuilding and installing xterm still p= uts > out the warning. >=20 > Anyone know what's going on? What have I missed? Is my problem related to > wide-character support? Any clues on what I can do to fix it? >=20 > Thanks in advance for any help you can provide...sorry for all the questi= ons, > but I'm at a loss at the moment (reading the man page about > eightBitSelectTypes seemed to give some clues, but failed to say where to > specify it that I could find). that's not related :-) --=20 Thomas E. Dickey <dickey@invisible-island.net> https://invisible-island.net ftp://ftp.invisible-island.net --YiEDa0DAkWCtVeE4 Content-Type: application/pgp-signature; name="signature.asc" Content-Description: Digital signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1 iEYEARECAAYFAlqudkMACgkQcCNT4PfkjtvhlQCg1KRVcdsNSvXF5a5PENEHURox fJcAniUm+srPmLd9XWSLq5NAkEieE64I =kLCK -----END PGP SIGNATURE----- --YiEDa0DAkWCtVeE4--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20180318142259.GA5224>