From: Cecil Westerhof <Cecil@decebal.nl>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 30080@debbugs.gnu.org, monnier@IRO.UMontreal.CA
Subject: bug#30080: 24.5; write-region can reset idle time
Date: Fri, 12 Jan 2018 11:36:15 +0100 [thread overview]
Message-ID: <874lnr8iu8.fsf@munus.decebal.nl> (raw)
In-Reply-To: <83r2qv30i6.fsf@gnu.org> (Eli Zaretskii's message of "Fri, 12 Jan 2018 11:11:13 +0200")
Eli Zaretskii <eliz@gnu.org> writes:
>> From: Cecil Westerhof <Cecil@decebal.nl>
>> Date: Fri, 12 Jan 2018 02:36:52 +0100
>> Cc: 30080@debbugs.gnu.org
>>
>> Also (desktop-save-mode 1) has the same effect. When I do not have
>> (global-auto-revert-mode 1), but I do have (desktop-save-mode 1), then
>> also write-region will reset idle time.
>
> desktop-save-mode writes the desktop file from time to time, and it
> uses an idle timer, so I think this explains that.
I have two problems with that:
- I do not think that it is done every minute, or less. And the reset
is done on the moment of the write-region of my command. So does not
directly relate to the writing of the desktop file.
- Before 19 December I did not have this behaviour. So it started
after an update. It did not work like this for more as five years,
but started the 19th of December 2017.
--
Cecil Westerhof
Senior Software Engineer
M Cecil@Decebal.nl
LinkedIn: http://www.linkedin.com/in/cecilwesterhof
next prev parent reply other threads:[~2018-01-12 10:36 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-11 21:00 bug#30080: 24.5; write-region can reset idle time Cecil Westerhof
2018-01-11 23:49 ` Stefan Monnier
2018-01-12 1:36 ` Cecil Westerhof
2018-01-12 9:11 ` Eli Zaretskii
2018-01-12 10:36 ` Cecil Westerhof [this message]
2018-01-12 13:53 ` Eli Zaretskii
2018-01-12 14:37 ` Cecil Westerhof
2018-01-12 16:51 ` Glenn Morris
2018-01-12 17:10 ` Cecil Westerhof
2018-01-12 18:22 ` Stefan Monnier
2018-01-12 22:59 ` Cecil Westerhof
2018-01-12 14:56 ` Stefan Monnier
2018-01-12 15:11 ` 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=874lnr8iu8.fsf@munus.decebal.nl \
--to=cecil@decebal.nl \
--cc=30080@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=monnier@IRO.UMontreal.CA \
/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).