From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-io1-xd2f.google.com (mail-io1-xd2f.google.com [IPv6:2607:f8b0:4864:20::d2f]) by sourceware.org (Postfix) with ESMTPS id 57E263858C1F for ; Mon, 31 Jan 2022 19:34:00 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.4.1 sourceware.org 57E263858C1F Received: by mail-io1-xd2f.google.com with SMTP id s18so18284800ioa.12 for ; Mon, 31 Jan 2022 11:34:00 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:from:to:cc:subject:references:date:in-reply-to :message-id:user-agent:mime-version; bh=W9+aBLN0BNnVUq8a+vROkGJ5IE5Nuh66K8sk2QPwlyo=; b=Not7yL2lRKkvugexL2kyZ6fJzWD26bDmp9zIGeDA8cdY6drrzDzHsC0T32RXw/tWvO u1h+SSUWlvCM1RR2oVELeIFRsFd/f6lrcn4gAtaOw+OBnxE41b6OqjHgnYtchgzh2k57 PVMUCHuG1TOSooLbMDu9RNYcljQMu133HxL/WenFpsgIc94Lf6DzBJQ7iFwoXaxJGwKa FNmmZZysLRgnQxafxzr/IcYe4YEc9N5TPT8DMTq94sb8oPaBQtuftf7S7W0QnJT7AhX1 /N2vpM+0cx1n3Hv5jSyS/6SpAxqGfKFhO0XLs2KGLww0Ip8cMbMPgJF1Fr+miZLUoM+l zGgA== X-Gm-Message-State: AOAM533P5fy9nbvOXI1fcQz4kumLTOkR5WVYreZFVuRukTziSpQHN+/U TT87HzdV2ndSf+GLYSIXpE9Ve6Ioy4H+Pw== X-Google-Smtp-Source: ABdhPJy+QHqYEbc3NKhuYgDS8nPhNJ1GWWWfsHWu1JVDXmASeftYCmdZTN1o6y2WJIcG+K0urJGojg== X-Received: by 2002:a05:6638:d8a:: with SMTP id l10mr4563370jaj.27.1643657639708; Mon, 31 Jan 2022 11:33:59 -0800 (PST) Received: from murgatroyd (75-166-128-165.hlrn.qwest.net. [75.166.128.165]) by smtp.gmail.com with ESMTPSA id n3sm7384897ioz.9.2022.01.31.11.33.58 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Mon, 31 Jan 2022 11:33:59 -0800 (PST) From: Tom Tromey To: Tom Tromey via Gdb-patches Cc: Tom Tromey Subject: Re: [RFC] Print MI prompt on interrupted command References: <20220106173213.3682241-1-tromey@adacore.com> <87h79q9vv8.fsf@tromey.com> X-Attribution: Tom Date: Mon, 31 Jan 2022 12:33:58 -0700 In-Reply-To: <87h79q9vv8.fsf@tromey.com> (Tom Tromey via Gdb-patches's message of "Wed, 26 Jan 2022 11:48:11 -0700") Message-ID: <87mtjbya1l.fsf@tromey.com> User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/27.2 (gnu/linux) MIME-Version: 1.0 Content-Type: text/plain X-Spam-Status: No, score=-5.3 required=5.0 tests=BAYES_00, DKIM_SIGNED, DKIM_VALID, DKIM_VALID_AU, DKIM_VALID_EF, RCVD_IN_DNSWL_NONE, SPF_HELO_NONE, SPF_PASS, TXREP, T_SCC_BODY_TEXT_LINE autolearn=ham autolearn_force=no version=3.4.4 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: Mon, 31 Jan 2022 19:34:02 -0000 >>>>> "Tom" == Tom Tromey via Gdb-patches writes: Tom> Does it seems like a reasonable idea? It is likely to break existing Tom> clients? Or perhaps should start_event_loop (that's what notifies the Tom> command_error observer) loop over all UIs and emit a prompt for each? >> I'm leaning toward this latter plan now. I did some experimenting with new-ui and I think that it would be weird to emit a prompt in this situation. So now I'm back to thinking the original patch is probably ok. Tom