From: Glenn Morris <rgm@gnu.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: p.stephani2@gmail.com, 25478@debbugs.gnu.org
Subject: bug#25478: 26.0.50; No hooks are called when auto-saving
Date: Fri, 20 Jan 2017 12:42:48 -0500 [thread overview]
Message-ID: <f2efzx1vc7.fsf@fencepost.gnu.org> (raw)
In-Reply-To: <837f5q6rxq.fsf@gnu.org> (Eli Zaretskii's message of "Fri, 20 Jan 2017 10:45:05 +0200")
Eli Zaretskii wrote:
> All in all, I think this option is subtly dangerous and should be
> either deprecated or completely reimplemented to invoke
> basic-save-buffer instead. I'm quite sure this option made sense in
> the past, when complications with encoding and save-related hooks
> didn't exist, but that is no longer the case in Emacs these days.
> If someone thinks using this option will allow them not to bother with
> saving their edits, they are in for an unpleasant surprise.
Deprecation sounds good to me.
I believe there's a "real-auto-save" package that does a standard save
at intervals.
next prev parent reply other threads:[~2017-01-20 17:42 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-18 21:39 bug#25478: 26.0.50; No hooks are called when auto-saving Philipp Stephani
2017-01-19 20:29 ` Glenn Morris
2017-01-20 8:45 ` Eli Zaretskii
2017-01-20 17:42 ` Glenn Morris [this message]
2017-03-26 18:21 ` Philipp Stephani
2017-03-26 18:45 ` Eli Zaretskii
2017-03-26 19:17 ` Philipp Stephani
2017-04-22 19:01 ` Philipp Stephani
2017-04-28 9:27 ` Eli Zaretskii
2017-04-29 18:47 ` Philipp Stephani
2017-04-29 18:49 ` bug#25478: [PATCH] Reimplement auto-saving to visited files Philipp Stephani
[not found] ` <20170429184909.40204-1-phst@google.com>
2017-04-29 19:20 ` Eli Zaretskii
2017-04-29 19:31 ` Philipp Stephani
[not found] ` <CAArVCkR-BeJDgC5tu0PfN-63PRB5UN9Yid-UbuVdT-CpafVeAg@mail.gmail.com>
2020-08-11 8:08 ` Stefan Kangas
2020-10-01 12:11 ` Stefan Kangas
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=f2efzx1vc7.fsf@fencepost.gnu.org \
--to=rgm@gnu.org \
--cc=25478@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=p.stephani2@gmail.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 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).