From: Eli Zaretskii <eliz@gnu.org>
To: Peter Neidhardt <pe.neidhardt@googlemail.com>
Cc: 28945@debbugs.gnu.org
Subject: bug#28945: 25.2; desktop auto save timer does not work
Date: Sun, 22 Oct 2017 20:58:39 +0300 [thread overview]
Message-ID: <83376bawts.fsf@gnu.org> (raw)
In-Reply-To: <87efpvulk1.fsf@gmail.com> (message from Peter Neidhardt on Sun, 22 Oct 2017 18:41:50 +0100)
> From: Peter Neidhardt <pe.neidhardt@googlemail.com>
> Cc: 28945@debbugs.gnu.org
> Date: Sun, 22 Oct 2017 18:41:50 +0100
>
> 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.
next prev parent reply other threads:[~2017-10-22 17:58 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 [this message]
2017-10-23 19:28 ` Peter Neidhardt
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=83376bawts.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=28945@debbugs.gnu.org \
--cc=pe.neidhardt@googlemail.com \
/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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.