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 21:41:03 +0200 Message-ID: <2a1f48d7-1dee-3dba-ef69-efa90fc1c786@gmx.at> 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: 7bit Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="11022"; 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 21:42:09 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 1mIymn-0002ji-Cq for geb-bug-gnu-emacs@m.gmane-mx.org; Wed, 25 Aug 2021 21:42:09 +0200 Original-Received: from localhost ([::1]:48506 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1mIymm-00031e-4U for geb-bug-gnu-emacs@m.gmane-mx.org; Wed, 25 Aug 2021 15:42:08 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:47300) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1mIymg-00031H-45 for bug-gnu-emacs@gnu.org; Wed, 25 Aug 2021 15:42:02 -0400 Original-Received: from debbugs.gnu.org ([209.51.188.43]:36365) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.90_1) (envelope-from ) id 1mIymf-0008Fg-SN for bug-gnu-emacs@gnu.org; Wed, 25 Aug 2021 15:42:01 -0400 Original-Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1mIymf-0007SG-Lm for bug-gnu-emacs@gnu.org; Wed, 25 Aug 2021 15:42: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: Wed, 25 Aug 2021 19:42: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.162992047928601 (code B ref 13336); Wed, 25 Aug 2021 19:42:01 +0000 Original-Received: (at 13336) by debbugs.gnu.org; 25 Aug 2021 19:41:19 +0000 Original-Received: from localhost ([127.0.0.1]:47910 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1mIylz-0007RF-53 for submit@debbugs.gnu.org; Wed, 25 Aug 2021 15:41:19 -0400 Original-Received: from mout.gmx.net ([212.227.15.18]:46503) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1mIylv-0007R1-VK for 13336@debbugs.gnu.org; Wed, 25 Aug 2021 15:41:17 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=gmx.net; s=badeba3b8450; t=1629920465; bh=w663YRRjwo8Ij0tVkR0CJgp8u7D8f53V6NP9lIlcS+0=; h=X-UI-Sender-Class:Subject:To:Cc:References:From:Date:In-Reply-To; b=G04jxj7/9wKOgY/Gq5iOJ/RvNZbt5e1KHobBy8/sYyRa1XYSTMuQnMK9lyIwZDQjG V4sLF8nx7DIzyznPKiqx7KkxRYfFvaXRXNDEPvcFq+7Upz+XUIDyhkyKM+NcckLRko oUEUEkwxzCnKaCTPM57fe+fSVvNw2/NouoYZIuCk= X-UI-Sender-Class: 01bb95c1-4bf8-414a-932a-4f6e2808ef9c Original-Received: from [192.168.1.100] ([213.142.97.162]) by mail.gmx.net (mrgmx005 [212.227.17.190]) with ESMTPSA (Nemesis) id 1M4JmN-1mJFsu1G7N-000JD4; Wed, 25 Aug 2021 21:41:05 +0200 In-Reply-To: Content-Language: en-US X-Provags-ID: V03:K1:XA+ycbKzAF+8xuO3ij7JU24KcgGfAtq5hP1EHuBnae6yrpuEjXX IAVjRdoqtmcVmx/2YzPooA8rYOZOLHusvI6bjlnU+dkKEuIPHJ7uQFGnn13lB/W2F08XIFk 5mPk4b6DObPZCIfaeBhP5sALDBmbyCc+YvrmmfFkTkxb9W77GPl1HP1gPoUu9lZ9DEg0CFn LTClsa/4/VZlBWcKQBX0w== X-UI-Out-Filterresults: notjunk:1;V03:K0:meZJ8V7XKAM=:53gIVxo8ymLkDGAtLJAvY8 qfxXZDEwHrX5YEsk5h0FtFmqihD0n8XevG/FBB6Rx7ECaCqvTeISPe1iO/K1ZRBKBKDqe3JB/ Y79Ry0OfQ1nY1xKrsTr5p7NWTxom7UeBD9Hd+43dwPzlFnKthdxNH1+50PFuNpFOaQaiE1sav IwZplakbgyfiG0UIQ+Mt04YLnZG6Wtg1raVjBnNW2oi29K52+1hWehq7JoDKLSwA0IouFYjVl hlL+ZTnapEx8zFrYhTr5lsfmS1GVxKpsCt9ee3AkerbjI3iW+qgbDW5ttP8O7QPvlSdHtC8ZH gIg3F6zpZwr7j1lyE/U2jAY1W4suZfKBb12o/T2dBdSOoPVjzARcmU/7hJM8Ks4lsPegZcw4h 733o1syF4prfbZItpXbGQgSbF6xXVvJDAa8pX3Kw+yCncMNRITK6ONvOgkX+KrSy18uhiqBH3 dM+6ZCTiaqBxXxFkyHNzO6eosgkQ9C4pbizaWHGrjCKnVj4YVYNrHFnHyF20GmE72DJ7tho+A /bht8eq3f/qy3mtgT9YB5hmqDeFSUf8MeTYcBpTqcrZqyF6udgKMvXXRA+oyu/md8EpQSkDWc mFgPfmQj4zzHDMvX/oSVL3bOT9YVKGdx+9nZNRqXTy4u9/oSCNMtz17J6VAAxtmyCLFR2QNOs SHq/DlB3U2Qd9MOEYbYPOauN9xAmVsHU3vdjtENg2tR4vfDMGOD3sadPmyx6sD2HGQsWVagb6 r2wsDzJZRGPmS3fHDsgzfiyt0e4zfQSTsfMhdM3jVO8u6v3FwP3gap52Vx6FCj8Fstcq4427 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:212672 Archived-At: >> What would you have to "duplicate" here? > > "the parameters of `special-display-regexps'". > > I want the *Backtrace* frame to look and act like > frames for other buffers whose names also match > that regexp. Why can't you add the `no-other-frame' parameter to that common list for the *Backtrace* buffer alone? >> Using `after-make-frame-functions' requires a >> certain knowledge of Elisp. > > Meaning what - what "certain knowledge"? I guess > you're suggesting that I lack it, so it would be > good to know what it is. I lack it and that's why I neither use nor recommend using `after-make-frame-functions'. > I define the frame parameters separately, with a > user option, `1on1-special-display-frame-alist' > (which others besides myself use). The setting of > just `special-display-regexps' is in my init file, > for myself alone. > > Put differently, I separate the appearance of > special-display frames from a criterion (in this > case buffer-name-matching-regexp) for which buffers > get special-display frames. > > That's also the purpose, presumably, of option > `special-display-frame-alist' (which option > `1on1-special-display-frame-alist' augments). And you cannot augment that alist by additional elements for specific buffers? >> > 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. > > Sorry, I don't know what you're referring to. > Could you be specific? These options have been provided to control the display of buffers where the user does not "control how or when the frame gets created". >> Because using `after-make-frame-functions' requires >> a certain knowledge of Elisp. > > See above. > > Is there some specific caveat about using this hook, > which is not in the Elisp manual? Nothing particular > is said in the manual about the hook. > > What special Elisp knowledge is required? Why the > vague formulation (repeated) of "a certain knowledge"? > It's not clear to me what you're suggesting. If you understand how frame names, explicit names and titles are set up, you know much more than I do. But in that case you should not have made the wrong assumption about the name of the *Backtrace* frame at the time `after-make-frame-functions' is run. So what I am suggesting is that since we both don't know all too much about this subject, it might be better for us to avoid using `after-make-frame-functions' in code we write. martin