On 09/01/2019 12:29, Austin Group Bug Tracker wrote:
[...] > ---------------------------------------------------------------------- (0004201) geoffclare (manager) - 2019-01-09 12:29 http://austingroupbugs.net/view.php?id=953#c4201 ---------------------------------------------------------------------- This is a proposed new resolution which addresses comments made since http://austingroupbugs.net/view.php?id=953#c3113 both here and on the mailing list. There have been a <b>lot</b> of comments, so if I missed anything please reply <b>on the mailing list</b> and (if I agree) I will edit this note. [...] On page 2351 line 74901-74904 (XCU 2.5.3 Shell Variables) change:<blockquote>This variable, when and only when an interactive shell is invoked, shall be subjected to parameter expansion (see Section 2.6.2) by the shell and the resulting value shall be used as a pathname of a file containing shell commands to execute in the current environment.</blockquote>to:<blockquote>This variable, when and only when an interactive shell is invoked, shall be subjected to parameter expansion (see Section 2.6.2) by the shell and the resulting value shall be used as a pathname of a file. Before any interactive commands are read, the shell shall tokenize (see [xref to XCU 2.3 Token Recognition]) the contents of the file, parse the tokens as a <i>program</i> (see [xref to XCU 2.10 Shell Grammar]), and execute the resulting commands in the current environment. (In other words, the contents of the ENV file are not parsed as a single <i>compound_list</i>, unlike the contents of a dot script. This distinction matters because it influences when aliases take effect.)</blockquote>
This last bit was part of an earlier version, but it no longer fits now that the contents of a dot script are no longer required to be parsed as a compound_list. The rest of the comment still makes perfect sense if you take out the ", unlike the contents of a dot script" bit, I think.
Cheers, Harald van Dijk
