all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Rudi C <rudiwillalwaysloveyou@gmail.com>
Cc: 50983@debbugs.gnu.org, alan@idiocy.org
Subject: bug#50983: 28.0.50; [REGRESSION, BUG] Display bugs with uncommon characters
Date: Mon, 04 Oct 2021 15:40:05 +0300	[thread overview]
Message-ID: <83h7dx6k0q.fsf@gnu.org> (raw)
In-Reply-To: <CAE9z9A1zV5dBmC7QExSc_F+1g04QNKZ8jd7MQj_MwuC7hqBpcw@mail.gmail.com> (message from Rudi C on Mon, 4 Oct 2021 11:35:41 +0330)

> From: Rudi C <rudiwillalwaysloveyou@gmail.com>
> Date: Mon, 4 Oct 2021 11:35:41 +0330
> Cc: Alan Third <alan@idiocy.org>, 50983@debbugs.gnu.org
> 
> But the problem does not happen with vim (nor with emacs 27 for `weird.txt`), so it is clearly an interaction
> of different elements. 
> 
> Anyhow, I have opened an [upstream issue](https://github.com/kovidgoyal/kitty/issues/4094). Please
> subscribe to it so that you might offer your emacs expertise there, if needed.

I subscribed and posted the following comment:

Emacs uses character width tables computed from the latest Unicode
Standard version 14.0.0, using the data in the file
EastAsianWidth.txt.  In that text, the U+00AD SOFT HYPHEN character,
which caused the problems in your file, has the East Asian Width
property value of A, which stands for "Ambiguous".  The definition of
this value in the Unicode Standard Annex 11 (UAX#11) is as follows:

  East Asian Ambiguous (A): All characters that can be sometimes wide
  and sometimes narrow. Ambiguous characters require additional
  information not contained in the character code to further resolve
  their width.

    Ambiguous characters occur in East Asian legacy character sets as
    wide characters, but as narrow (i.e., normal-width) characters in
    non-East Asian usage.

And since the file you show didn't have any East Asian legacy
characters, treating SOFT HYPHEN as narrow is IMO correct.

> > changing the "character encoding" setting in iTerm to ASCII
> 
> This is a most loath workaround. I do want UTF-8, as I use mathematical symbols, emojis, and non-English
> languages. Anyhow, making the text full of random unrecognized characters is not much better than the
> current behavior.

It is better because it doesn't confuse the user regarding which
character is he or she editing.

But I agree with you that the results are hardly satisfactory, so my
recommendation is not to use Kitty in conjunction with Emacs.





  reply	other threads:[~2021-10-04 12:40 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-10-02 22:50 bug#50983: 28.0.50; [REGRESSION, BUG] Display bugs with uncommon characters Rudi C
2021-10-03  5:51 ` Eli Zaretskii
2021-10-03  6:47   ` Rudi C
2021-10-03  9:01     ` Eli Zaretskii
2021-10-03  9:11   ` Lars Ingebrigtsen
2021-10-03  9:54   ` Alan Third
2021-10-03 10:04     ` Eli Zaretskii
2021-10-03 10:24       ` Alan Third
2021-10-03 10:49         ` Eli Zaretskii
2021-10-03 11:26           ` Alan Third
2021-10-03 12:02             ` Eli Zaretskii
2021-10-03 12:54               ` Alan Third
2021-10-03 14:48                 ` Eli Zaretskii
2021-10-03 11:00         ` Rudi C
2021-10-03 11:11           ` Eli Zaretskii
2021-10-04  8:05             ` Rudi C
2021-10-04 12:40               ` Eli Zaretskii [this message]
2021-10-04 13:50                 ` Eli Zaretskii
2022-09-04 21:37                   ` Lars Ingebrigtsen
2021-10-03  9:08 ` Lars Ingebrigtsen
2021-10-03 10:48   ` Rudi C

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=83h7dx6k0q.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=50983@debbugs.gnu.org \
    --cc=alan@idiocy.org \
    --cc=rudiwillalwaysloveyou@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.