From: martin rudalics <rudalics@gmx.at>
To: Juri Linkov <juri@jurta.org>
Cc: rms@gnu.org, emacs-devel@gnu.org
Subject: Re: desktop.el: autosave?
Date: Thu, 06 Dec 2007 00:09:24 +0100 [thread overview]
Message-ID: <47572FA4.4080207@gmx.at> (raw)
In-Reply-To: <87d4tk22dz.fsf@jurta.org>
>>Wouldn't it be sufficient to have one idle timer which triggers
>>auto-saving only if some timeout has elapsed since the last auto-save
>>of the desktop?
>
>
> It seems this is not possible with idle timers because they use timeout
> elapsed since the last user input, not the last time they run.
Ahh no. I meant using an extra variable which records the last autosave
date. Whenever the routine triggered by the idle timer detects that the
period (one hour ...) has elapsed (by comparing that variable's value
with the present time) it does autosave and reset that variable. This
would only fail when an idle time starts before the autosave timeout has
expired and terminates long after that.
next prev parent reply other threads:[~2007-12-05 23:09 UTC|newest]
Thread overview: 56+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <alpine.DEB.0.99999.0711301407250.4037@localhost.localdomain>
2007-11-30 23:35 ` desktop.el: autosave? Richard Stallman
2007-12-01 0:35 ` Juri Linkov
2007-12-01 23:41 ` Richard Stallman
2007-12-03 22:57 ` Juri Linkov
2007-12-04 7:39 ` martin rudalics
2007-12-05 2:57 ` Richard Stallman
2007-12-05 9:02 ` martin rudalics
2007-12-05 22:28 ` Juri Linkov
2007-12-05 23:09 ` martin rudalics [this message]
2007-12-05 23:41 ` Juri Linkov
2007-12-06 15:12 ` Richard Stallman
2007-12-06 2:11 ` Richard Stallman
2007-12-06 23:29 ` Juri Linkov
2007-12-04 16:55 ` Richard Stallman
2007-12-06 14:58 ` Reuben Thomas
2007-12-06 15:38 ` tomas
2007-12-06 15:47 ` Reuben Thomas
2007-12-06 23:28 ` Juri Linkov
2007-12-06 23:44 ` Reuben Thomas
2007-12-07 0:03 ` Juri Linkov
2007-12-07 2:48 ` Stefan Monnier
2007-12-09 20:35 ` Reuben Thomas
2007-12-10 0:27 ` Juri Linkov
2007-12-10 0:35 ` Reuben Thomas
2007-12-10 0:50 ` Drew Adams
2007-12-10 0:59 ` Juri Linkov
2007-12-10 1:10 ` Reuben Thomas
2007-12-10 3:03 ` Stefan Monnier
2007-12-10 22:01 ` Reuben Thomas
2007-12-10 23:55 ` Juri Linkov
2007-12-11 0:10 ` Reuben Thomas
2007-12-11 0:23 ` Juri Linkov
2007-12-11 0:42 ` Reuben Thomas
2013-04-10 1:36 ` Reuben Thomas
2013-04-10 7:05 ` Juri Linkov
2013-04-10 10:57 ` Reuben Thomas
2013-04-11 8:29 ` Juri Linkov
2013-04-11 11:04 ` Reuben Thomas
2013-04-27 20:57 ` Juri Linkov
2007-12-10 22:02 ` Reuben Thomas
2007-12-10 22:12 ` Drew Adams
2007-12-10 22:16 ` Reuben Thomas
2007-12-10 23:57 ` Juri Linkov
2007-12-11 0:02 ` Reuben Thomas
2007-12-11 0:23 ` Juri Linkov
2007-12-11 0:48 ` Reuben Thomas
2007-12-11 19:01 ` Richard Stallman
2007-12-12 0:50 ` Reuben Thomas
2007-12-12 22:53 ` Richard Stallman
2007-12-12 23:59 ` Juri Linkov
2007-12-14 10:10 ` Richard Stallman
2007-12-07 2:47 ` Stefan Monnier
2007-12-07 17:18 ` Richard Stallman
2007-12-03 21:14 ` Reuben Thomas
2007-12-03 22:57 ` Juri Linkov
2007-12-06 14:56 ` Reuben Thomas
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=47572FA4.4080207@gmx.at \
--to=rudalics@gmx.at \
--cc=emacs-devel@gnu.org \
--cc=juri@jurta.org \
--cc=rms@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.
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).