unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Aura Kelloniemi <kaura.dev@sange.fi>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 50865@debbugs.gnu.org
Subject: bug#50865: 28.0.50; Emoji with emoji modifier in Linux console garbles emacs display
Date: Tue, 28 Sep 2021 23:32:53 +0300	[thread overview]
Message-ID: <87a6jw8mq2.fsf@sange.fi> (raw)
In-Reply-To: <8335pok0pv.fsf@gnu.org>

On 2021-09-28 at 21:35 +0300, Eli Zaretskii <eliz@gnu.org> wrote:
 > That should not be that way.  Some characters are double-width, and
 > should take up 2 columns on display.

I noticed, that Linux console does not understand most of the zero-width
characters either. It happily prints most of the code points in the list of
zero-width characters. Of course they are printed just as diamonds, because
Linux cannot store enough glyphs in its 512-glyph font space, but anyway it
prints a diamond for such characters as <COMBINING GRAVE ACCENT>.

The character range \y200B-\u200F seems to be an exception here. When I try to
print one of these characters on a Linxu VT, it really prints nothing.

When I insert zero-width characters in Emacs, the diamonds representing the
characters are printed interspersed by the padding spaces added by emacs. The
cursor is left behind the extending line of characters as a type, because
Emacs thinks, that the zero-width characters really do not print anything,
even though they do.

I believe that the one viable solution is to make char-width-table a terminal
local variable, so that there can be a simplified version for terminals that
don't understand Unicode correctly.

-- 
Aura





  parent reply	other threads:[~2021-09-28 20:32 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-09-28 14:11 bug#50865: 28.0.50; Emoji with emoji modifier in Linux console garbles emacs display Aura Kelloniemi
2021-09-28 16:12 ` Eli Zaretskii
2021-09-28 16:54   ` Aura Kelloniemi
2021-09-28 17:21     ` Eli Zaretskii
2021-09-28 17:41       ` Aura Kelloniemi
2021-09-28 18:35         ` Eli Zaretskii
2021-09-28 19:20           ` Aura Kelloniemi
2021-09-28 20:32           ` Aura Kelloniemi [this message]
2021-09-29 13:00             ` Eli Zaretskii
2021-10-01 13:23               ` Aura Kelloniemi
2021-10-01 13:35                 ` Eli Zaretskii
2021-10-01 14:33                   ` Aura Kelloniemi
2021-10-01 15:41                     ` Eli Zaretskii
2021-10-01 16:02                       ` Aura Kelloniemi
2021-10-01 17:48                         ` Eli Zaretskii
2021-10-02 10:58                           ` Eli Zaretskii
2021-10-02 11:21                             ` Andreas Schwab
2021-10-02 11:56                               ` Eli Zaretskii
2021-10-04 12:25                             ` Aura Kelloniemi
2021-10-04 13:15                               ` Eli Zaretskii
2021-10-04 16:35                                 ` Eli Zaretskii
2021-10-04 16:51                                   ` Aura Kelloniemi
2021-10-04 17:06                                     ` Eli Zaretskii
2022-09-02 12:08                                       ` Lars Ingebrigtsen
2022-09-02 12:31                                         ` Gregory Heytings
2022-09-02 12:59                                         ` Eli Zaretskii
2022-09-02 13:19                                           ` Gregory Heytings
2021-10-02  8:11                       ` Lars Ingebrigtsen
2021-10-02  8:54                         ` 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

  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=87a6jw8mq2.fsf@sange.fi \
    --to=kaura.dev@sange.fi \
    --cc=50865@debbugs.gnu.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).