From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: martin rudalics Newsgroups: gmane.emacs.bugs Subject: bug#13336: [External] : Re: bug#13336: `next-frame' should not choose the *Backtrace* frame while debugging Date: Thu, 26 Aug 2021 09:53:43 +0200 Message-ID: References: <1776CE98469A44C484752764DD29E2DE@us.oracle.com> <878s0srzup.fsf@gnus.org> <25c7bc14-fab3-5411-5526-24ad0de6ed85@gmx.at> <98917a3e-e465-6cfb-ffe6-d977673bf185@gmx.at> <2a1f48d7-1dee-3dba-ef69-efa90fc1c786@gmx.at> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="8468"; mail-complaints-to="usenet@ciao.gmane.io" Cc: "13336@debbugs.gnu.org" <13336@debbugs.gnu.org> To: Drew Adams , Lars Ingebrigtsen Original-X-From: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane-mx.org@gnu.org Thu Aug 26 09:54:10 2021 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 1mJADB-0001yZ-VQ for geb-bug-gnu-emacs@m.gmane-mx.org; Thu, 26 Aug 2021 09:54:09 +0200 Original-Received: from localhost ([::1]:60030 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1mJADA-00025z-V0 for geb-bug-gnu-emacs@m.gmane-mx.org; Thu, 26 Aug 2021 03:54:08 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:35374) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1mJAD4-00025d-3c for bug-gnu-emacs@gnu.org; Thu, 26 Aug 2021 03:54:02 -0400 Original-Received: from debbugs.gnu.org ([209.51.188.43]:36758) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.90_1) (envelope-from ) id 1mJAD3-0008Jv-S3 for bug-gnu-emacs@gnu.org; Thu, 26 Aug 2021 03:54:01 -0400 Original-Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1mJAD3-0004TM-JL for bug-gnu-emacs@gnu.org; Thu, 26 Aug 2021 03:54:01 -0400 X-Loop: help-debbugs@gnu.org Resent-From: martin rudalics Original-Sender: "Debbugs-submit" Resent-CC: bug-gnu-emacs@gnu.org Resent-Date: Thu, 26 Aug 2021 07:54:01 +0000 Resent-Message-ID: Resent-Sender: help-debbugs@gnu.org X-GNU-PR-Message: followup 13336 X-GNU-PR-Package: emacs X-GNU-PR-Keywords: wontfix Original-Received: via spool by 13336-submit@debbugs.gnu.org id=B13336.162996443617177 (code B ref 13336); Thu, 26 Aug 2021 07:54:01 +0000 Original-Received: (at 13336) by debbugs.gnu.org; 26 Aug 2021 07:53:56 +0000 Original-Received: from localhost ([127.0.0.1]:48304 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1mJACx-0004Sz-PP for submit@debbugs.gnu.org; Thu, 26 Aug 2021 03:53:55 -0400 Original-Received: from mout.gmx.net ([212.227.17.20]:36313) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1mJACw-0004Sl-EV for 13336@debbugs.gnu.org; Thu, 26 Aug 2021 03:53:54 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=gmx.net; s=badeba3b8450; t=1629964425; bh=hnWghpS4ez8WHYIjeSCqCaKM5dSer+4xRihmhEd8Kns=; h=X-UI-Sender-Class:Subject:To:Cc:References:From:Date:In-Reply-To; b=TpA+0ZFcJ5UWFTCEmZHtzIK8cj5JS2seizHX6fzgLMrBXaEvKESV/GsZhl+sKiHFY td/4F5EbSLchNtXjN5IcWbEB7NG0vYGmRC6B7GV/zTEHanjEC8WVnqWPUXbS191LvY 5HwEqB47P19hxq4xhQOUt9vppapJ3FB172uDcHoc= X-UI-Sender-Class: 01bb95c1-4bf8-414a-932a-4f6e2808ef9c Original-Received: from [192.168.1.102] ([212.95.5.85]) by mail.gmx.net (mrgmx105 [212.227.17.168]) with ESMTPSA (Nemesis) id 1N1fmq-1n3SGv12KG-0122bS; Thu, 26 Aug 2021 09:53:45 +0200 In-Reply-To: Content-Language: en-US X-Provags-ID: V03:K1:jJYf+3mFkgVY46KzGc9HRhUSJHIQrGLuU3IgTaKNHr3Tz/oiXIU nuyUeVkHhLTlcQqI5gfGGMAjAVnUhJg3SrV8liCCHTQfeIymW9nQ4tOl10TBJfIqfWGSClW rRMxnnj0/l2rvYV8BvO+hmyxPb5PhofzOPzvvNgEa4SW/Gu4n7Y0sy8bkVVXvqd4cEDuZoe EjGzoDcbwj35dz8h7vV3g== X-UI-Out-Filterresults: notjunk:1;V03:K0:VIlWXmZO8IQ=:CxLtybPALisWQsQ2TgNrFk fF+meNjxPObd8kk+NVT6xBtAGkWEqeRU3Nl4ftj5cOOV93WmqS9SPYGoiVA/oeqJ4baGXyUus /i65EJbEhyvRlGi30yeI0c/Hdc/pGeYj4xvpx7z+FHfG62Kyy3vlZM5nvWUOhlv6oH8lexomz 4jrNaHdV42MUtddoxAsXKuitdGll7cHU6jqohLhKHV2fNJUhDkxAC1QhhTbKhbtwWSg+7gXqJ KwYJ9iRwfYlZdcEnQx8qvnfkY0XF14jKzcXSMaOd6dXbMIOUKgqm8rqrkS7WYOklieBsWL9C9 NGZKHFvvvWYO1LdWQ3Kl4ZmcsgOTy8jP4fO0UnD7RCHrB+Iek5WDVAy12XsctDB7N/V+xiBGX X2/lJ+ip1Do/3hmtPBjOTdZIfRPA6MrCx9UHgEBR2OArJ2oUUK5Cnx1SJ16MSKKBXB8BF9MC3 ks34NteI6gE4tX440nJho2HX9d94XXGUO75I5psKcTuleG9ynXiXzWDh1yOU2nqJ6q6uCYb9y /jNvCiIvAvQG88LyHTFnp/IpXlotTcs573E67ScfXSSGNnW56zJfiZnqY0aYSs/wHFZxy28Qz AddAm7PlAl1bgH0lkNquFZuTjjvkC5th8CdkPfAPPZco/BdG2zNoijGShxbaAnvs4+vgOFeFf IAmeu3iR0OLg8GJ2pjqt0x5610d3xolOTR1jl5O5Ex+NGd++pP+fJTM0HfZD7gj6T83iArbbs 9AnEVzX2MYSJNcSOY96DPCZVVbj3jXHPZwWNB9e4PGm+U2xw6jy+0cVp1Dgfw8SjnUSLmemQ 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:212694 Archived-At: >> Why can't you add the `no-other-frame' parameter to that common list for >> the *Backtrace* buffer alone? > > Dunno what you mean. (But it sounds like duplicating > the common list, and adding something to the copy.) Maintain a 'basic-alist' of frame parameters and for the *Backtrace* buffer use (cons (cons 'no-other-frame t) basic-alist) as list of frame parameters. > Why doesn't its doc give users a heads-up in this > (unspecified) regard, if it requires special > knowledge or handling? I don't know but there is one thing I know for sure: Setting up a frame and using `after-make-frame-functions' to add or a change a parameter is madness. Creating a frame mostly means to process frame parameters in a carefully laid out fashion. If, at the end of that, a user decides that some additional parameter should be processed, this may confuse the hell out of that process. Never do that - specify all parameters you need at the time you ask Emacs to create the frame. >> And you cannot augment that alist by additional elements for specific >> buffers? > > Dunno what you mean. It's just like > `special-display-frame-alist' - an alist of frame > parameters. It applies to all special-display > buffers. See above. > `display-buffer-alist' terrifies me. ;-) It's just as terrific as `special-display-regexps'. martin