all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Ignacio Casso <ignaciocasso@hotmail.com>
Cc: larsi@gnus.org, 54371@debbugs.gnu.org
Subject: bug#54371: 29.0.50; read-char does not reset idle timer in some cases
Date: Sun, 13 Mar 2022 21:34:28 +0200	[thread overview]
Message-ID: <83ee35lk8r.fsf@gnu.org> (raw)
In-Reply-To: <PAXPR06MB7760E20F16BB6428F82D3C6FC60E9@PAXPR06MB7760.eurprd06.prod.outlook.com> (message from Ignacio Casso on Sun, 13 Mar 2022 18:45:33 +0100)

> From: Ignacio Casso <ignaciocasso@hotmail.com>
> Cc: Lars Ingebrigtsen <larsi@gnus.org>, 54371@debbugs.gnu.org
> Date: Sun, 13 Mar 2022 18:45:33 +0100
> 
> However, I still think that if not a bug, this is at least inconsistent
> and probably deserving a footnote in the relevant section of the Emacs
> Lisp manual
> (https://www.gnu.org/software/emacs/manual/html_node/elisp/Idle-Timers.html).

I think accessing current-idle-time from an idle time is inherently
problematic: when the idle timer runs and receives input, whether or
not Emacs is idle is ambiguous in principle.  IOW, code which does
that is splitting hair.





  reply	other threads:[~2022-03-13 19:34 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-03-12 23:27 bug#54371: 29.0.50; read-char does not reset idle timer in some cases Ignacio Casso
2022-03-13 10:08 ` Eli Zaretskii
2022-03-13 10:48   ` Ignacio Casso
2022-03-13 15:02     ` Lars Ingebrigtsen
2022-03-13 16:43       ` Eli Zaretskii
2022-03-13 17:45         ` Ignacio Casso
2022-03-13 19:34           ` Eli Zaretskii [this message]
2022-03-13 21:58             ` Ignacio Casso
2022-04-01 18:22               ` Ignacio Casso
2022-04-01 19:36                 ` Eli Zaretskii
2022-04-07 11:42                   ` Ignacio Casso
2022-04-08  6:50                     ` Eli Zaretskii
2022-04-11  6:42                       ` Ignacio Casso
2022-04-11 11:17                         ` Eli Zaretskii

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=83ee35lk8r.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=54371@debbugs.gnu.org \
    --cc=ignaciocasso@hotmail.com \
    --cc=larsi@gnus.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 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.