From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Eli Zaretskii Newsgroups: gmane.emacs.bugs Subject: bug#73752: 29.4; Ligatures are randomly rendered with extra spaces Date: Mon, 28 Oct 2024 16:25:25 +0200 Message-ID: <86jzds719m.fsf@gnu.org> References: <86zfn9ycis.fsf@gnu.org> <86o735als7.fsf@gnu.org> <87o73534dn.fsf@gmail.com> <86h68x8nuz.fsf@gnu.org> <86ed418niu.fsf@gnu.org> <6566317e-03bb-4856-9cc8-5e90c2875e44@xlk.me> <86cyjl8mqs.fsf@gnu.org> <86bjz58ik7.fsf@gnu.org> <04c3e9c5-0e18-4c35-8e5d-893c17690e5f@xlk.me> <86y12971jq.fsf@gnu.org> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="28414"; mail-complaints-to="usenet@ciao.gmane.io" Cc: luangruo@yahoo.com, 73752@debbugs.gnu.org, visuweshm@gmail.com To: Yixuan Chen Original-X-From: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane-mx.org@gnu.org Mon Oct 28 15:26:59 2024 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 1t5Qhv-0006oi-1H for geb-bug-gnu-emacs@m.gmane-mx.org; Mon, 28 Oct 2024 15:26:59 +0100 Original-Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1t5QhQ-0006Qi-Jp; Mon, 28 Oct 2024 10:26:28 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1t5QhO-0006QC-Jj for bug-gnu-emacs@gnu.org; Mon, 28 Oct 2024 10:26:26 -0400 Original-Received: from debbugs.gnu.org ([2001:470:142:5::43]) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.90_1) (envelope-from ) id 1t5QhO-0003Ib-BY for bug-gnu-emacs@gnu.org; Mon, 28 Oct 2024 10:26:26 -0400 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=debbugs.gnu.org; s=debbugs-gnu-org; h=MIME-version:References:In-Reply-To:From:Date:To:Subject; bh=AkIG75gf3Lw4dYRE8OntAaTnFkkuJc02xTvWJQzhCBc=; b=VLYcNKoWpZU8mrDahxLk3HXrJI9anPsODUP7Wma15aK5McnuGzoGGn5hN0ETYRl4hXTnw9l1btIW0IeF9sKiVwn2vKvuHsS2leogr3z5mWceAxDdNsKJtrxhAgWrgFRMUlRvHZGAkLjEHJ2IBksA+qxqI/rWW4ecPBFnGHBnhQvQ/ZY2y288DEOafQUGg2vmxXDYCgnf+JyWzRqrbB6Fkhixx95Hm/6S6iPKOinwDBrIQoLpik0bPZpAbWgz1E7R7kdE/ag+TrgiJ81J5daRr3z94snmjF5+vPqRARwXi5xt2gek2bSqq0Tze6wUjuv2RSiefJLoNcdv0/O6KI1aAA==; Original-Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1t5Qhy-0003C2-Gs for bug-gnu-emacs@gnu.org; Mon, 28 Oct 2024 10:27:02 -0400 X-Loop: help-debbugs@gnu.org Resent-From: Eli Zaretskii Original-Sender: "Debbugs-submit" Resent-CC: bug-gnu-emacs@gnu.org Resent-Date: Mon, 28 Oct 2024 14:27:02 +0000 Resent-Message-ID: Resent-Sender: help-debbugs@gnu.org X-GNU-PR-Message: followup 73752 X-GNU-PR-Package: emacs Original-Received: via spool by 73752-submit@debbugs.gnu.org id=B73752.173012557312210 (code B ref 73752); Mon, 28 Oct 2024 14:27:02 +0000 Original-Received: (at 73752) by debbugs.gnu.org; 28 Oct 2024 14:26:13 +0000 Original-Received: from localhost ([127.0.0.1]:54279 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1t5QhB-0003As-0d for submit@debbugs.gnu.org; Mon, 28 Oct 2024 10:26:13 -0400 Original-Received: from eggs.gnu.org ([209.51.188.92]:58382) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1t5Qh8-0003Ac-T3 for 73752@debbugs.gnu.org; Mon, 28 Oct 2024 10:26:12 -0400 Original-Received: from fencepost.gnu.org ([2001:470:142:3::e]) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1t5QgS-0003F4-LV; Mon, 28 Oct 2024 10:25:28 -0400 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=gnu.org; s=fencepost-gnu-org; h=MIME-version:References:Subject:In-Reply-To:To:From: Date; bh=AkIG75gf3Lw4dYRE8OntAaTnFkkuJc02xTvWJQzhCBc=; b=r4L34HpQGwAop4M96jpi KyXra2Io/4Yt1ic9bwbbdzAwnlFWPkMPtBuMZSFucTsy1R9E+ABKqMX5+i9vMEc2PrZwUS757MjgG AUwrXG2QscqqbamjHcStMBXU+WLTqU5LlbfwbDPlURB6WSQPvVqhaDlTzzZLDElBeSQH//uSFHzmq 5cj6eaeEMu4a6lo+YU30inFiEhCSRtmJkPninmgS/KvWdKccihZlAjiG2N25A0aDySi2EBeusF/m8 IeVvgdsz98Lg8jVLyP9PN01+3LbUNkor/eOganOHHlp05CDbqIMB0hgAEMwxB3XmqDVAa6swRlQzL rAK0fMhySG0D0w==; In-Reply-To: (message from Yixuan Chen on Sun, 27 Oct 2024 16:32:34 -0400) 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-bounces+geb-bug-gnu-emacs=m.gmane-mx.org@gnu.org Xref: news.gmane.io gmane.emacs.bugs:294426 Archived-At: > Date: Sun, 27 Oct 2024 16:32:34 -0400 > Cc: visuweshm@gmail.com, luangruo@yahoo.com, 73752@debbugs.gnu.org > From: Yixuan Chen > > On 10/27/24 16:07, Eli Zaretskii wrote: > > To convince me that this is really happening (although I'm unable to > > understand how it could, given how Emacs faces work), you will need to > > show some code which generates such a situation in a reproducible > > manner, and then show me by using "M-x describe-text-properties" and > > "C-u C-x =" that indeed the same characters in the same face are shown > > on different lines with different metrics. > > OK, here you go. Not exactly what I asked for, or understood how the problem manifests itself... > "screenshot1.png" shows the bugged display. Here's the result of > "describe-text-properties", > > There are text properties here: > > face (face12 font-lock-string-face) > > fontified t But this is a completely different issue. There's no indentation here, right? You are saying that in the "bad" display there's some extra space between the ligature and the following quote, right? Is that extra space a real SPC glyph or is it just that the ligature is considered "wider"? What happens if you put the cursor on the ▷ ligature in the "bad" display -- does the block cursor then take up all the space up to the next quote?