all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Yixuan Chen <xuan@xlk.me>
To: Eli Zaretskii <eliz@gnu.org>
Cc: luangruo@yahoo.com, 73752@debbugs.gnu.org, visuweshm@gmail.com
Subject: bug#73752: 29.4; Ligatures are randomly rendered with extra spaces
Date: Mon, 28 Oct 2024 10:44:23 -0400	[thread overview]
Message-ID: <1e871a38-a150-4198-a53a-831b9576df8b@xlk.me> (raw)
In-Reply-To: <86jzds719m.fsf@gnu.org>

[-- Attachment #1: Type: text/plain, Size: 2126 bytes --]



On 10/28/24 10:25, Eli Zaretskii wrote:
>> Date: Sun, 27 Oct 2024 16:32:34 -0400
>> Cc: visuweshm@gmail.com, luangruo@yahoo.com, 73752@debbugs.gnu.org
>> From: Yixuan Chen <xuan@xlk.me>
>>
>> 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?

Maybe my use of words were terrible. The problem I want to report was 
never about indentation. It was always about the "extra space between 
the ligature and the following character" (and sometimes also some extra 
space between the ligature and the character, although not in this 
instance).

> 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?

It's not a real SPC glyph. It's a single character ▷ (or ligature/glyph 
I should call it? the underlying text is "|||>"). I attached five 
screenshots, where the block cursor is at ", |, |, |, >, " respectively. 
Noticeably, the block cursor for the first | character (1_bar.png) is 
extra wide, and the block cursors for the following characters looks 
offset from where they are.

[-- Attachment #2: 0_quote.png --]
[-- Type: image/png, Size: 1816 bytes --]

[-- Attachment #3: 1_bar.png --]
[-- Type: image/png, Size: 1607 bytes --]

[-- Attachment #4: 2_bar.png --]
[-- Type: image/png, Size: 1597 bytes --]

[-- Attachment #5: 3_bar.png --]
[-- Type: image/png, Size: 1352 bytes --]

[-- Attachment #6: 4_gt.png --]
[-- Type: image/png, Size: 1454 bytes --]

[-- Attachment #7: 5_quote.png --]
[-- Type: image/png, Size: 1364 bytes --]

  reply	other threads:[~2024-10-28 14:44 UTC|newest]

Thread overview: 50+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-10-11 16:18 bug#73752: 29.4; Ligatures are randomly rendered with extra spaces xuan
2024-10-12  8:02 ` Eli Zaretskii
2024-10-12 16:09   ` Yixuan Chen
2024-10-27 10:21     ` Eli Zaretskii
2024-10-27 16:19       ` Visuwesh
2024-10-27 17:19         ` Eli Zaretskii
2024-10-27 17:27           ` Eli Zaretskii
2024-10-27 17:39             ` Yixuan Chen
2024-10-27 17:43               ` Eli Zaretskii
2024-10-27 17:46                 ` Yixuan Chen
2024-10-27 19:14                   ` Eli Zaretskii
2024-10-27 19:36                     ` Yixuan Chen
2024-10-27 19:44                       ` Eli Zaretskii
2024-10-27 19:47                         ` Yixuan Chen
2024-10-27 20:11                           ` Eli Zaretskii
2024-10-27 19:41                     ` Yixuan Chen
2024-10-27 20:07                       ` Eli Zaretskii
2024-10-27 20:32                         ` Yixuan Chen
2024-10-28 14:25                           ` Eli Zaretskii
2024-10-28 14:44                             ` Yixuan Chen [this message]
2024-10-28 14:47                               ` Yixuan Chen
2024-10-28 15:05                               ` Eli Zaretskii
2024-10-28 15:20                                 ` Yixuan Chen
2024-10-28 17:19                                   ` Eli Zaretskii
2024-10-28 17:26                                     ` Eli Zaretskii
2024-10-28 17:28                                     ` Yixuan Chen
2024-10-28 18:41                                       ` Eli Zaretskii
2024-10-28  4:26             ` Visuwesh
2024-10-28 14:59               ` Eli Zaretskii
2024-10-28 15:24                 ` Yixuan Chen
2024-10-28 16:18                 ` Visuwesh
2024-10-28 17:13                   ` Eli Zaretskii
2024-10-29 10:59                     ` Visuwesh
2024-10-29 13:04                       ` Eli Zaretskii
2024-10-29 13:54                         ` Visuwesh
2024-10-29 14:00                           ` Visuwesh
2024-10-29 15:38                           ` Eli Zaretskii
2024-10-29 16:46                             ` Visuwesh
2024-10-29 17:45                               ` Eli Zaretskii
2024-10-30  5:43                                 ` Visuwesh
2024-10-29 16:51                             ` Eli Zaretskii
2024-10-27 17:29           ` Yixuan Chen
2024-10-29 23:14 ` Tim Ruffing
2024-10-30 15:12   ` Eli Zaretskii
2024-10-30 15:45     ` Eli Zaretskii
     [not found]     ` <mvmikt9zkcq.fsf@suse.de>
2024-10-30 15:47       ` Eli Zaretskii
2024-10-30 17:34         ` Tim Ruffing
2024-10-30 17:46           ` Eli Zaretskii
2024-10-30 18:00             ` Tim Ruffing
2024-10-30 18:57               ` Eli Zaretskii

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1e871a38-a150-4198-a53a-831b9576df8b@xlk.me \
    --to=xuan@xlk.me \
    --cc=73752@debbugs.gnu.org \
    --cc=eliz@gnu.org \
    --cc=luangruo@yahoo.com \
    --cc=visuweshm@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.