zsh-workers
 help / color / mirror / code / Atom feed
From: Bart Schaefer <schaefer@brasslantern.com>
To: zsh-workers@zsh.org
Subject: Re: zsh-5.2-test-3
Date: Sun, 11 Dec 2016 00:58:40 -0800	[thread overview]
Message-ID: <161211005840.ZM27127@torch.brasslantern.com> (raw)
In-Reply-To: <20161211041119.GA32167@fujitsu.shahaf.local2>

On Dec 11,  4:11am, Daniel Shahaf wrote:
} Subject: Re: zsh-5.2-test-3
}
} Bart Schaefer wrote on Sat, Dec 10, 2016 at 19:44:21 -0800:
} > Actually -- why is that test in B02 in the first place, rather than in
} > say D04parameter.ztst ?
} 
} Because it's about assignment, as opposed to substitution?

Then why isn't in it A06assign ?  (Because it's not really about
assignment, either -- it's about a special-parameter side-effect.)

} If there's a better home for the test I don't mind moving it.

It probably ought to be in A05execution, or maybe we need a new test
file just for behavior of assorted special parameters.  C06specials ?

Incidentally, assigning to USERNAME attempts to change both UID and
GID and is still only a warning, not an error.  Further, if setuid()
and setgid() aren't available, assignments to UID et al. silently
do nothing, which is probably why failure of set?id() when available
was never a hard error before.

Passing thought, mostly unrelated:  There should be tests of "getopts"
in B08shift.  I believe we still have some incompatibility with POSIX
in OPTIND/OPTARG handling it would be nice to have an example of the
current behavior with some mention of the difference in case we get
around to fixing it.


      reply	other threads:[~2016-12-11  9:06 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CGME20161206195028epcas2p3c53119ab37952571be3238cdf228d88f@epcas2p3.samsung.com>
     [not found] ` <20161206194916.10448440@ntlworld.com>
2016-12-06 23:33   ` test failures on Solaris (was Re: zsh-5.2-test-2) Danek Duvall
2016-12-07  0:36     ` Bart Schaefer
     [not found]   ` <20161209095729.2033b5be@pwslap01u.europe.root.pri>
     [not found]     ` <20161209195457.27e43234@ntlworld.com>
     [not found]       ` <584CB4EF.6070904@eastlink.ca>
2016-12-11  3:07         ` zsh-5.2-test-3 Bart Schaefer
2016-12-11  3:26           ` zsh-5.2-test-3 Daniel Shahaf
2016-12-11  3:33             ` zsh-5.2-test-3 Bart Schaefer
2016-12-11  3:26           ` zsh-5.2-test-3 Ray Andrews
2016-12-11  3:44             ` zsh-5.2-test-3 Bart Schaefer
2016-12-11  3:59               ` zsh-5.2-test-3 Ray Andrews
2016-12-11  9:36                 ` zsh-5.2-test-3 Bart Schaefer
2016-12-11 17:01                   ` zsh-5.2-test-3 Ray Andrews
2016-12-11 17:14                     ` zsh-5.2-test-3 Bart Schaefer
2016-12-11  4:11               ` zsh-5.2-test-3 Daniel Shahaf
2016-12-11  8:58                 ` Bart Schaefer [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:
  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=161211005840.ZM27127@torch.brasslantern.com \
    --to=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).