From: Eli Zaretskii <eliz@gnu.org>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: 49997@debbugs.gnu.org, pm@a16n.net
Subject: bug#49997: 27.2; idle-time reset when switching desktop-page
Date: Sun, 15 Aug 2021 19:46:52 +0300 [thread overview]
Message-ID: <838s12ac5f.fsf@gnu.org> (raw)
In-Reply-To: <87y292isxp.fsf@gnus.org> (message from Lars Ingebrigtsen on Sun, 15 Aug 2021 18:17:06 +0200)
> From: Lars Ingebrigtsen <larsi@gnus.org>
> Cc: pm@a16n.net, 49997@debbugs.gnu.org, rudalics@gmx.at
> Date: Sun, 15 Aug 2021 18:17:06 +0200
>
> static void
> x_focus_changed (int type, int state, struct x_display_info *dpyinfo, struct frame *frame, struct input_event *bufp)
> {
> if (type == FocusIn)
> {
> if (dpyinfo->x_focus_event_frame != frame)
> {
> x_new_focus_frame (dpyinfo, frame);
> dpyinfo->x_focus_event_frame = frame;
> bufp->kind = FOCUS_IN_EVENT;
> XSETFRAME (bufp->frame_or_window, frame);
> }
>
> frame->output_data.x->focus_state |= state;
> [...]
> else if (type == FocusOut)
> {
> frame->output_data.x->focus_state &= ~state;
>
> So we lose focus and then get it back, and that makes Emacs unidle.
If we get focus in/out events when the user changes the page, then
it's the correct behavior.
> Which is arguably correct behaviour, but I can see the case for changing
> that. I mean, the user hasn't done anything inside Emacs.
The user switched off the Emacs frame, which is something, not
nothing.
Why exactly does the stop of idleness present a problem in this case?
And if it does present a problem, cannot the OP use
after-focus-change-function to restart the idleness?
next prev parent reply other threads:[~2021-08-15 16:46 UTC|newest]
Thread overview: 45+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-11 8:42 bug#49997: 27.2; idle-time reset when switching desktop-page Peter Münster
2021-08-11 11:32 ` Lars Ingebrigtsen
2021-08-11 12:00 ` Eli Zaretskii
2021-08-15 14:18 ` Lars Ingebrigtsen
2021-08-15 14:29 ` Eli Zaretskii
2021-08-15 14:36 ` Lars Ingebrigtsen
2021-08-15 14:44 ` Eli Zaretskii
2021-08-15 14:59 ` Lars Ingebrigtsen
2021-08-15 16:17 ` Lars Ingebrigtsen
2021-08-15 16:46 ` Eli Zaretskii [this message]
2021-08-15 16:49 ` Eli Zaretskii
2021-08-15 17:12 ` Lars Ingebrigtsen
2021-08-15 17:39 ` Eli Zaretskii
2021-08-15 16:54 ` Eli Zaretskii
2021-08-15 17:03 ` Eli Zaretskii
2021-08-15 17:09 ` Lars Ingebrigtsen
2021-08-18 8:02 ` martin rudalics
2021-08-18 9:16 ` Peter Münster
2021-08-18 11:36 ` Eli Zaretskii
2021-08-18 14:36 ` Lars Ingebrigtsen
2021-08-20 8:19 ` martin rudalics
2021-08-20 10:43 ` Eli Zaretskii
2021-08-22 8:24 ` martin rudalics
2021-08-22 9:33 ` Eli Zaretskii
2021-08-22 21:41 ` Lars Ingebrigtsen
2021-10-11 9:40 ` Lars Ingebrigtsen
2021-10-11 11:11 ` martin rudalics
2021-10-11 11:20 ` Lars Ingebrigtsen
2021-10-12 8:11 ` martin rudalics
2021-10-11 11:33 ` Peter Münster
2021-10-12 8:11 ` martin rudalics
2021-08-15 20:02 ` Peter Münster
2021-08-15 20:16 ` Lars Ingebrigtsen
2021-08-16 7:22 ` Peter Münster
2021-08-16 11:43 ` Lars Ingebrigtsen
2021-08-16 11:54 ` Eli Zaretskii
2021-08-16 15:51 ` Peter Münster
2021-08-16 15:55 ` Eli Zaretskii
2021-08-16 16:42 ` Peter Münster
2021-08-16 16:49 ` Eli Zaretskii
2021-08-16 17:10 ` Peter Münster
2021-08-16 17:21 ` Eli Zaretskii
2021-08-16 17:47 ` Peter Münster
2021-08-16 18:08 ` Eli Zaretskii
2021-08-16 19:54 ` Peter Münster
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=838s12ac5f.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=49997@debbugs.gnu.org \
--cc=larsi@gnus.org \
--cc=pm@a16n.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 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.