From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: dick Newsgroups: gmane.emacs.bugs Subject: bug#55863: 29.0.50; [PATCH] Avoid hanging chad of *Backtrace* Date: Fri, 10 Jun 2022 07:39:28 -0400 Message-ID: <87leu4bvdb.fsf@dick> References: <877d5qetfm.fsf@dick> <874k0u6lhv.fsf@gnus.org> <87czfi3pyu.fsf@dick> <864k0teq3y.fsf@mail.linkov.net> <877d5pwsrx.fsf@ericabrahamsen.net> <878rq54omf.fsf@dick> <875yl8x40c.fsf@gnus.org> <874k0s4yyx.fsf@dick> <87v8t8u92q.fsf@gnus.org> <87zgik3jez.fsf@dick> Mime-Version: 1.0 Content-Type: text/plain Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="23243"; mail-complaints-to="usenet@ciao.gmane.io" User-Agent: Gnus/5.14 (Gnus v5.14) Commercial/29.0.50 (gnu/linux) Cc: 55863@debbugs.gnu.org To: Lars Ingebrigtsen Original-X-From: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane-mx.org@gnu.org Fri Jun 10 16:32:48 2022 Return-path: Envelope-to: geb-bug-gnu-emacs@m.gmane-mx.org Original-Received: from lists.gnu.org ([209.51.188.17]) by ciao.gmane.io with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1nzfgu-0005wA-KK for geb-bug-gnu-emacs@m.gmane-mx.org; Fri, 10 Jun 2022 16:32:48 +0200 Original-Received: from localhost ([::1]:33128 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1nzfgt-00064o-7I for geb-bug-gnu-emacs@m.gmane-mx.org; Fri, 10 Jun 2022 10:32:47 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:46234) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1nzffE-0004tI-59 for bug-gnu-emacs@gnu.org; Fri, 10 Jun 2022 10:31:04 -0400 Original-Received: from debbugs.gnu.org ([209.51.188.43]:57047) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.90_1) (envelope-from ) id 1nzffD-00012Y-7w for bug-gnu-emacs@gnu.org; Fri, 10 Jun 2022 10:31:03 -0400 Original-Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1nzffD-0000WQ-5v for bug-gnu-emacs@gnu.org; Fri, 10 Jun 2022 10:31:03 -0400 X-Loop: help-debbugs@gnu.org Resent-From: dick Original-Sender: "Debbugs-submit" Resent-CC: bug-gnu-emacs@gnu.org Resent-Date: Fri, 10 Jun 2022 14:31:03 +0000 Resent-Message-ID: Resent-Sender: help-debbugs@gnu.org X-GNU-PR-Message: followup 55863 X-GNU-PR-Package: emacs X-GNU-PR-Keywords: moreinfo Original-Received: via spool by 55863-submit@debbugs.gnu.org id=B55863.16548714191924 (code B ref 55863); Fri, 10 Jun 2022 14:31:03 +0000 Original-Received: (at 55863) by debbugs.gnu.org; 10 Jun 2022 14:30:19 +0000 Original-Received: from localhost ([127.0.0.1]:50939 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1nzfeT-0000Uo-7t for submit@debbugs.gnu.org; Fri, 10 Jun 2022 10:30:19 -0400 Original-Received: from mail-qt1-f175.google.com ([209.85.160.175]:34478) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1nzczH-0004LU-Ly for 55863@debbugs.gnu.org; Fri, 10 Jun 2022 07:39:36 -0400 Original-Received: by mail-qt1-f175.google.com with SMTP id c8so19125056qtj.1 for <55863@debbugs.gnu.org>; Fri, 10 Jun 2022 04:39:35 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=from:to:cc:subject:references:date:in-reply-to:message-id :user-agent:mime-version; bh=8cy5GX/SR4f2ODIRq02xa/YS99kydhbZZOyt5eUMMCQ=; b=eTcuDD/Ezy8womvj35LhUJAQgI/3stGKbMy/57fCr4o2XS326GVWzi4v/youwLiFmO 2H6rOc3M6nLU82hGioSC/Sa3fIK+K+dUkwWZ3JnvlapOMb+1boZPsayOvPUi2C8qoEQE Ebwr/0NXvTh5/KAVpEaiU1stKzlpncBXWAVvTbAumFMHUMb3cXPufck9cRHiUm9WYeDl wJgSW2VHfSlhB88ecMBT15kvSa6lqMxtNw+QwJZiDavhSNuBPi39tS5M82dohXd65Odt m0+vUAnyCDd9HCl0narVF0BjJElFInEzt004rvWA7a4b3sWYJwMbgwmhcYIJD1WVmjRr DY5A== 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=8cy5GX/SR4f2ODIRq02xa/YS99kydhbZZOyt5eUMMCQ=; b=dIXuyoI+V4IHlBBgTMwkZ1JR/Fpe67fk5N8qM6Q00lPtx6ZOsQSZ+K+uPX8RZgBRBr MJWE/lRDeiA0IwSR3CJ7aSgU4HXfV0eEGIGZoK6xjF0gGz7S9dY+29aqrLqvprn3fCmS VLnzXiqFr69OPjXf/eemefRNSthozO8tLvHxwWGz36mNfwKI74r2w9Wbp0rcmuJaZQA8 eAcX0ILDo1LPin+99S/4UXkUQZyuoF4r4HCcib4qHiBIsd4Vk95hdLfEUABICnHbBK1a lMHEG4CKooLksH4YSA/yhbaz6VVCmdjC8IUgAa02Y0Z8vLwXu/ZGXclWkTfvFueq0Gza yANA== X-Gm-Message-State: AOAM532y4rfnchpsiC83a5a3C5ZAiAdjTGIrNGajK43m3WMhS0hTru6s ybeJZQGvGpWrl+uwVds1/V2jwWul2zU= X-Google-Smtp-Source: ABdhPJwqHjT7Sn4IXWG8KSOFAk57M0mTAiy7fEcez31+dH+AIVb39f13PAUSjoss57KLRwT9h3y7rw== X-Received: by 2002:ac8:5b51:0:b0:305:1aa7:1aab with SMTP id n17-20020ac85b51000000b003051aa71aabmr2527369qtw.616.1654861169879; Fri, 10 Jun 2022 04:39:29 -0700 (PDT) Original-Received: from localhost (pool-96-232-253-158.nycmny.fios.verizon.net. [96.232.253.158]) by smtp.gmail.com with ESMTPSA id d16-20020ac86690000000b00304e90f66f7sm11900147qtp.70.2022.06.10.04.39.29 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Fri, 10 Jun 2022 04:39:29 -0700 (PDT) In-Reply-To: <87zgik3jez.fsf@dick> (dick's message of "Fri, 10 Jun 2022 06:24:52 -0400") X-Mailman-Approved-At: Fri, 10 Jun 2022 10:30:11 -0400 X-BeenThere: debbugs-submit@debbugs.gnu.org X-Mailman-Version: 2.1.18 Precedence: list X-BeenThere: bug-gnu-emacs@gnu.org List-Id: "Bug reports for GNU Emacs, the Swiss army knife of text editors" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane-mx.org@gnu.org Original-Sender: "bug-gnu-emacs" Xref: news.gmane.io gmane.emacs.bugs:234227 Archived-At: So I set about replacing kill-buffer with bury-buffer, then demoting the *Backtrace* buffer from debugger-mode to backtrace-mode, and realized maybe kill-buffer is best. The confusion is we're accustomed to "q" as a passive bury, when in fact "q" in debugger-mode corresponds to the highly un-passive "debugger-quit". To emphasize that, perhaps "q" in debugger-mode should be gated by an "Are you sure?" yes-or-no-p. Toting around old *Backtrace* buffers is fraught. As GNU is really a preservationist society moonlighting as software developers, I expect I am, as usual, in the minority and will bow out of this particular discuz. >>>>> dick writes: > I'm down for burying on "q" so long as subsequent debug's don't > generate-new-buffer to admit *Backtrace<2>* and *Backtrace<3>*.