A NOTE has been added to this issue. ====================================================================== https://www.austingroupbugs.net/view.php?id=1629 ====================================================================== Reported By: mirabilos Assigned To: ====================================================================== Project: 1003.1(2016/18)/Issue7+TC2 Issue ID: 1629 Category: Shell and Utilities Type: Clarification Requested Severity: Editorial Priority: normal Status: New Name: mirabilos Organization: mksh User Reference: Section: unsure which applies Page Number: (page or range of pages) Line Number: (Line or range of lines) Interp Status: --- Final Accepted Text: ====================================================================== Date Submitted: 2023-01-15 17:30 UTC Last Modified: 2023-02-20 21:14 UTC ====================================================================== Summary: Shell vs. read(2) errors on the script ====================================================================== Relationships ID Summary ---------------------------------------------------------------------- related to 0000367 interaction between readonly, export, g... ======================================================================
---------------------------------------------------------------------- (0006160) chet_ramey (reporter) - 2023-02-20 21:14 https://www.austingroupbugs.net/view.php?id=1629#c6160 ---------------------------------------------------------------------- How, if at all, does this affect the behavior of `.'? I assume that this interpretation intends that read errors during execution of `.' are treated as fatal special builtin errors similar to pathname not found. If the shell parses the contents of the file as a program, the shell should handle read errors as it would when reading a shell script and treat them as a fatal error for `.', with the consequences that implies. Is that the intent? Another question is exactly what constitutes a `partial command'. If you have a line that reads echo a; echo b; echo c and you get a read error after the second `;', this isn't exactly a `partial command'. It's a perfectly valid list. Or is this more intended to address partial lines? Getting EOF while parsing a compound command like `while' is already a syntax error, so this doesn't seem to make a difference there. It's mostly lists and pipelines. Issue History Date Modified Username Field Change ====================================================================== 2023-01-15 17:30 mirabilos New Issue 2023-01-15 17:30 mirabilos Name => mirabilos 2023-01-15 17:30 mirabilos Organization => mksh 2023-01-15 17:30 mirabilos URL => unsure which applies 2023-01-15 17:30 mirabilos Section => unsure which applies 2023-01-20 21:18 chet_ramey Note Added: 0006120 2023-01-30 16:45 nick Relationship added related to 0000367 2023-02-02 15:51 chet_ramey Note Added: 0006142 2023-02-04 17:46 chet_ramey Note Added: 0006143 2023-02-09 16:59 geoffclare Note Added: 0006145 2023-02-09 17:06 geoffclare Project Online Pubs => 1003.1(2016/18)/Issue7+TC2 2023-02-18 21:51 mirabilos Note Added: 0006158 2023-02-18 21:54 mirabilos Note Edited: 0006158 2023-02-20 21:14 chet_ramey Note Added: 0006160 ======================================================================
