From: martin rudalics <rudalics@gmx.at>
To: Drew Adams <drew.adams@oracle.com>, Lars Ingebrigtsen <larsi@gnus.org>
Cc: "13336@debbugs.gnu.org" <13336@debbugs.gnu.org>
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 [thread overview]
Message-ID: <2a1f48d7-1dee-3dba-ef69-efa90fc1c786@gmx.at> (raw)
In-Reply-To: <SJ0PR10MB5488895821941727F4B6E32FF3C69@SJ0PR10MB5488.namprd10.prod.outlook.com>
>> 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
next prev parent reply other threads:[~2021-08-25 19:41 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-02 18:13 bug#13336: 24.3.50; `next-frame' should not choose a frame (e.g. *Backtrace*) that did not exist when it was invoked Drew Adams
2017-01-30 6:33 ` npostavs
2017-01-30 14:32 ` Drew Adams
2017-01-31 3:22 ` npostavs
2021-08-23 14:37 ` bug#13336: `next-frame' should not choose the *Backtrace* frame while debugging Lars Ingebrigtsen
2021-08-23 15:20 ` bug#13336: [External] : " Drew Adams
2021-08-23 16:06 ` martin rudalics
2021-08-23 17:41 ` Drew Adams
2021-08-24 9:41 ` martin rudalics
2021-08-24 15:49 ` Drew Adams
2021-08-24 17:41 ` martin rudalics
2021-08-24 20:02 ` Drew Adams
2021-08-25 7:48 ` martin rudalics
2021-08-25 15:27 ` Drew Adams
2021-08-25 19:41 ` martin rudalics [this message]
2021-08-25 20:23 ` Drew Adams
2021-08-26 7:53 ` martin rudalics
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=2a1f48d7-1dee-3dba-ef69-efa90fc1c786@gmx.at \
--to=rudalics@gmx.at \
--cc=13336@debbugs.gnu.org \
--cc=drew.adams@oracle.com \
--cc=larsi@gnus.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.