From: Peter Neidhardt <pe.neidhardt@googlemail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 28945@debbugs.gnu.org
Subject: bug#28945: 25.2; desktop auto save timer does not work
Date: Mon, 23 Oct 2017 20:28:34 +0100 [thread overview]
Message-ID: <871slt64v1.fsf@gmail.com> (raw)
In-Reply-To: <83376bawts.fsf@gnu.org>
Eli Zaretskii <eliz@gnu.org> writes:
>> > What this boils down to is that every automatic desktop-save produces
>> > an annoying "hiccup" in Emacs responsiveness.
>>
>> It's an idle timer, so if Emacs is idle, i.e. the user does not do
>> anything, how to you notice the hiccup?
>
> I notice it when I resume typing during the time desktop.el
> auto-saves. The response to my typing is "sluggish", because once the
> timer function starts running, it runs to completion, before Emacs
> notices I typed something and responds.
Correct me if I'm wrong:
- If you keep using Emacs for hours (that is "typing/moving the point
around") without taking a 30 sec break, then the timer won't trigger
the desktop saving. Right?
- The sluggishness would only be noticed if you happen to do nothing for
more than `desktop-auto-save-timeout' but for less than
desktop-auto-save-timeout + "time needed for saving". It seems
improbable that this happens _often_.
- I've used desktop-mode for years and I've never noticed any
sluggishness as it takes less than a fraction of a second to save.
I've had crappy computers, but admitedly most of them had an SSD. My
current timeout is 5 and I don't see any performance impact even on a
bad computer with an even worse HDD.
Either way, the default value is not that important since every user is free
to change the value. What is more important is to document it
properly. Something in the line of:
> If you experience any irresponsiveness everytime desktop gets saved,
> increase the timeout.
> If not, it's safe to have it around 10.
What do you think?
Cheers!
--
Peter Neidhardt
The difference between legal separation and divorce is that legal
separation gives the man time to hide his money.
next prev parent reply other threads:[~2017-10-23 19:28 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-22 16:19 bug#28945: 25.2; desktop auto save timer does not work Peter Neidhardt
2017-10-22 17:11 ` Eli Zaretskii
2017-10-22 17:41 ` Peter Neidhardt
2017-10-22 17:58 ` Eli Zaretskii
2017-10-23 19:28 ` Peter Neidhardt [this message]
2017-10-23 19:35 ` Eli Zaretskii
2017-10-23 19:57 ` Peter Neidhardt
2017-10-23 20:02 ` Eli Zaretskii
2017-10-24 21:46 ` Richard Stallman
2017-10-25 2:32 ` Eli Zaretskii
2017-10-26 3:42 ` Richard Stallman
2017-10-26 10:01 ` Pierre Neidhardt
2017-10-27 2:42 ` Richard Stallman
2017-10-27 9:12 ` Eli Zaretskii
2017-10-28 21:49 ` Richard Stallman
2017-10-26 15:53 ` Eli Zaretskii
2017-10-26 16:19 ` Drew Adams
2017-10-26 17:10 ` Eli Zaretskii
2017-10-26 18:28 ` Drew Adams
2017-10-26 18:46 ` Eli Zaretskii
2017-10-28 12:12 ` Eli Zaretskii
2017-11-05 16:18 ` Peter Neidhardt
2017-11-11 9:58 ` Eli Zaretskii
2017-11-11 11:59 ` Peter Neidhardt
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=871slt64v1.fsf@gmail.com \
--to=pe.neidhardt@googlemail.com \
--cc=28945@debbugs.gnu.org \
--cc=eliz@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).