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-18 11:15 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... ======================================================================
---------------------------------------------------------------------- (0005756) geoffclare (manager) - 2022-03-18 11:15 https://austingroupbugs.net/view.php?id=1550#c5756 ---------------------------------------------------------------------- Taking the points raised in turn: 1) Since there is already a cross-reference to "Regular Expressions in sed", rather than adding a second in the same sentence, I would rearrange the sentence, e.g.:<blockquote>... (which consists of an RE, preceded and followed by a delimiter—usually a <slash>—as described in Regular Expressions in sed).</blockquote> 2a) I would put the reason for the construction up front instead of later:<blockquote>In a context address, a delimiter other than <slash> can be used by means of the construction ...</blockquote>I also think "shall be identical" is wrong because that implies that <slash> still needs to be escaped in the RE even if "c" is a different character. 2b) It is already perfectly clear that "c" can be any character other than <backslash> or <newline>. Which means it can be <slash>. No change needed. 2c) By a strict reading, you are right, although I think the intention is clear. Any fix for this would overlap with bug https://austingroupbugs.net/view.php?id=1551 so is probably best addressed there. I agree with the final comment about moving that bullet item. The need to escape the delimiter is described in the s and y commands, not here, so it seems odd that it is here for context addresses instead of in the description of addresses. 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 ======================================================================
