zsh-workers
 help / color / mirror / code / Atom feed
From: Bart Schaefer <schaefer@brasslantern.com>
To: Mikael Magnusson <mikachu@gmail.com>
Cc: Alexandre ZANNI <alexandre@acceis.fr>, zsh-workers@zsh.org
Subject: Re: Unicode ZWJ sequence
Date: Sat, 19 Aug 2023 10:07:52 -0700	[thread overview]
Message-ID: <CAH+w=7YX1xGeyuS0g7CDWYWz9XU_SOjbfm6t=4zRhE1pHb6-ew@mail.gmail.com> (raw)
In-Reply-To: <CAHYJk3S1Oa_9eFPhdWM-ma+F9=485XqMO7iRHr8L4Z7hMNWKpA@mail.gmail.com>

On Sat, Aug 19, 2023 at 9:46 AM Mikael Magnusson <mikachu@gmail.com> wrote:
>
> Well, I wasn't even really talking about zsh specifically, but I
> suppose if you don't care where any text ends up on the screen then
> yes, you can display them.

In this case he's got a terminal emulator that is able to display the
grapheme, and in fact as the output of "echo" it works fine, it's only
on the command line that zsh is behaving differently -- and that's
because zle understands the potential problems you described and does
what it can to avoid them.

> That said, if you want randomly corrupted listings you can setopt
> combiningchars and zsh will output even ZWJ directly to the terminal.

It doesn't, though -- even with combiningchars you don't get the
joins, you just get the red heart:

% echo "👩<200d>❤<fe0f><200d>👨"
👩‍❤️‍👨
% setopt combiningchars
% echo "👩<200d>❤️<200d>👨"
👩‍❤️‍👨
%

> (I have a vague memory I argued against this at some point in the past

I think you may have prevailed.

I any event we're not talking about output in the stdout sense here,
we're talking about what zle has in the editor buffer after it gets
terminal input.


  reply	other threads:[~2023-08-19 17:08 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-08-18 13:02 Alexandre ZANNI
2023-08-18 15:24 ` Mikael Magnusson
2023-08-19 16:16   ` Bart Schaefer
2023-08-19 16:46     ` Mikael Magnusson
2023-08-19 17:07       ` Bart Schaefer [this message]
2023-08-19 17:11         ` Bart Schaefer
2023-08-19 15:53 ` Roman Perepelitsa
2023-08-19 17:11   ` Wesley Schwengle
2023-08-20  0:06     ` maxbeckie
2023-08-20  0:13       ` Lawrence Velázquez

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='CAH+w=7YX1xGeyuS0g7CDWYWz9XU_SOjbfm6t=4zRhE1pHb6-ew@mail.gmail.com' \
    --to=schaefer@brasslantern.com \
    --cc=alexandre@acceis.fr \
    --cc=mikachu@gmail.com \
    --cc=zsh-workers@zsh.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.vuxu.org/mirror/zsh/

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 NNTP newsgroup(s).