From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Lars Ingebrigtsen Newsgroups: gmane.emacs.bugs Subject: bug#27403: 26.0.50; Indentation misalignment with Unicode code points >65535 Date: Sat, 05 Feb 2022 07:40:10 +0100 Message-ID: <87y22perzp.fsf@gnus.org> References: <5bd704e4-b3e4-bcd3-eea6-66856fc47dd6@gmail.com> <83tw3fyr7k.fsf@gnu.org> <83shiyzz5y.fsf@gnu.org> <8737ayolx3.fsf@linux-m68k.org> <83poe2zqae.fsf@gnu.org> <87wp8amqrn.fsf@linux-m68k.org> <83fueyzd8w.fsf@gnu.org> <875ypvn1eo.fsf@gnus.org> <831r0j3ycz.fsf@gnu.org> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="3786"; mail-complaints-to="usenet@ciao.gmane.io" User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/29.0.50 (gnu/linux) Cc: 27403@debbugs.gnu.org, schwab@linux-m68k.org, adam.niederer@gmail.com To: Eli Zaretskii Original-X-From: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane-mx.org@gnu.org Sat Feb 05 07:42:45 2022 Return-path: Envelope-to: geb-bug-gnu-emacs@m.gmane-mx.org Original-Received: from lists.gnu.org ([209.51.188.17]) by ciao.gmane.io with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1nGEmS-0000lK-IY for geb-bug-gnu-emacs@m.gmane-mx.org; Sat, 05 Feb 2022 07:42:44 +0100 Original-Received: from localhost ([::1]:48330 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1nGEmR-0006sx-1O for geb-bug-gnu-emacs@m.gmane-mx.org; Sat, 05 Feb 2022 01:42:43 -0500 Original-Received: from eggs.gnu.org ([209.51.188.92]:47516) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1nGEkq-0006ra-N7 for bug-gnu-emacs@gnu.org; Sat, 05 Feb 2022 01:41:04 -0500 Original-Received: from debbugs.gnu.org ([209.51.188.43]:39609) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.90_1) (envelope-from ) id 1nGEkn-0007Hb-VO for bug-gnu-emacs@gnu.org; Sat, 05 Feb 2022 01:41:03 -0500 Original-Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1nGEkn-0005oV-Ou for bug-gnu-emacs@gnu.org; Sat, 05 Feb 2022 01:41:01 -0500 X-Loop: help-debbugs@gnu.org Resent-From: Lars Ingebrigtsen Original-Sender: "Debbugs-submit" Resent-CC: bug-gnu-emacs@gnu.org Resent-Date: Sat, 05 Feb 2022 06:41:01 +0000 Resent-Message-ID: Resent-Sender: help-debbugs@gnu.org X-GNU-PR-Message: followup 27403 X-GNU-PR-Package: emacs Original-Received: via spool by 27403-submit@debbugs.gnu.org id=B27403.164404322622298 (code B ref 27403); Sat, 05 Feb 2022 06:41:01 +0000 Original-Received: (at 27403) by debbugs.gnu.org; 5 Feb 2022 06:40:26 +0000 Original-Received: from localhost ([127.0.0.1]:33506 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1nGEkE-0005nZ-MD for submit@debbugs.gnu.org; Sat, 05 Feb 2022 01:40:26 -0500 Original-Received: from quimby.gnus.org ([95.216.78.240]:42066) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1nGEkB-0005nH-Km for 27403@debbugs.gnu.org; Sat, 05 Feb 2022 01:40:24 -0500 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=gnus.org; s=20200322; h=Content-Transfer-Encoding:Content-Type:MIME-Version:Message-ID :In-Reply-To:Date:References:Subject:Cc:To:From:Sender:Reply-To:Content-ID: Content-Description:Resent-Date:Resent-From:Resent-Sender:Resent-To:Resent-Cc :Resent-Message-ID:List-Id:List-Help:List-Unsubscribe:List-Subscribe: List-Post:List-Owner:List-Archive; bh=Gj1jpzUxT+xV3LfBb8EH+x13U+PVJz9d+xz88phxo/I=; b=uObazOwBQ9if7AgZoJjnK5hdmu bJ96NbOJ2dphYD2XH8cVdP6Uf8PJduRrw7TvhshrABUP9t/gO/aseSmXvBIR9Fs78FflaJcKqCl/d le7etPGhiXHDoTPmaLGxuraKx0pBmjbHnW2B4jxtxPuD24e4vY2QNowdmhFkui/5MkL4=; Original-Received: from [84.212.220.105] (helo=giant) by quimby.gnus.org with esmtpsa (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1nGEk1-0005A1-Oq; Sat, 05 Feb 2022 07:40:16 +0100 Face: iVBORw0KGgoAAAANSUhEUgAAADAAAAAwBAMAAAClLOS0AAAABGdBTUEAALGPC/xhBQAAACBj SFJNAAB6JgAAgIQAAPoAAACA6AAAdTAAAOpgAAA6mAAAF3CculE8AAAAG1BMVEX9/f3RpKvivsFE HyegVGKwkpbp0tO6eoL////k9b6kAAAAAWJLR0QIht6VegAAAAd0SU1FB+YCBQYaG38SvugAAAGr SURBVDjLbZTBcpswEIZlT1GuXaXEVyTXzrUz0PZaBlGuVo3cK9B4fS0JDq9fCZxmkLQzoJn9dtn9 dwcR8marbSo/Et/WRWosQO6tP/1KsUGKiO8fSmdL3IQ/xinN88UFpkJmMzK39C0hTZsliIyrmPo6 BEAaaJiaCjLYVpFlc79uV0c5FFKWLz4omeYjHzxwX+1y/toFQPkpB2xlANR9YoEjkGyrzch78MGT rOQoZZ+5YC3TGh5LXnqLklfJG3LxVwifK57QjQ8uddwm3csPD9xVLSAPgA/5HjsYfnpgm8cAsfzm gSIfxn5z9MDq+waYeD4eXECT6ITtQ018YwrivfL9q54D63yBVCshRAfKHWKsNBOCM86W8bGKlQUo OrZ/97f6qvUE2E4B/E+KRqWHq2Kd0PGgEHenGxi0ZibDzOokkO878XvuICq1gisT5j+CBgUSep71 P2kAzdBa20yx7Tzj+hfyB0fsdJSuJqPWvtf+bsijjY0OPjjbkUWBSa9s8DkA1ha0ZklLt1FymI9X 00hjLgpCib0rngm9rWVcFvhLyE3BZaHkbgr/B5RbZYu6CG6kAAAAJXRFWHRkYXRlOmNyZWF0ZQAy MDIyLTAyLTA1VDA2OjI2OjI3KzAwOjAwXjRbPQAAACV0RVh0ZGF0ZTptb2RpZnkAMjAyMi0wMi0w NVQwNjoyNjoyNyswMDowMC9p44EAAAAASUVORK5CYII= X-Now-Playing: David Bowie's _Aladdin Sane_: "Panic In Detroit" In-Reply-To: <831r0j3ycz.fsf@gnu.org> (Eli Zaretskii's message of "Fri, 04 Feb 2022 09:05:48 +0200") X-BeenThere: debbugs-submit@debbugs.gnu.org X-Mailman-Version: 2.1.18 Precedence: list X-BeenThere: bug-gnu-emacs@gnu.org List-Id: "Bug reports for GNU Emacs, the Swiss army knife of text editors" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane-mx.org@gnu.org Original-Sender: "bug-gnu-emacs" Xref: news.gmane.io gmane.emacs.bugs:226033 Archived-At: Eli Zaretskii writes: >> In the fonts I use, it's definitely wide. But so is =E2=98=BA, which is= marked >> as narrow. >>=20 >> So =E2=9D=93 > > I don't see how this can be solved as long as indentation works in > columns. If some font produces a glyph whose width isn't anywhere > close to the Unicode width specifications, what can we do except tell > people not to use those fonts? > > Alternatively, if it turns out that most fonts use different width, we > could amend our char-width table to be consistent with those fonts. Yes, it would be nice if this worked better out-of-the-box for most people, but I wouldn't want to manually maintain a list of typical char widths, either. By the way, =E2=98=BA in the terminal here (Debian/bullseye) does take 1 character while =F0=9F=91=8D takes two, so perhaps they're also using the s= ame Unicode data that we're using... --=20 (domestic pets only, the antidote for overdose, milk.) bloggy blog: http://lars.ingebrigtsen.no