unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Alan Mackenzie <acm@muc.de>
To: emacs-devel@gnu.org
Subject: Re: Edebug, with Elisp source in different frame - Edebug doesn't select the source window.
Date: Wed, 17 Oct 2018 16:22:53 +0000	[thread overview]
Message-ID: <20181017162253.GD4753@ACM> (raw)
In-Reply-To: <20181017142226.GC4753@ACM>

Hello, Emacs.

On Wed, Oct 17, 2018 at 14:22:26 +0000, Alan Mackenzie wrote:
> Before I submit a bug report for this, I wonder if I'm doing something
> silly.

> In a GUI Emacs (26.1 or master), instrument a function for edebug with
> C-u C-M-x in frame F1.  From a different frame, F2, cause this function
> to be called, thus entering edebug.  F2 is still selected.  Surely edebug
> should have selected F1?

> Note that in a text terminal, F1 gets selected as expected.  (Normally I
> run Emacs in a text terminal.)

> Does anybody have any ideas why this is happening to me in a GUI
> environment?  Do other people see the same?  Why has nobody else
> submitted a bug report for this?  Anything else?

I've found the answer, I think.  Edebug is using select-window to select
the frame.  What select-window doesn't do is to shift the X-Window focus.
For that, one needs to call select-frame-set-input-focus, something which
the current incarnation of edebug fails to do.

My first experimentation with s-f-set-i-focus indicates this is the
problem.  I will come up with a patch.

-- 
Alan Mackenzie (Nuremberg, Germany).



  reply	other threads:[~2018-10-17 16:22 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-10-17 14:22 Edebug, with Elisp source in different frame - Edebug doesn't select the source window Alan Mackenzie
2018-10-17 16:22 ` Alan Mackenzie [this message]
2018-10-18 11:08   ` Edebug, with Elisp source in different frame - Edebug doesn't select the source window. [PATCH] Alan Mackenzie
2018-10-18 14:26     ` Should FOCUS_OUT_EVENT be ignored for the purposes of input-pending-p? [was: Edebug, with Elisp source in different frame...] Alan Mackenzie
2018-10-18 16:28       ` Stefan Monnier

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=20181017162253.GD4753@ACM \
    --to=acm@muc.de \
    --cc=emacs-devel@gnu.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 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).