zsh-workers
 help / color / mirror / code / Atom feed
From: Sebastian Gniazdowski <sgniazdowski@gmail.com>
To: Peter Stephenson <p.stephenson@samsung.com>,
	Zsh hackers list <zsh-workers@zsh.org>
Subject: Re: [PATCH] [[:blank:]] only matches on SPC and TAB
Date: Thu, 17 May 2018 11:03:46 +0200	[thread overview]
Message-ID: <CAKc7PVAKMBjWF+Bs9bOprH6VCAbxTzaZf4mffJm=eJvdJbRm+Q@mail.gmail.com> (raw)
In-Reply-To: <20180514123425.GA19631@chaz.gmail.com>

On 14 May 2018 at 14:34, Stephane Chazelas <stephane.chazelas@gmail.com> wrote:
> I don't think many people complained when multi-byte support was
> added and English people were starting to have their [[:alpha:]]
> match on Greek or Korean letters in addition to English ones
> (fair enough as "alpha" means the first letter of the Greek
> alphabet).

This is a very interesting point. Think bank-systems. I think no one
ever predicted that control code of deployed programs will be
influenced from outside. The [[:alpha:]] case should find its way to
books on computer science as an example of something unbelievable. The
same as changing libc and fopen() to return NULL also when, say ...,
disk is near-full. I wonder how this compares to y2k situation hehe.
That said, I think that what is hidden behind those "upgrades" of
standard libraries, is a motivation to do a 1-time bungee jump,
risking breaking bones, but hoping to fix past mistakes. The past
(ignoring of non-ascii strings) had to haunt enough people so that
this happened.

> --
> Stephane


  parent reply	other threads:[~2018-05-17  9:04 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-05-13 21:25 Stephane Chazelas
2018-05-13 21:49 ` [PATCH v2] " Stephane Chazelas
2018-05-14  2:27 ` [PATCH] " Sebastian Gniazdowski
2018-05-14  4:41   ` Sebastian Gniazdowski
2018-05-14  6:36   ` Stephane Chazelas
2018-05-14  6:44     ` Stephane Chazelas
2018-05-14  8:47       ` Peter Stephenson
2018-05-14 12:34         ` Stephane Chazelas
2018-05-14 13:50           ` Peter Stephenson
2018-05-14 15:51             ` Stephane Chazelas
2018-05-14 16:31               ` Sebastian Gniazdowski
2018-05-14 16:50                 ` Bart Schaefer
2018-05-14 19:52                   ` Daniel Tameling
2018-05-14 20:42                     ` Stephane Chazelas
2018-05-15 18:12                       ` Stephane Chazelas
2018-05-16  4:18                         ` Sebastian Gniazdowski
2018-05-15 19:06               ` Oliver Kiddle
2018-05-16 13:15                 ` Stephane Chazelas
2018-05-16 13:40                   ` Peter Stephenson
2018-05-16 16:31                     ` Stephane Chazelas
2018-05-16 21:02                       ` [PATCH v4] " Stephane Chazelas
2018-05-17  8:29                         ` Peter Stephenson
2018-05-17 22:05                       ` [PATCH] " Oliver Kiddle
2018-05-17  9:03           ` Sebastian Gniazdowski [this message]
2018-05-17 10:10             ` Sebastian Gniazdowski
2018-05-14  8:11     ` Sebastian Gniazdowski

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='CAKc7PVAKMBjWF+Bs9bOprH6VCAbxTzaZf4mffJm=eJvdJbRm+Q@mail.gmail.com' \
    --to=sgniazdowski@gmail.com \
    --cc=p.stephenson@samsung.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).