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: Fri, 01 Apr 2022 22:36:12 +0300 [thread overview]
Message-ID: <83sfqw4mvn.fsf@gnu.org> (raw)
In-Reply-To: <PAXPR06MB7760C2EDA3F27941058DF5BDC6E09@PAXPR06MB7760.eurprd06.prod.outlook.com> (message from Ignacio Casso on Fri, 01 Apr 2022 20:22:00 +0200)
> From: Ignacio Casso <ignaciocasso@hotmail.com>
> Cc: larsi@gnus.org, 54371@debbugs.gnu.org
> Date: Fri, 01 Apr 2022 20:22:00 +0200
>
>
> Hi again,
>
> Since my other bug report has already been closed, I've picked up again
> the next one in my pending list, which was this one.
>
> > However, I still think this should be documented somewhere. The only
> > thing I found was a comment in keyboard.c, and that was only after you
> > pointed me to the right email thread.
>
> After searching again, I've seen that this behavior is indeed documented
> in the section of the Emacs Lisp manual describing `read-event'.
>
> >
> > And this is not only about the use of read-event inside timer
> > functions. Currently the Idle Timers section of the manual would make
> > any reader think that these two forms would produce the output "A\nB" if
> > the user takes a few seconds to input a character, but only the first
> > one would.
> >
> > (progn
> > (run-with-idle-timer 1 nil (lambda () (message "A")))
> > (read-char "Please wait for 2 seconds" nil nil)
> > (message "B"))
> >
> > (progn
> > (run-with-idle-timer 1 nil (lambda () (message "A")))
> > (read-char "Please wait for 2 seconds" nil 20)
> > (message "B"))
> >
> > So as I see it, the manual is incorrect right now, or at best incomplete
> > or ambiguous, and a footnote could not hurt. What do you think?
>
> So unless you see a problem with this, you can close this bug report. Or
> if you want, I can send a patch to update that section of the manual
> with a footnote, and maybe some other relevant docstrings.
Please send the patch, and let's take it from there.
Thanks.
next prev parent reply other threads:[~2022-04-01 19:36 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
2022-03-13 21:58 ` Ignacio Casso
2022-04-01 18:22 ` Ignacio Casso
2022-04-01 19:36 ` Eli Zaretskii [this message]
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
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=83sfqw4mvn.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 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).