From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!.POSTED!not-for-mail From: Eli Zaretskii Newsgroups: gmane.emacs.devel,gmane.mail.mu.general Subject: Re: Bug in Unicode character width in Emacs 25.1, bisected to a761fbf (Unicode 9.0.0beta import) Date: Mon, 19 Sep 2016 19:34:07 +0300 Message-ID: <831t0fj1c0.fsf@gnu.org> References: Reply-To: Eli Zaretskii NNTP-Posting-Host: blaine.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit X-Trace: blaine.gmane.org 1474302917 32599 195.159.176.226 (19 Sep 2016 16:35:17 GMT) X-Complaints-To: usenet@blaine.gmane.org NNTP-Posting-Date: Mon, 19 Sep 2016 16:35:17 +0000 (UTC) Cc: mu-discuss@googlegroups.com, emacs-devel@gnu.org To: =?utf-8?B?w4Z2YXIgQXJuZmrDtnLDsA==?= Bjarmason Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Mon Sep 19 18:35:11 2016 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([208.118.235.17]) by blaine.gmane.org with esmtp (Exim 4.84_2) (envelope-from ) id 1bm1XC-0007yY-O9 for ged-emacs-devel@m.gmane.org; Mon, 19 Sep 2016 18:35:10 +0200 Original-Received: from localhost ([::1]:56747 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1bm1XA-0001zG-Qk for ged-emacs-devel@m.gmane.org; Mon, 19 Sep 2016 12:35:08 -0400 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:36395) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1bm1Wd-0001z8-57 for emacs-devel@gnu.org; Mon, 19 Sep 2016 12:34:36 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1bm1WY-0003c1-EE for emacs-devel@gnu.org; Mon, 19 Sep 2016 12:34:34 -0400 Original-Received: from fencepost.gnu.org ([2001:4830:134:3::e]:48177) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1bm1W9-0003S1-HE; Mon, 19 Sep 2016 12:34:05 -0400 Original-Received: from 84.94.185.246.cable.012.net.il ([84.94.185.246]:1314 helo=home-c4e4a596f7) by fencepost.gnu.org with esmtpsa (TLS1.2:RSA_AES_128_CBC_SHA1:128) (Exim 4.82) (envelope-from ) id 1bm1W5-0003vf-I8; Mon, 19 Sep 2016 12:34:04 -0400 In-reply-to: (message from =?utf-8?B?w4Z2YXIgQXJuZmrDtnLDsA==?= Bjarmason on Sun, 18 Sep 2016 20:52:44 +0200) X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.2.x-3.x [generic] X-Received-From: 2001:4830:134:3::e X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Original-Sender: "Emacs-devel" Xref: news.gmane.org gmane.emacs.devel:207612 gmane.mail.mu.general:4043 Archived-At: > From: Ævar Arnfjörð Bjarmason > Date: Sun, 18 Sep 2016 20:52:44 +0200 > Cc: mu-discuss@googlegroups.com, Eli Zaretskii > > [I'm sending this to the ML instead of bug-* because I figure a bug > caused by the Unicode 9 import will garner some wider interest than > your typical regression] IMO, that was a mistake. Bugs should be reported to the bug tracker, and all those who might be interested are reading the bug mailing list anyway. Reporting a bug with "M-x report-emacs-bug" has the advantage of including in the report important details about your system configuration that might be relevant to the issue. > The mu4e mode has a mu4e-use-fancy-chars option which if set will use > e.g. ⚓ (Unicode ANCHOR; U+2693) instead of "a" in the vertically > aligned headers view to show that an E-Mail has an attachment. > > In Emacs 25.1 this vertical alignment is off consistent with ⚓ being > considered a zero-width character, i.e. the content to the right-hand > side of the ⚓ character is shifted 1 character to the left. This character's width is 2, not zero: (char-width ?⚓) => 2 > I'm sorry that I don't have a more isolated test case than "run mu4e, > turn on mu4e-use-fancy-chars and check out the misalignment in the > header view" but I figure with the bisect + my successfully testing a > revert of a761fbf on top of emacs-25.1 we have enough info to get > started in narrowing this down. Unfortunately, this description is not enough. And since it is unlikely we'll decide to revert that commit, we need more information to understand what code (or font?) is the culprit and how to fix that. For starters, I don't yet have a clear idea of what display problems are caused by that character; a screenshot would help. The results of "C-u C-x =" with point on the anchor character would also be of value. Finally, does selecting a different font for this character fix the problem? Thanks.