zsh-workers
 help / color / mirror / code / Atom feed
From: Stephane Chazelas <stephane.chazelas@gmail.com>
To: ZyX <kp-pav@yandex.ru>
Cc: Peter Stephenson <p.w.stephenson@ntlworld.com>,
	"zsh-workers@zsh.org" <zsh-workers@zsh.org>
Subject: Re: [BUG] Unicode variables can be exported and are exported metafied
Date: Sat, 20 Dec 2014 00:13:58 +0000	[thread overview]
Message-ID: <20141220001357.GA21647@chaz.gmail.com> (raw)
In-Reply-To: <798181419029050@web11g.yandex.ru>

2014-12-20 01:44:10 +0300, ZyX:
[...]
[about making the shell syntax locale-dependant]
> bash: echoes $абв
[...]

You'd have gotten a different behaviour in a single-byte locale.

Related discussion:

http://thread.gmane.org/gmane.comp.shells.bash.bugs/22367

Personally, I think I'd rather shell variable names be limited
to ASCII [:alnum:]_.

Making the shell syntax locale dependant is a problem in scripts
(and we're already affected by that to some extent with
utilities) because there, it's the *author*'s locale that
matters, not the user's.

(Or else, you could do like rc and allow anything allowed in env
vars (rc allows any name as long as it's not empty and doesn't
contain `=`).

-- 
Stephane


  reply	other threads:[~2014-12-20  0:21 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-12-18 18:19 ZyX
2014-12-18 19:29 ` Peter Stephenson
2014-12-18 19:47   ` Peter Stephenson
2014-12-18 19:58     ` Bart Schaefer
2014-12-18 20:09       ` Peter Stephenson
     [not found]       ` <54933513.6010501@case.edu>
2014-12-18 20:20         ` Fwd: " Bart Schaefer
2014-12-19  9:29       ` Christoph (Stucki) von Stuckrad
2014-12-19 18:17       ` Christoph (Stucki) von Stuckrad
2014-12-19 20:13         ` Павлов Николай Александрович
2014-12-19 21:21         ` Peter Stephenson
2014-12-19 22:44           ` ZyX
2014-12-20  0:13             ` Stephane Chazelas [this message]
2014-12-20  9:27               ` ZyX
2014-12-20 10:08                 ` Stephane Chazelas

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=20141220001357.GA21647@chaz.gmail.com \
    --to=stephane.chazelas@gmail.com \
    --cc=kp-pav@yandex.ru \
    --cc=p.w.stephenson@ntlworld.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).