From: Lars Ingebrigtsen <larsi@gnus.org>
To: "Peter Münster" <pm@a16n.net>
Cc: 49997@debbugs.gnu.org
Subject: bug#49997: 27.2; idle-time reset when switching desktop-page
Date: Sun, 15 Aug 2021 22:16:34 +0200 [thread overview]
Message-ID: <874kbqihul.fsf@gnus.org> (raw)
In-Reply-To: <87y292h3yd.fsf@a16n.net> ("Peter Münster"'s message of "Sun, 15 Aug 2021 22:02:02 +0200")
Peter Münster <pm@a16n.net> writes:
> On Wed, Aug 11 2021, Peter Münster wrote:
>
>> Emacs is on page 2-2 and even when emacs is not affected by the
>> page-change (for example from 1-1 to 1-2), the idle time is reset.
>
> Just to be clear: That means, that Emacs is already out of focus
> *before* the page change. And after the page change too.
Oh, then we're not seeing the exact same behaviour -- when I switch
virtual desktops in Gnome (where Emacs isn't on any of them), then idle
time isn't reset.
But I guess it's window manager dependent.
Do you get focus-in events when you do the changing between pages in the
way you describe? Try putting something on focus-in-hook -- that should
be run when Emacs gets a focus-in event.
--
(domestic pets only, the antidote for overdose, milk.)
bloggy blog: http://lars.ingebrigtsen.no
next prev parent reply other threads:[~2021-08-15 20:16 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
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 [this message]
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
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=874kbqihul.fsf@gnus.org \
--to=larsi@gnus.org \
--cc=49997@debbugs.gnu.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 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).