A NOTE has been added to this issue. ====================================================================== https://austingroupbugs.net/view.php?id=1786 ====================================================================== Reported By: eblake Assigned To: ====================================================================== Project: Issue 8 drafts Issue ID: 1786 Category: Shell and Utilities Type: Clarification Requested Severity: Objection Priority: normal Status: Resolved Name: Eric Blake Organization: Red Hat User Reference: ebb.ed Section: XCU ed Page Number: 2801 Line Number: 92899 Final Accepted Text: Resolution: Reopened Fixed in Version: ====================================================================== Date Submitted: 2023-11-02 15:13 UTC Last Modified: 2023-11-16 16:40 UTC ====================================================================== Summary: ed behavior on non-existing filename ====================================================================== Relationships ID Summary ---------------------------------------------------------------------- related to 0000251 Forbid newline, or even bytes 1 through... ======================================================================
---------------------------------------------------------------------- (0006571) eblake (manager) - 2023-11-16 16:40 https://austingroupbugs.net/view.php?id=1786#c6571 ---------------------------------------------------------------------- Based on https://austingroupbugs.net/view.php?id=1786#c6570, we did some more investigation into existing implementations. It appears that most implementations clear the buffer change flag on an 'e' or 'q' that warned about a modified buffer, as in the following behavior:<blockquote>$ ed a text . q ? a . q $</blockquote> where GNU ed was the outlier. The following modification to https://austingroupbugs.net/view.php?id=1786#c6567 would capture that: On page 2800 line 92844, change: <blockquote>... and shall continue in command mode with the current line number unchanged. If the <b>e</b> or <b>q</b> command is repeated with no intervening command, it shall take effect.</blockquote> to <blockquote>... and shall continue in command mode with the buffer change flag cleared and the current line number unchanged. If another <b>e</b> or <b>q</b> command is then attempted with no intervening command that sets the buffer change flag, it shall take effect.</blockquote> For now, we've reopened the bug to allow more feedback Issue History Date Modified Username Field Change ====================================================================== 2023-11-02 15:13 eblake New Issue 2023-11-02 15:13 eblake Name => Eric Blake 2023-11-02 15:13 eblake Organization => Red Hat 2023-11-02 15:13 eblake User Reference => ebb.ed 2023-11-02 15:13 eblake Section => XCU ed 2023-11-02 15:13 eblake Page Number => 2801 2023-11-02 15:13 eblake Line Number => 92899 2023-11-02 15:16 eblake Relationship added related to 0000251 2023-11-02 15:18 eblake Description Updated 2023-11-02 15:18 eblake Desired Action Updated 2023-11-13 17:31 geoffclare Note Added: 0006567 2023-11-13 17:32 geoffclare Final Accepted Text => https://austingroupbugs.net/view.php?id=1786#c6567 2023-11-13 17:32 geoffclare Status New => Resolved 2023-11-13 17:32 geoffclare Resolution Open => Accepted As Marked 2023-11-13 17:32 geoffclare Tag Attached: issue8 2023-11-14 16:00 Antonio Diaz Note Added: 0006570 2023-11-16 16:37 eblake Final Accepted Text https://austingroupbugs.net/view.php?id=1786#c6567 => 2023-11-16 16:37 eblake Resolution Accepted As Marked => Reopened 2023-11-16 16:40 eblake Note Added: 0006571 ======================================================================