From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!.POSTED!not-for-mail From: Peter Neidhardt Newsgroups: gmane.emacs.bugs Subject: bug#28945: 25.2; desktop auto save timer does not work Date: Mon, 23 Oct 2017 20:28:34 +0100 Message-ID: <871slt64v1.fsf@gmail.com> References: <87k1znuphh.fsf@gmail.com> <8360b7ayzq.fsf@gnu.org> <87efpvulk1.fsf@gmail.com> <83376bawts.fsf@gnu.org> NNTP-Posting-Host: blaine.gmane.org Mime-Version: 1.0 Content-Type: text/plain X-Trace: blaine.gmane.org 1508786966 15528 195.159.176.226 (23 Oct 2017 19:29:26 GMT) X-Complaints-To: usenet@blaine.gmane.org NNTP-Posting-Date: Mon, 23 Oct 2017 19:29:26 +0000 (UTC) User-Agent: mu4e 0.9.18; emacs 25.2.1 Cc: 28945@debbugs.gnu.org To: Eli Zaretskii Original-X-From: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane.org@gnu.org Mon Oct 23 21:29:22 2017 Return-path: Envelope-to: geb-bug-gnu-emacs@m.gmane.org Original-Received: from lists.gnu.org ([208.118.235.17]) by blaine.gmane.org with esmtp (Exim 4.84_2) (envelope-from ) id 1e6iPH-0001Kt-UL for geb-bug-gnu-emacs@m.gmane.org; Mon, 23 Oct 2017 21:29:04 +0200 Original-Received: from localhost ([::1]:40265 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1e6iPP-0002ZM-Dp for geb-bug-gnu-emacs@m.gmane.org; Mon, 23 Oct 2017 15:29:11 -0400 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:38243) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1e6iPJ-0002ZG-Bp for bug-gnu-emacs@gnu.org; Mon, 23 Oct 2017 15:29:06 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1e6iPG-0006yO-5U for bug-gnu-emacs@gnu.org; Mon, 23 Oct 2017 15:29:05 -0400 Original-Received: from debbugs.gnu.org ([208.118.235.43]:49330) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1e6iPG-0006yE-1f for bug-gnu-emacs@gnu.org; Mon, 23 Oct 2017 15:29:02 -0400 Original-Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1e6iPF-0005sF-Lq for bug-gnu-emacs@gnu.org; Mon, 23 Oct 2017 15:29:01 -0400 X-Loop: help-debbugs@gnu.org Resent-From: Peter Neidhardt Original-Sender: "Debbugs-submit" Resent-CC: bug-gnu-emacs@gnu.org Resent-Date: Mon, 23 Oct 2017 19:29:01 +0000 Resent-Message-ID: Resent-Sender: help-debbugs@gnu.org X-GNU-PR-Message: followup 28945 X-GNU-PR-Package: emacs X-GNU-PR-Keywords: Original-Received: via spool by 28945-submit@debbugs.gnu.org id=B28945.150878692722555 (code B ref 28945); Mon, 23 Oct 2017 19:29:01 +0000 Original-Received: (at 28945) by debbugs.gnu.org; 23 Oct 2017 19:28:47 +0000 Original-Received: from localhost ([127.0.0.1]:58011 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1e6iP0-0005rj-QJ for submit@debbugs.gnu.org; Mon, 23 Oct 2017 15:28:46 -0400 Original-Received: from mail-wm0-f48.google.com ([74.125.82.48]:56557) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1e6iOy-0005rV-Sg for 28945@debbugs.gnu.org; Mon, 23 Oct 2017 15:28:45 -0400 Original-Received: by mail-wm0-f48.google.com with SMTP id z3so4924839wme.5 for <28945@debbugs.gnu.org>; Mon, 23 Oct 2017 12:28:44 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlemail.com; s=20161025; h=from:references:user-agent:to:cc:subject:in-reply-to:date :message-id:mime-version; bh=6QRRDLd07imSF/TgE4/nxKaW6/NIb7m4IvR2zYvu4m8=; b=q5EVAdDCyK+m4XiaFosTmSF5EHb33wQ/+ca/YKNE8L+GobjmZGCzdoKEvvR7Ij67KR 19xuSG2B6sKsZekc8xpDhyFSXLOxVFhAKiHXMEQwehzGr3CH0nFRF+0bjxErE5v1/Qs3 o4cJNtdHYbbqHAfDqtgAJ98u1t53r3104Ilsz/mO2uGXUA6M5ahehq2aobLkki3VUm7X VaqF2Iztf975+F2UC073lPMAP8PEXYB7vEjJyK9uowL1XUwffSNxhu1QvVLce1Gpq706 emHtpvzPi6Mnjp7UHfDNsHg3aK/P04cy4viFxAvKbcPPFtCHf8yuHhEUd7jqo5sfOLGK /EeA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:references:user-agent:to:cc:subject :in-reply-to:date:message-id:mime-version; bh=6QRRDLd07imSF/TgE4/nxKaW6/NIb7m4IvR2zYvu4m8=; b=fD+K4w8lKnH+xLVm8z9dEiJcLuMFwEEbWkLmBpu4wnpRDLYBjLutn1L+SzS1aH3u0A Qi/r78Rpp9cIsCli/RXPYHEggehbwZPJcdFSucLC5gG/jWHyrScFFlZsKRB6uqWU0bcd ZMu7pmyvA/2BRsLwG0YTLscTBq1zjwo3hjwxvDL3V4D5jE8JPYoRHDYHwWvg0H+mGeq5 WW+b0waAsa6XpPg91cd29mcD38Tjw+oaeYz4ITyUNdXchvIYzWRgBcwXd3LnE1gbBiuD /2hNv75QS57dR2R4XW5WoofIvC7b0q7vsQ7i8ZXVa6Zz/iMrL9loaC6anNG6xZGQ+y4k Z8+Q== X-Gm-Message-State: AMCzsaXc1cYHQ1T2t/0B9FYsaVNhejq3IpT8bemjrQQnBKHYzzQhHYw/ NKX3zKCM7wqhB9XGH+9Rnytj/Q== X-Google-Smtp-Source: ABhQp+QNYRY/Wj2M9hc5i5SnJW8EM/qZQoRU8S8amYXgeYoGFU/KRvy5aBRO8GDYnM5nyqhzBb5EKw== X-Received: by 10.28.173.66 with SMTP id w63mr6321467wme.17.1508786918660; Mon, 23 Oct 2017 12:28:38 -0700 (PDT) Original-Received: from dhiov23k ([197.3.130.54]) by smtp.gmail.com with ESMTPSA id 64sm4112422wma.21.2017.10.23.12.28.35 (version=TLS1_2 cipher=ECDHE-RSA-CHACHA20-POLY1305 bits=256/256); Mon, 23 Oct 2017 12:28:37 -0700 (PDT) X-Google-Original-From: Peter Neidhardt In-reply-to: <83376bawts.fsf@gnu.org> X-BeenThere: debbugs-submit@debbugs.gnu.org X-Mailman-Version: 2.1.18 Precedence: list X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.2.x-3.x [generic] X-Received-From: 208.118.235.43 X-BeenThere: bug-gnu-emacs@gnu.org List-Id: "Bug reports for GNU Emacs, the Swiss army knife of text editors" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane.org@gnu.org Original-Sender: "bug-gnu-emacs" Xref: news.gmane.org gmane.emacs.bugs:138904 Archived-At: Eli Zaretskii 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.