zsh-workers
 help / color / mirror / code / Atom feed
From: ZyX <kp-pav@yandex.ru>
To: Bart Schaefer <schaefer@brasslantern.com>,
	Zsh hackers list <zsh-workers@zsh.org>
Subject: Re: ["regression"] Stéphane= 1 zsh -c 'echo $Stéphane'
Date: Tue, 06 Oct 2015 21:59:01 +0300	[thread overview]
Message-ID: <24401444157941@web22h.yandex.ru> (raw)
In-Reply-To: <151006084416.ZM5546@torch.brasslantern.com>


06.10.2015, 18:44, "Bart Schaefer" <schaefer@brasslantern.com>:
> This is discussed in the thread starting at workers/34004 and leading
> up to workers/34015.
>
> Nobody ever commented on whether the environment is allowed to contain
> names with the high-order bit set, but POSIX identifiers cannot, so it
> stands to reason you can't import something with that shape of name.

>From the list of shells I have ${Stéphane} with Stéphane=2 in environment accept only tcsh and ksh now (LANG=ru_RU.UTF-8).

Not accepting: mksh, rcsh*, posh, bash, dash, fish.

No shell accepts this with LANG=C.

glibc+tcc+getenv() call is fine with this name even with LANG=C.

Note: I do not know which standard describes environment variable names and what exactly it says about the issue.

* Plan 9 rc reimplementation, uses name `rcsh` due to name conflict with openrc.

>
> zsh -f -o posixidentifiers -c 'Stéphane=2; echo $Stéphane'
> zsh:1: command not found: Stéphane=2
> éphane
>
> In effect the environment is always treated as POSIX_IDENTIFIERS.
>
> POSIX_IDENTIFIERS <K> <S>
>      When this option is set, only the ASCII characters a to z, A to Z,
>      0 to 9 and _ may be used in identifiers (names of shell parameters
>      and modules).


  reply	other threads:[~2015-10-06 19:05 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-10-06 11:04 ["regression"] Stéphane=1 " Stephane Chazelas
2015-10-06 15:44 ` ["regression"] Stéphane= 1 " Bart Schaefer
2015-10-06 18:59   ` ZyX [this message]
2015-10-06 19:29     ` Stephane Chazelas
2015-10-07 13:15   ` 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=24401444157941@web22h.yandex.ru \
    --to=kp-pav@yandex.ru \
    --cc=schaefer@brasslantern.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).