From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Yixuan Chen Newsgroups: gmane.emacs.bugs Subject: bug#73752: 29.4; Ligatures are randomly rendered with extra spaces Date: Wed, 30 Oct 2024 22:36:59 -0400 Message-ID: <135b8c1a-5f0f-4144-b3b0-71c4f28572bc@xlk.me> References: <91cb4d5a6c979bf096ca9fa26711395ab29b941b.camel@timruffing.de> <86wmhp4obi.fsf@gnu.org> <86msil4mpn.fsf@gnu.org> <8f02b0490d2abb0889b760fb80c3ec492c63c784.camel@timruffing.de> <86ed3x4h7m.fsf@gnu.org> <86cyjh4dx5.fsf@gnu.org> <68b51105125b6c7a34ec8c2032588ce72d8557bc.camel@timruffing.de> Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="35610"; mail-complaints-to="usenet@ciao.gmane.io" User-Agent: Mozilla Thunderbird Cc: 73752@debbugs.gnu.org, visuweshm@gmail.com To: Tim Ruffing , Eli Zaretskii Original-X-From: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane-mx.org@gnu.org Thu Oct 31 06:23:46 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 1t6Nes-000979-0V for geb-bug-gnu-emacs@m.gmane-mx.org; Thu, 31 Oct 2024 06:23:46 +0100 Original-Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1t6NeD-00063I-Se; Thu, 31 Oct 2024 01:23:05 -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 1t6NeA-00062m-TU for bug-gnu-emacs@gnu.org; Thu, 31 Oct 2024 01:23:04 -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 1t6NeA-0003TA-Ks for bug-gnu-emacs@gnu.org; Thu, 31 Oct 2024 01:23:02 -0400 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=debbugs.gnu.org; s=debbugs-gnu-org; h=In-Reply-To:From:References:MIME-Version:Date:To:Subject; bh=X3IOTwv2M21NS5QtYquezT1ZRNgM3g6853ocwzAgl+o=; b=irrLf0BaRePZ8X8csCQv5CLv8mFcadMzJxl4HJoFIiZappjzhn8I6KIHAird4DVPMmjrRV0naWBFGY0V8qRIVlqEZd0JrzD2RwkpogMfX/55F3ulrRnk0HbYAMhiJlxjAdmxKxJo2c+m+WhrYdiqvoNHojbshjJ0mkxN9E3Xz/9Mus7qD2K6deXPobOPXpUtp/SQbeLRIgMlpUBKWmf/b4uNRnLqABiwv4l9cSlkH/7AN2M/LZfgtYW/+u4GUH1uZD1AVKryn/KrQ5de6sxqY+8NAbf6wgS5n8HhBo+y9cPNtd84dMYbQmVCY1PgnZQJ/6TdltDkGt0MbOyeWNxCTw==; Original-Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1t6NeA-0000wq-81 for bug-gnu-emacs@gnu.org; Thu, 31 Oct 2024 01:23:02 -0400 X-Loop: help-debbugs@gnu.org Resent-From: Yixuan Chen Original-Sender: "Debbugs-submit" Resent-CC: bug-gnu-emacs@gnu.org Resent-Date: Thu, 31 Oct 2024 05:23: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.17303521313588 (code B ref 73752); Thu, 31 Oct 2024 05:23:02 +0000 Original-Received: (at 73752) by debbugs.gnu.org; 31 Oct 2024 05:22:11 +0000 Original-Received: from localhost ([127.0.0.1]:39858 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1t6NdL-0000vl-1r for submit@debbugs.gnu.org; Thu, 31 Oct 2024 01:22:11 -0400 Original-Received: from qs51p00im-qukt01071501.me.com ([17.57.155.4]:21113) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1t6L3c-0003LO-IX for 73752@debbugs.gnu.org; Wed, 30 Oct 2024 22:37:11 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=xlk.me; s=sig1; t=1730342223; bh=X3IOTwv2M21NS5QtYquezT1ZRNgM3g6853ocwzAgl+o=; h=Message-ID:Date:MIME-Version:Subject:To:From:Content-Type: x-icloud-hme; b=E4vOSLp/jqQotOiIXtrr4sK9hprpZloj5njqkeuZcQN11fjvvOf7Mgu4cf8Os4xtX WlKnTVWjBLoDiNLVeZIN8vYkmeiHqq9+AFObJOi7ly6g56qO8VQgjMge5/Fx5b5Lpz EmyG03sptvqD1olIK+PiC/qGwj9joFfQS0yFH0jUTu4wE47m/jBU119rh7FoA8uq0S gpSDh3yhlGfms38g9qZpSF771qt1uhxeFiTNEQSx5VO7vD+FLzgnEZnPr60fNETHdU e6XVvOngT2xtch22XadA+YiNj49NFEoQoUSym+vsJHL4DMQSoNqEfKqd/noiGMUnMn hrz8jUNNqbZdg== Original-Received: from [192.168.1.14] (qs51p00im-dlb-asmtp-mailmevip.me.com [17.57.155.28]) by qs51p00im-qukt01071501.me.com (Postfix) with ESMTPSA id 9472E1C40302; Thu, 31 Oct 2024 02:37:01 +0000 (UTC) Content-Language: en-US In-Reply-To: <68b51105125b6c7a34ec8c2032588ce72d8557bc.camel@timruffing.de> X-Proofpoint-ORIG-GUID: OtX1UNygErTwtxl4RaWroIzV7OqrYgxe X-Proofpoint-GUID: OtX1UNygErTwtxl4RaWroIzV7OqrYgxe X-Proofpoint-Virus-Version: vendor=baseguard engine=ICAP:2.0.272,Aquarius:18.0.1051,Hydra:6.0.680,FMLib:17.12.62.30 definitions=2024-10-30_14,2024-10-30_01,2024-09-30_01 X-Proofpoint-Spam-Details: rule=notspam policy=default score=0 mlxscore=0 mlxlogscore=576 malwarescore=0 bulkscore=0 suspectscore=0 adultscore=0 phishscore=0 clxscore=1030 spamscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.19.0-2308100000 definitions=main-2410310020 X-Mailman-Approved-At: Thu, 31 Oct 2024 01:22:10 -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:294591 Archived-At: On 10/30/24 21:39, Tim Ruffing wrote: > I'm not sure if I have the time to verify this in the coming days, I'd > appreciate if some of the other affected users could give it a try. I'm sorry I wasn't following this thread closely for the last few days. I'm currently busy with a submission due in two weeks so I don't have continuous time to investigate the problem using GDB before Nov. 14. > I can't recall that it ever flipped suddenly from good to > bad *when the affected ligatures was in the visible array of the > buffer*. But I'm not so sure if this has really never flipped from good > to bad during a session, when the ligature was not visible. I'm pretty certain it doesn't happen to a line spontaneously. I usually encounter this behavior (with a probability) when 1. after a font changes, like what the script I submitted did. 2. after switching to a different buffer, even if both buffers contains ligatures and uses the same font/fontset setting (though maybe one of the buffers contains certain characters with bold/italic/etc font attributes, I don't recall it exactly). 3. (maybe) after scrolling down/up the buffer into a position where a line contains ligatures appears. Best, Yixuan