From owner-freebsd-bugs Tue Feb 27 22:48:47 1996 Return-Path: owner-bugs Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id WAA16044 for bugs-outgoing; Tue, 27 Feb 1996 22:48:47 -0800 (PST) Received: from fw.ast.com (fw.ast.com [165.164.6.25]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id WAA16033 for ; Tue, 27 Feb 1996 22:48:45 -0800 (PST) Received: from nemesis by fw.ast.com with uucp (Smail3.1.29.1 #2) id m0treEN-00084fC; Tue, 27 Feb 96 23:15 CST Received: by nemesis.lonestar.org (Smail3.1.27.1 #20) id m0trdvl-000DI3C; Tue, 27 Feb 96 22:56 WET Message-Id: Date: Tue, 27 Feb 96 22:56 WET To: bugs@freebsd.org From: uhclem@nemesis.lonestar.org (Frank Durda IV) Sent: Tue Feb 27 1996, 22:56:01 CST Subject: gnu/1047: send-pr: Aborting... Sender: owner-bugs@freebsd.org Precedence: bulk [0]send-pr sometimes after you have written your bug report and exit the [0]editor, will say [0] [0]send-pr: Aborting... [0] [0]and deletes your bug report without sending it. Enormously irritating! I agree! You can cause this if you hit at any point while in VI writing the problem report. When you exit after carefully constructing the problem reports, send-pr immediately aborts and the tmp file is erased. It used to be the case that you could press or *prior* to vi completely exiting and cause it to abort, although this is much harder to do. I suggest the code be modified to at least keep the prepared bug file around somewhere like it does if you do select "A" for Abort. It certainly should disregard signals sent to children like . Frank Durda IV |"The Knights who say "LETNi" or uhclem%nemesis@rwsystr.nkn.net | demand... A SEGMENT REGISTER!!!" |"A what?" or ...letni!rwsys!nemesis!uhclem |"LETNi! LETNi! LETNi!" - 1983