From: Eli Zaretskii <eliz@gnu.org>
To: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: larsi@gnus.org, emacs-devel@gnu.org
Subject: Re: master e8488bcc9c: Avoid having font locking triggering unnecessary auto-saving
Date: Sat, 07 May 2022 20:26:16 +0300 [thread overview]
Message-ID: <83a6btxnif.fsf@gnu.org> (raw)
In-Reply-To: <jwv1qx52rb7.fsf-monnier+emacs@gnu.org> (message from Stefan Monnier on Sat, 07 May 2022 13:21:40 -0400)
> From: Stefan Monnier <monnier@iro.umontreal.ca>
> Cc: larsi@gnus.org, emacs-devel@gnu.org
> Date: Sat, 07 May 2022 13:21:40 -0400
>
> Eli Zaretskii [2022-05-07 19:40:42] wrote:
> > Not good enough: auto-saving is a critical feature, and I object to
> > changes that could make it less reliable, because it could mean users
> > will lose their edits. By contrast, with-silent-modifications is just
> > a convenience device, to avoid annoying users with redundant "changes"
> > of the buffer.
>
> Your call. The change to `with-silent-modifications` can similarly
> break auto-save, of course.
If it does, we will hear about it sooner or later. But code that uses
with-silent-modifications is but a fraction of the code that changes
buffers in some way. And when some code is inside
with-silent-modifications, it is clearly marked, so its effects on
auto-save are easily seen and understood. Thus, chances are
relatively small that we allow some changes that should cause
auto-save be hidden by with-silent-modifications.
> > What practical problem do you want to solve by that change in
> > auto-save?
>
> The motivation for the change makes me think that the change I propose
> might be closer to the ideal.
The ideal for auto-saving is to save any changes, and when in doubt,
save anyway.
next prev parent reply other threads:[~2022-05-07 17:26 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <165191796540.22789.3432288633082546349@vcs2.savannah.gnu.org>
[not found] ` <20220507100605.B7CA7C051FF@vcs2.savannah.gnu.org>
2022-05-07 16:06 ` master e8488bcc9c: Avoid having font locking triggering unnecessary auto-saving Stefan Monnier
2022-05-07 16:10 ` Eli Zaretskii
2022-05-07 16:27 ` Stefan Monnier
2022-05-07 16:40 ` Eli Zaretskii
2022-05-07 17:21 ` Stefan Monnier
2022-05-07 17:26 ` Eli Zaretskii [this message]
2022-05-07 16:49 ` Lars Ingebrigtsen
2022-05-09 12:37 ` Lars Ingebrigtsen
2022-05-09 13:22 ` Stefan Monnier
2022-05-09 13:35 ` Lars Ingebrigtsen
2022-05-09 13:47 ` Lars Ingebrigtsen
2022-05-09 15:43 ` Stefan Monnier
2022-05-09 16:05 ` Lars Ingebrigtsen
2022-05-09 16:30 ` Eli Zaretskii
2022-05-09 16:45 ` Lars Ingebrigtsen
2022-05-09 17:40 ` Lars Ingebrigtsen
2022-05-09 18:29 ` Stefan Monnier
2022-05-10 1:51 ` Lars Ingebrigtsen
2022-05-10 2:11 ` Stefan Monnier
2022-05-10 11:45 ` Lars Ingebrigtsen
2022-05-10 11:55 ` Stefan Monnier
2022-05-11 11:22 ` Lars Ingebrigtsen
2022-05-11 13:19 ` Stefan Monnier
2022-05-12 0:18 ` Lars Ingebrigtsen
2022-05-09 17:00 ` 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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=83a6btxnif.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=larsi@gnus.org \
--cc=monnier@iro.umontreal.ca \
/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.