zsh-workers
 help / color / mirror / code / Atom feed
From: Sebastian Gniazdowski <sgniazdowski@gmail.com>
To: Zsh hackers list <zsh-workers@zsh.org>
Subject: Re: [PATCH] [[:blank:]] only matches on SPC and TAB
Date: Wed, 16 May 2018 06:18:25 +0200	[thread overview]
Message-ID: <CAKc7PVAYXTdeHjawSAfpPVDkB7AepYt=5w0pxH85g08Fbe1nHA@mail.gmail.com> (raw)
In-Reply-To: <20180515181212.GA13171@chaz.gmail.com>

On 15 May 2018 at 20:12, Stephane Chazelas <stephane.chazelas@gmail.com> wrote:
> Note that by some reading of the spec, and bash and yash have
> made such readings, when the spec says tokens are delimited by
> blanks, that's any blank in the locale.
>
> $ yash -c $'echo\u2006test'
> test
>
> In the case of bash, that only works "properly" with single-byte
> characters.

Doing some more or less bizarre coding, this allows to hide
information in the command line. Assuming script has access to full
command text (e.g. $jobtexts), it can check which argument is
prepended with e.g. non-breaking space(s), and which with regular
space(s). Zshell would behave as if there's no difference, while
script could decide on something, e.g. that nbs-prepended argument is
a fifo not a regular file, and some custom function show_jobs_status()
could show fifos in different color. Just doing deep-implications
survey, if e.g. SQL designers would do this properly, there wouldn't
be so many flavors of SQL today.

-- 
Best regards,
Sebastian Gniazdowski


  reply	other threads:[~2018-05-16  4:18 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 [this message]
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
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='CAKc7PVAYXTdeHjawSAfpPVDkB7AepYt=5w0pxH85g08Fbe1nHA@mail.gmail.com' \
    --to=sgniazdowski@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).