help / color / mirror / code / Atom feed
From: Oliver Kiddle <opk@zsh.org>
To: Zsh hackers list <zsh-workers@zsh.org>
Subject: Re: read -d $'\200' doesn't work with set +o multibyte (and [PATCH])
Date: Thu, 15 Dec 2022 03:01:33 +0100	[thread overview]
Message-ID: <55635-1671069693.668786@bPS-.5Kzj.qxen> (raw)
In-Reply-To: <20221210090626.mkv7bxeqnap6awah@chazelas.org>

On 10 Dec, Stephane Chazelas wrote:
> Is a requirement on the *application*, not the implementation.
> That is, it only specifies what's meant to happen when the input
> doesn't contain NULs.
> So I think we're good here.

Ok, good. I'm afraid I'm not very good at interpreting the specific
language used in those standards.

> I'm susbscribed to both austin-group-l and zsh-workers but don't
> follow them very closely. I try to mention things relevant to
> zsh here when I spot them on austin-group-l and I try to argue
> there about things that would conflict with the zsh way for no
> good reason.

Thanks for passing such things on. I did subscribe some time ago but
time is limited and it didn't spark joy so I unsubscribed. I still have
a login for the site at least.

> GB18030 and BIG5/BIG5-HKSCS may still be relevant. They don't
> work on Shift state like Shift-JIS, but many of their characters
> have bytes <= 0x7f, and zsh doesn't really work with them for
> that reason.

Thanks for the answer.


      parent reply	other threads:[~2022-12-15  2:05 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-12-09 15:42 read -d $'\200' doesn't work with set +o multibyte Stephane Chazelas
2022-12-09 20:05 ` Oliver Kiddle
2022-12-10  9:06   ` read -d $'\200' doesn't work with set +o multibyte (and [PATCH]) Stephane Chazelas
2022-12-13 11:12     ` Jun T
2022-12-14 21:42       ` Oliver Kiddle
2022-12-15 12:37         ` Jun. T
2022-12-16  8:29           ` Oliver Kiddle
2022-12-18 10:51             ` Jun. T
2022-12-18 17:58               ` Stephane Chazelas
2022-12-15  2:01     ` Oliver Kiddle [this message]

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:

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

  git send-email \
    --in-reply-to=55635-1671069693.668786@bPS-.5Kzj.qxen \
    --to=opk@zsh.org \
    --cc=zsh-workers@zsh.org \


* 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


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).