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-04-02 09:37 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... related to 0001556 clarify meaning of \n used in a bracket... ======================================================================
---------------------------------------------------------------------- (0005775) kre (reporter) - 2022-04-02 09:37 https://austingroupbugs.net/view.php?id=1550#c5775 ---------------------------------------------------------------------- Rather than making the spec for delimiters ban the use of backslash or newline, I'd prefer to simply say "Any character ..." and leave the basic definition at that. Then, in a subsequent sentence, or perhaps even paragraph, say something like Note: even if escaped, the characters <backslash> and <newline> cannot be used as dellimiter characters. <backslash> does not work, as if unescaped later in the RE, it either becomes the escape character, in which case its purpose is to escape the following character, which can then never be the ending delimiter, or it forms part of a bracket expression, inside which the ending delimiter for the RE cannot be located. <newline> does not work either, as if not escaped, it is removed, and terminates the command, meaning it cannot be the ending delimiter., and if escaped, cannot be the ending delimiter either. Hence use of either of these characters as a delimiter makes it impossible to supply the required ending delimiter. That both removes the \ and \n from being odd special cases, and explains just why they don't (can't) work as delimiter characters (without requiring any extra text to explain what the implementation should do should the user attempt to do such a thing). 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 2022-03-26 00:34 calestyo Note Edited: 0005767 2022-03-31 16:00 nick Relationship added related to 0001556 2022-04-02 01:53 calestyo Note Added: 0005771 2022-04-02 02:30 calestyo Note Added: 0005772 2022-04-02 09:37 kre Note Added: 0005775 ======================================================================
