From: Rudi C <rudiwillalwaysloveyou@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 50983@debbugs.gnu.org, Alan Third <alan@idiocy.org>
Subject: bug#50983: 28.0.50; [REGRESSION, BUG] Display bugs with uncommon characters
Date: Mon, 4 Oct 2021 11:35:41 +0330 [thread overview]
Message-ID: <CAE9z9A1zV5dBmC7QExSc_F+1g04QNKZ8jd7MQj_MwuC7hqBpcw@mail.gmail.com> (raw)
In-Reply-To: <83wnmu8irr.fsf@gnu.org>
[-- Attachment #1: Type: text/plain, Size: 1341 bytes --]
> I see no Emacs problem here
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.
> 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.
On Sun, Oct 3, 2021 at 2:42 PM Eli Zaretskii <eliz@gnu.org> wrote:
> > From: Rudi C <rudiwillalwaysloveyou@gmail.com>
> > Date: Sun, 3 Oct 2021 14:30:56 +0330
> >
> > Also, can you be more specific about where you do observe the bugs? In
> TUI emacs on iTerm?
> >
> > I can confirm that the bug with `weird.txt` happens on iTerm, too, again
> with both emacs and neovim! But the
> > bug with `bug.txt` does not happen in iTerm, only on Kitty.
>
> This sounds like the terminal emulators have a problem in supporting
> unusual Unicode characters, such as zero-width or double-width
> characters, perhaps? I see no Emacs problem here, since it happens
> only on some terminal emulators and not on others.
>
[-- Attachment #2: Type: text/html, Size: 1916 bytes --]
next prev parent reply other threads:[~2021-10-04 8:05 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 [this message]
2021-10-04 12:40 ` Eli Zaretskii
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAE9z9A1zV5dBmC7QExSc_F+1g04QNKZ8jd7MQj_MwuC7hqBpcw@mail.gmail.com \
--to=rudiwillalwaysloveyou@gmail.com \
--cc=50983@debbugs.gnu.org \
--cc=alan@idiocy.org \
--cc=eliz@gnu.org \
/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 public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).