unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: Cecil Westerhof <Cecil@decebal.nl>
To: help-gnu-emacs@gnu.org
Subject: Re: Function write-region resets idle time
Date: Thu, 11 Jan 2018 20:14:15 +0100	[thread overview]
Message-ID: <87a7xki4xk.fsf@munus.decebal.nl> (raw)
In-Reply-To: mailman.7219.1515693952.27995.help-gnu-emacs@gnu.org

Eli Zaretskii <eliz@gnu.org> writes:

>> From: Cecil Westerhof <Cecil@decebal.nl>
>> Date: Thu, 11 Jan 2018 18:43:53 +0100
>> 
>> I found a strange problem: write-region resets idle-time. But only
>> after the calling function has returned.
>
> ??? Any Lisp you run resets idle-time.  Idleness starts when Emacs
> gets to its command loop and finds that there's no pending input.  It
> ends when there's some input event that causes the command loop to run
> the Lisp interpreter.  In your case, the input event is supplied by
> the timer you set up.
>
> So why is what you discovered surprising, let alone a problem?  Am I
> missing something?

The definition of idle:
    Emacs becomes idle when it starts waiting for user input, and it
    remains idle until the user provides some input. If a timer is set
    for five seconds of idleness, it runs approximately five seconds
    after Emacs first becomes idle.

And to make it even more clear:
    Even if repeat is non-nil, this timer will not run again as long
    as Emacs remains idle, because the duration of idleness will
    continue to increase and will not go down to five seconds again.

So the running of the function should NOT reset idle time.


The behaviour changed (for me) on the 19th of December.

And if what you say would be true: then there should be also no
difference if my function uses write-region or not. But there is.
Without write-region idle time is NOT reset. With write-region
idle-time IS reset.

I certainly find it surprising that write-region does something else
as all other functions with idle time.

-- 
Cecil Westerhof
Senior Software Engineer
LinkedIn: http://www.linkedin.com/in/cecilwesterhof


  parent reply	other threads:[~2018-01-11 19:14 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-01-11 17:43 Function write-region resets idle time Cecil Westerhof
2018-01-11 18:05 ` Eli Zaretskii
     [not found] ` <mailman.7219.1515693952.27995.help-gnu-emacs@gnu.org>
2018-01-11 19:14   ` Cecil Westerhof [this message]
2018-01-11 19:38     ` Cecil Westerhof
2018-01-11 20:48       ` Eli Zaretskii
     [not found]       ` <mailman.7229.1515703701.27995.help-gnu-emacs@gnu.org>
2018-01-11 21:24         ` Cecil Westerhof
2018-01-11 19:40     ` Stefan Monnier
     [not found]     ` <mailman.7223.1515699746.27995.help-gnu-emacs@gnu.org>
2018-01-11 20:45       ` Cecil Westerhof
2018-01-12 23:08 ` Cecil Westerhof

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=87a7xki4xk.fsf@munus.decebal.nl \
    --to=cecil@decebal.nl \
    --cc=help-gnu-emacs@gnu.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.
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).