A NOTE has been added to this issue. ====================================================================== https://austingroupbugs.net/view.php?id=1550 ====================================================================== Reported By: calestyo Assigned To: ====================================================================== Project: Issue 8 drafts Issue ID: 1550 Category: Shell and Utilities Type: Enhancement Request Severity: Editorial Priority: normal Status: New Name: Christoph Anton Mitterer Organization: User Reference: Section: Utilities, sed Page Number: 3132, ff. (in the draft) Line Number: see below Final Accepted Text: ====================================================================== Date Submitted: 2022-01-14 05:32 UTC Last Modified: 2022-03-26 00:08 UTC ====================================================================== Summary: clarifications/ambiguities in the description of context addresses and their delimiters for sed ====================================================================== Relationships ID Summary ---------------------------------------------------------------------- related to 0001551 sed: ambiguities in the how BREs/EREs a... ======================================================================
---------------------------------------------------------------------- (0005767) calestyo (reporter) - 2022-03-26 00:08 https://austingroupbugs.net/view.php?id=1550#c5767 ---------------------------------------------------------------------- Re: https://austingroupbugs.net/view.php?id=1550#c5756 your (1): agreed your (2a): agreed, and you're right about the issue with "shall be identical" your (2b): I wouldn't agree here because... In "where c is any character other than <backslash> or <newline>", the idea behind exclusion of <backslash> and <newline> is, AFAIU, rather a *general* exclusion, that is in the sense of "neither of these two characters can ever be delimiters". I wouldn't have understood that sentence in the sense of "any c except <backslash> and <newline> have to use the \cREc form" but rather as "any c have to use the \cREc form and <backslash> or <newline> cannot be used at all". I agree, that the wording of the sentence actually describes the former,... but I think the spirit that it means is rather the latter (in which case it would be open whether c is any character or any character except (forward) <slash>). If not, the question would be open as to how <backslash> or <newline> would be encoded as delimiters. your (2c): Well I agree it's "semi-clear" (especially because of the given example)... still adding a short clarification as in: "If any but the first occurrence of the character designated by c appears following a <backslash>" shouldn't cause much harm and make it really definite. I personally would recommend against dealing with that in https://austingroupbugs.net/view.php?id=1551 . While they touch the same section, this one here is merely a subtle cosmetic change, which doesn't really affect the deeper semantics as most of #1551 does. Issue History Date Modified Username Field Change ====================================================================== 2022-01-14 05:32 calestyo New Issue 2022-01-14 05:32 calestyo Name => Christoph Anton Mitterer 2022-01-14 05:32 calestyo Section => Utilities, sed 2022-01-14 05:32 calestyo Page Number => 3132, ff. (in the draft) 2022-01-14 05:32 calestyo Line Number => see below 2022-01-14 05:40 calestyo Note Added: 0005601 2022-01-14 06:34 Don Cragun Relationship added related to 0001551 2022-01-14 06:52 Don Cragun Project 1003.1(2016/18)/Issue7+TC2 => Issue 8 drafts 2022-01-14 06:54 Don Cragun Note Added: 0005603 2022-01-14 06:54 Don Cragun version => Draft 2.1 2022-03-18 11:15 geoffclare Note Added: 0005756 2022-03-18 11:15 geoffclare Note Edited: 0005756 2022-03-25 16:18 geoffclare Note Added: 0005761 2022-03-25 16:22 geoffclare Note Edited: 0005761 2022-03-26 00:08 calestyo Note Added: 0005767 ======================================================================
