From: Eli Zaretskii <eliz@gnu.org>
To: Aaron Jensen <aaronjensen@gmail.com>
Cc: larsi@gnus.org, emacs-devel@gnu.org
Subject: Re: A whole lotta auto-saving going
Date: Thu, 07 Jan 2021 16:55:28 +0200 [thread overview]
Message-ID: <83ble0lrtr.fsf@gnu.org> (raw)
In-Reply-To: <CAHyO48xPe5==0hsbK48MC6ozU6GiqA_WggM3seLpmNGLW4zgfA@mail.gmail.com> (message from Aaron Jensen on Wed, 6 Jan 2021 16:05:52 -0600)
> From: Aaron Jensen <aaronjensen@gmail.com>
> Date: Wed, 6 Jan 2021 16:05:52 -0600
> Cc: Lars Ingebrigtsen <larsi@gnus.org>
>
> > The past few days on the trunk, I'm seeing "Auto-saving...done" a whole
> > lot more than before. Sometimes it's popping up every few characters
> > I'm typing, which just seems unhelpful.
> >
> > I haven't investigated at all why this is happening -- is it immediately
> > obvious to somebody what's going on?
>
> I too am seeing this in my emacs config in enh-ruby-mode. If I change
> auto-save-interval to 0, it stops. So it appears that the
> auto-save-interval is somehow broken.
I suggest to put a breakpoint in Fdo_auto_save and see what invokes it
and why. First, which code invokes it? Next, if it's indeed this
place:
if (commandflag != 0 && commandflag != -2
&& auto_save_interval > 0
&& num_nonmacro_input_events - last_auto_save > max (auto_save_interval, 20)
&& !detect_input_pending_run_timers (0))
{
Fdo_auto_save (auto_save_no_message ? Qt : Qnil, Qnil);
/* Hooks can actually change some buffers in auto save. */
redisplay ();
}
then why does it happen? Do we fail to update last_auto_save? or do
we increment num_nonmacro_input_events too quickly for some reason?
I presume that this doesn't happen in "emacs -Q", because I was unable
to reproduce it. Then maybe some customizations cause this, directly
or indirectly. For example, maybe some timers or subprocesses cause
this.
next prev parent reply other threads:[~2021-01-07 14:55 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-06 22:05 A whole lotta auto-saving going Aaron Jensen
2021-01-07 12:24 ` Lars Ingebrigtsen
2021-01-07 15:21 ` Stefan Monnier
2021-01-08 14:05 ` Aaron Jensen
2021-01-08 14:19 ` Aaron Jensen
2021-01-10 11:10 ` Lars Ingebrigtsen
2021-01-10 15:08 ` Aaron Jensen
2021-01-10 15:24 ` Lars Ingebrigtsen
2021-01-10 17:27 ` Eli Zaretskii
2021-01-10 17:38 ` Stefan Monnier
2021-01-11 4:23 ` Stefan Monnier
2021-01-11 15:04 ` Eli Zaretskii
2021-01-11 16:00 ` Stefan Monnier
2021-01-11 16:54 ` Eli Zaretskii
2021-01-11 18:00 ` Stefan Monnier
2021-01-12 14:58 ` Eli Zaretskii
2021-01-12 15:18 ` Stefan Monnier
2021-01-13 22:25 ` Stefan Monnier
2021-01-18 16:06 ` Lars Ingebrigtsen
2021-01-10 17:18 ` Stefan Monnier
2021-01-10 18:34 ` T.V Raman
2021-01-10 18:54 ` Aaron Jensen
2021-01-12 16:02 ` T.V Raman via Emacs development discussions.
2021-01-07 14:55 ` Eli Zaretskii [this message]
2021-01-10 11:09 ` Lars Ingebrigtsen
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=83ble0lrtr.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=aaronjensen@gmail.com \
--cc=emacs-devel@gnu.org \
--cc=larsi@gnus.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).