From: Alan Mackenzie <acm@muc.de>
To: Stefan Monnier <monnier@IRO.UMontreal.CA>
Cc: emacs-devel@gnu.org
Subject: Re: [Emacs-diffs] master 7cfe2dc: In edebug in GUIs, move focus to the selected frame.
Date: Fri, 19 Oct 2018 18:49:17 +0000 [thread overview]
Message-ID: <20181019184916.GA6639@ACM> (raw)
In-Reply-To: <jwvd0s5stt8.fsf-monnier+emacsdiffs@gnu.org>
Hello, Stefan.
On Fri, Oct 19, 2018 at 13:58:44 -0400, Stefan Monnier wrote:
> Hi Alan,
> > (edebug-pop-to-buffer edebug-buffer)
> > + (edebug-focus-frame (window-frame (selected-window)))
> [...]
> > - (edebug-pop-to-buffer edebug-buffer (car edebug-window-data)))))
> > + (edebug-pop-to-buffer edebug-buffer (car edebug-window-data))
> > + (edebug-focus-frame (window-frame (selected-window))))))
> [...]
> > - (edebug-pop-to-buffer edebug-eval-buffer))
> > + (edebug-pop-to-buffer edebug-eval-buffer)
> > + (edebug-focus-frame (window-frame (selected-window))))
> Maybe edebug-pop-to-buffer should call edebug-focus-frame?
I thought about that, but in the end decided that could be a bit heavy
for when information is only being displayed, i.e. in
edebug-trace-display. Maybe putting the call in e-pop-to-buffer would
indeed be better. But I think edebug-trace-display would have then to
call edebug-focus-frame explicitly after re-selecting the original
window.
This bit of the code surely originates from the time before frames were
implemented.
> Stefan
--
Alan Mackenzie (Nuremberg, Germany).
next prev parent reply other threads:[~2018-10-19 18:49 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20181019175416.10874.88992@vcs0.savannah.gnu.org>
[not found] ` <20181019175418.27D6920407@vcs0.savannah.gnu.org>
2018-10-19 17:58 ` [Emacs-diffs] master 7cfe2dc: In edebug in GUIs, move focus to the selected frame Stefan Monnier
2018-10-19 18:49 ` Alan Mackenzie [this message]
2018-10-19 19:07 ` Stefan Monnier
2018-10-19 19:21 ` Alan Mackenzie
2018-10-19 19:39 ` Davis Herring
2018-10-19 19:50 ` Alan Mackenzie
2018-10-19 21:12 ` Stefan Monnier
2018-10-20 9:41 ` Alan Mackenzie
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=20181019184916.GA6639@ACM \
--to=acm@muc.de \
--cc=emacs-devel@gnu.org \
--cc=monnier@IRO.UMontreal.CA \
/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).