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: Wed, 25 Aug 2021 09:48:29 +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> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: quoted-printable Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="37311"; 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 Wed Aug 25 09:49:28 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 1mInf6-0009Su-0L for geb-bug-gnu-emacs@m.gmane-mx.org; Wed, 25 Aug 2021 09:49:28 +0200 Original-Received: from localhost ([::1]:50932 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1mInf4-0001Q7-GP for geb-bug-gnu-emacs@m.gmane-mx.org; Wed, 25 Aug 2021 03:49:26 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:42850) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1mInei-0001Mx-Jb for bug-gnu-emacs@gnu.org; Wed, 25 Aug 2021 03:49:05 -0400 Original-Received: from debbugs.gnu.org ([209.51.188.43]:34071) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.90_1) (envelope-from ) id 1mIneg-0007Kw-8x for bug-gnu-emacs@gnu.org; Wed, 25 Aug 2021 03:49:04 -0400 Original-Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1mIneg-0003my-79 for bug-gnu-emacs@gnu.org; Wed, 25 Aug 2021 03:49:02 -0400 X-Loop: help-debbugs@gnu.org Resent-From: martin rudalics Original-Sender: "Debbugs-submit" Resent-CC: bug-gnu-emacs@gnu.org Resent-Date: Wed, 25 Aug 2021 07:49:02 +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.162987772414539 (code B ref 13336); Wed, 25 Aug 2021 07:49:02 +0000 Original-Received: (at 13336) by debbugs.gnu.org; 25 Aug 2021 07:48:44 +0000 Original-Received: from localhost ([127.0.0.1]:45617 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1mIneN-0003mR-TK for submit@debbugs.gnu.org; Wed, 25 Aug 2021 03:48:44 -0400 Original-Received: from mout.gmx.net ([212.227.15.18]:47947) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1mIneK-0003m4-RB for 13336@debbugs.gnu.org; Wed, 25 Aug 2021 03:48:41 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=gmx.net; s=badeba3b8450; t=1629877711; bh=LTzTinFJ/nUkI7kKxgfuBCelzr1gn6USi1I3sON9WPs=; h=X-UI-Sender-Class:Subject:To:Cc:References:From:Date:In-Reply-To; b=hT2Rkkmj0wCMOwo3F50G2os73aJ3uGaRNot+EF52i4SVTq8uxbrfnjNzNR75vVf97 AgUByzYFMxOvj87r+4NX6vQblfFvgUJgWBkX8HoYgygpOXZo1vWSvNMP6VKe2lnHci 92tn7Y7IT1eXiSDcSzxNKkZM6QkTeMtsLwBiU7as= X-UI-Sender-Class: 01bb95c1-4bf8-414a-932a-4f6e2808ef9c Original-Received: from [192.168.1.102] ([212.95.5.185]) by mail.gmx.net (mrgmx004 [212.227.17.190]) with ESMTPSA (Nemesis) id 1MGz1V-1mEcnM230t-00E1cf; Wed, 25 Aug 2021 09:48:31 +0200 In-Reply-To: Content-Language: en-US X-Provags-ID: V03:K1:y74cm/CBs7rBihz5H68FfmzwNK6e4cWqT2Ar6pVYmZxLHO2jp5s Ir3hq98iu0LgyjurtvxRA3ON72o6fNvOqESlyvGkl+XnduCMFneMPHkyl//ySEv6iUDcy7Y lVIIc9bJ7xVKDSi/+uoiRJhVSjWSkB7X0RRaSVxYpNlpRiqhQHFSIV9+z1tv24U7qY6tGT7 2JK3ju95C/g3o0p8ZQUxA== X-UI-Out-Filterresults: notjunk:1;V03:K0:5TG31Uv6NZQ=:YXsV+hMo044PZ3lbU3tLVC JfcQtg0p6nqlOWdHOVh3Ae4fvsZCUJ1iMNIzZ3TebRj2V2OSKm0Tkgi9SocwQnG3vF8UsSgi2 fTxpIVt+nbi3WMRZiXvOGMwR123hHra/UUD5SykEugf7G2DMCxtGTUB5oQhyVFExu6Aynqqq4 dzln2rBKFODG4HnJbMe9bpFHmMP1y1VNPEkZIO8/mvVHKMIkzoO958mDyYr4frDDQAgKCDb16 AymaV3CokTch7HzRIaqIhz4ki8onmRUV1HFQybLFoZ7uj/d3TToEGq3uAJ8EJGVCZVjZ3R2ge PCc8ZQKnmG9MYvdx450gVo0DJWcTrE9VNfp3M2IrJQ0AnGdKgEpgttFXzlFu28lkna3KSS7tK LoIbDp+WqLCka+irI04rOBAmE9MvvKptaAHXSRyLj7Awsk7yqo83k3Zj2sYdgY7DpOpmJteLG HVXpxXaclZWjyV06ye+Wo3snY6DJcie/l2yOHa6MiRtfOk/aJWPErCgKXYcUmC6HSa7uZinwx P8H2NfGt/Qts3My+EmtQHkmMYr4wQC6O39/4tKec8646PB7xtAvMN981URzKmP8Odyp8QfQWp AXFXamR7AztdcWhegaFQBxYzerCCRLmHpkJAXtaDe0/6QR5a9Xuy9gqDL6Ts4tbqC0xcfrIN8 Fvx7PP50/5hXwIhMmuGgo0ZZ29/8NIO/KXbYDk/Ui6g3iQEXWj7DPXiPyvmIty35ZptLLk32T U/C9HfeI/gcFOfRDO1Wvp5vXlwK0xcp268stZQ5aSsYCXvaVz4C817INeLX3Od0GE4I/ocik 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:212585 Archived-At: > I could add a `*Backtrace*' entry to my value of > `special-display-buffer-names', yes, and duplicate the > parameters of `special-display-regexps' but also add > the kludge to work around this bug. What would you have to "duplicate" here? > Is that necessary? I was guessing it would be OK > (and reasonable) to use `after-make-frame-functions'. Using `after-make-frame-functions' requires a certain knowledge of Elisp. >> why on earth don't you use the FRAME-PARAMETERS idiom? > > It's not clear to me what idiom you have in mind. From the doc-string of `special-display-regexps': Alternatively, an element of this list can be specified as (REGEXP FRAME-PARAMETERS), where REGEXP is a regexp as above and FRAME-PARAMETERS an alist of (PARAMETER . VALUE) pairs. =E2=80=98special-display-popup-frame=E2=80=99 will then interpret thes= e pairs as frame parameters when creating a special frame for a buffer whose name matches REGEXP, overriding the corresponding values from =E2=80=98special-display-frame-alist=E2=80=99. >> > Debugging a bit shows that frame parameter `name' for >> > the *Backtrace* frame is indeed "*Backtrace*", >> >> Not at the time `after-make-frame-functions' gets called >> (unless you specified a name for it). > > I see. How would I do that? I don't control how or > when the frame gets created. Which means that you have to deal with a situation handled by `special-display-regexps' once and `display-buffer-alist' now. >> If you insist on using `after-make-frame-functions', >> the following should work. > > I don't insist. I was trying to interpret what you > suggested. Should I not use `after-make-frame-functions' > for some reason (why)? Because using `after-make-frame-functions' requires a certain knowledge of Elisp. martin