A NOTE has been added to this issue. ====================================================================== http://austingroupbugs.net/view.php?id=1038 ====================================================================== Reported By: kre Assigned To: ====================================================================== Project: 1003.1(2013)/Issue7+TC1 Issue ID: 1038 Category: Shell and Utilities Type: Error Severity: Objection Priority: normal Status: New Name: Robert Elz Organization: User Reference: Section: 2.5.3, 2.6 Page Number: 2352 Line Number: 74952 Interp Status: --- Final Accepted Text: ====================================================================== Date Submitted: 2016-03-24 18:24 UTC Last Modified: 2017-03-03 15:27 UTC ====================================================================== Summary: Specification relies upon unspecified behaviour ====================================================================== Relationships ID Summary ---------------------------------------------------------------------- related to 0001006 PS1 should be subject to command substi... ======================================================================
---------------------------------------------------------------------- (0003590) eblake (manager) - 2017-03-03 15:27 http://austingroupbugs.net/view.php?id=1038#c3590 ---------------------------------------------------------------------- In particular, the text was ambiguous as to whether the default PS1, PS2, and PS4 are applied at all places where the user unsets the variable, or only at shell startup (the latter matches existing practice - unsetting a PS? variable results in no further prompting, so the default is a startup-only operation). Also, bash currently does NOT set PS1 to something that expands to a mere '$ ', but instead sets it to something that expands to the basename of $0, a dash, a version string, and then the '$ '. It is unclear whether Chet Ramey is willing to fix this as a bug in 'bash --posix' mode, or whether the standard should be relaxed to permit bash behavior (by changing the wording to require that the prompt merely end in a literal '$ ', not that it is '$ ' in entirety). Another bash behavior brought up is that bash changes PS4 in subshells, by repeating the first character as an indication of shell depth, and the standard does not permit that. Again, Chet's opinion on whether it is something he is willing to fix for 'bash --posix', or whether the standard should be relaxed to allow it as existing behavior, would be worthwhile. Issue History Date Modified Username Field Change ====================================================================== 2016-03-24 18:24 kre New Issue 2016-03-24 18:24 kre Name => Robert Elz 2016-03-24 18:24 kre Section => 2.5.3, 2.6 2016-03-24 18:24 kre Page Number => unknown 2016-03-24 18:24 kre Line Number => unknown 2016-08-11 15:29 Don Cragun Relationship added related to 0001006 2017-03-02 16:22 nick Page Number unknown => 2352 2017-03-02 16:22 nick Line Number unknown => 74952 2017-03-02 16:22 nick Interp Status => --- 2017-03-03 14:42 shware_systems Note Added: 0003589 2017-03-03 15:27 eblake Note Added: 0003590 ======================================================================
