From: Drew Adams <drew.adams@oracle.com>
To: martin rudalics <rudalics@gmx.at>, 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 20:23:44 +0000 [thread overview]
Message-ID: <SJ0PR10MB54882B7C146580E7BC56D55AF3C69@SJ0PR10MB5488.namprd10.prod.outlook.com> (raw)
In-Reply-To: <2a1f48d7-1dee-3dba-ef69-efa90fc1c786@gmx.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?
Dunno what you mean. (But it sounds like duplicating
the common list, and adding something to the copy.)
> >> 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'.
Well, if you lack it then certainly I do too.
Why doesn't its doc give users a heads-up in this
(unspecified) regard, if it requires special
knowledge or handling?
> > 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?
Dunno what you mean. It's just like
`special-display-frame-alist' - an alist of frame
parameters. It applies to all special-display
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".
`display-buffer-alist' terrifies me. ;-)
> >> 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.
I certainly don't know more than you. And I don't
think I've given the impression that I think I do.
Certainly haven't meant that.
> 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.
Yes, that was my bad. Even without knowing that
that was the problem I should have thought to try
code such as what you suggested.
> 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.
Maybe so, and thanks for the warning. So far, I
have something that seems to work, and I'm not
sure what an alternative way to handle it would
be. I don't mean to take your time in trying to
do that, but I do appreciate your advice.
next prev parent reply other threads:[~2021-08-25 20:23 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
2021-08-25 20:23 ` Drew Adams [this message]
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=SJ0PR10MB54882B7C146580E7BC56D55AF3C69@SJ0PR10MB5488.namprd10.prod.outlook.com \
--to=drew.adams@oracle.com \
--cc=13336@debbugs.gnu.org \
--cc=larsi@gnus.org \
--cc=rudalics@gmx.at \
/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 public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).