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 19:57 UTC ====================================================================== Summary: Specification relies upon unspecified behaviour ====================================================================== Relationships ID Summary ---------------------------------------------------------------------- related to 0001006 PS1 should be subject to command substi... ======================================================================
---------------------------------------------------------------------- (0003602) shware_systems (reporter) - 2017-03-03 19:57 http://austingroupbugs.net/view.php?id=1038#c3602 ---------------------------------------------------------------------- On terminals that do not line wrap, echoing of user input on the same line would frequently go to /dev/nul/ instead of at least the first part being visible to the operator, with lines that long. A similar possibility exists with bash's PS4 prompts, if some script uses 100s of trace levels for a recursive algorithm. This is the primary concern here. Scripts that format output to adapt to terminals like this need a fixed width prompt to subtract from the terminal's line width setting to maintain alignments. The standard can't guard against any data ever being lost with terminals like this, but I agree with Don, the implementations shouldn't make it more likely to occur as their default behaviors. These variable length prompts are fine as a bash extension, or as default behavior for a user with extended privileges who has rtfm and is aware bash does this, but are non-conforming to what non-privileged users of sh who only read the sh man page are told to expect of script and interactive behavior. 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 2017-03-03 15:50 kre Note Added: 0003591 2017-03-03 15:59 joerg Note Added: 0003593 2017-03-03 16:10 geoffclare Note Added: 0003594 2017-03-03 16:41 shware_systems Note Added: 0003595 2017-03-03 16:44 joerg Note Deleted: 0003593 2017-03-03 16:46 chet_ramey Note Added: 0003597 2017-03-03 17:15 Don Cragun Note Added: 0003598 2017-03-03 17:16 Don Cragun Note Edited: 0003598 2017-03-03 18:58 chet_ramey Note Added: 0003599 2017-03-03 19:03 eblake Note Added: 0003600 2017-03-03 19:54 chet_ramey Note Added: 0003601 2017-03-03 19:57 shware_systems Note Added: 0003602 ======================================================================
