From: Eric Abrahamsen <eric@ericabrahamsen.net>
To: Noam Postavsky <npostavs@users.sourceforge.net>
Cc: 29518@debbugs.gnu.org
Subject: bug#29518: 27.0.50; Compilation errors grab frame focus
Date: Mon, 15 Jan 2018 16:15:19 -0800 [thread overview]
Message-ID: <87d12amzfs.fsf@ericabrahamsen.net> (raw)
In-Reply-To: <878tczpbpu.fsf@users.sourceforge.net> (Noam Postavsky's message of "Mon, 15 Jan 2018 07:07:09 -0500")
On 01/15/18 07:07 AM, Noam Postavsky wrote:
> Eric Abrahamsen <eric@ericabrahamsen.net> writes:
>
>> On 01/06/18 15:31 PM, Noam Postavsky wrote:
>>> I can't think of anything. If you M-x debug-on-error RET x-focus-frame
>>> RET do you get any hits?
>>
>> Sorry about the slow response...
>>
>> That was an odd recipe, but turning on debug-on-error, then running
>> several varieties of (x-focus-frame (window-frame)), including focusing
>> the current frame or other frames, never did anything other than what I
>> would expect it to -- returning nil when the frame was already focused,
>> and focusing the frame when it wasn't.
>
> Oh, it's odd because I made a thinko, that should have been M-x
> debug-on-entry ...
> ^^^^^
Aha! Turning that on results in nothing happening -- re-running your
earlier recipe for compile/install errors still yanks focus, but does
not enter the debugger. Other frame-switching activity (eg
`helm-projectile-switch-to-buffer') does enter the debugger.
Weird.
Eric
next prev parent reply other threads:[~2018-01-16 0:15 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-01 0:29 bug#29518: 27.0.50; Compilation errors grab frame focus Eric Abrahamsen
2018-01-06 14:50 ` Noam Postavsky
2018-01-06 20:13 ` Eric Abrahamsen
2018-01-06 20:31 ` Noam Postavsky
2018-01-15 4:40 ` Eric Abrahamsen
2018-01-15 12:07 ` Noam Postavsky
2018-01-16 0:15 ` Eric Abrahamsen [this message]
2022-01-23 15:51 ` Lars Ingebrigtsen
2022-01-24 1:04 ` Eric Abrahamsen
2022-01-24 9:42 ` Lars Ingebrigtsen
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=87d12amzfs.fsf@ericabrahamsen.net \
--to=eric@ericabrahamsen.net \
--cc=29518@debbugs.gnu.org \
--cc=npostavs@users.sourceforge.net \
/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).