From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from eggs.gnu.org (eggs.gnu.org [209.51.188.92]) by sourceware.org (Postfix) with ESMTPS id AC26A3858C83 for ; Tue, 8 Mar 2022 12:11:01 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.4.1 sourceware.org AC26A3858C83 Received: from [2001:470:142:3::e] (port=36864 helo=fencepost.gnu.org) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1nRYg8-00046n-Ol; Tue, 08 Mar 2022 07:11:00 -0500 Received: from [87.69.77.57] (port=3258 helo=home-c4e4a596f7) by fencepost.gnu.org with esmtpsa (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1nRYg8-0006Ut-4i; Tue, 08 Mar 2022 07:11:00 -0500 Date: Tue, 08 Mar 2022 14:10:53 +0200 Message-Id: <83fsnsfxv6.fsf@gnu.org> From: Eli Zaretskii To: Andrew Burgess Cc: gdb-patches@sourceware.org In-Reply-To: <87cziwwze2.fsf@redhat.com> (message from Andrew Burgess on Tue, 08 Mar 2022 09:45:57 +0000) Subject: Re: [PATCH 2/2] gdb: handle bracketed-paste-mode and ctrl-d correctly References: <9427f341bb8730756a98d491ffd33a3f883e1dba.1646665813.git.aburgess@redhat.com> <83mti1g042.fsf@gnu.org> <87cziwwze2.fsf@redhat.com> X-Spam-Status: No, score=1.4 required=5.0 tests=BAYES_00, DKIMWL_WL_HIGH, DKIM_SIGNED, DKIM_VALID, DKIM_VALID_AU, DKIM_VALID_EF, RCVD_IN_BARRACUDACENTRAL, SPF_HELO_PASS, SPF_PASS, TXREP, T_SCC_BODY_TEXT_LINE autolearn=no autolearn_force=no version=3.4.4 X-Spam-Level: * X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on server2.sourceware.org X-BeenThere: gdb-patches@sourceware.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Gdb-patches mailing list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 08 Mar 2022 12:11:05 -0000 > From: Andrew Burgess > Cc: gdb-patches@sourceware.org > Date: Tue, 08 Mar 2022 09:45:57 +0000 > > Below is the smallest fix which avoids the prompt corruption; simply > moving the "quit" message to the line after the prompt, like: > > (gdb) > quit Thanks, I think this is much safer for GDB 12, and seems to solve 95% of the original problem. I don't mind if, after branching for GDB 12, your original full changeset will be applied to the master branch, of course.