From: Eli Zaretskii <eliz@gnu.org>
To: Philipp Stephani <p.stephani2@gmail.com>
Cc: 25460-done@debbugs.gnu.org
Subject: bug#25460: 26.0.50; Documentation request: Save/write hooks and autosave
Date: Fri, 20 Jan 2017 11:03:18 +0200 [thread overview]
Message-ID: <8360la6r3d.fsf@gnu.org> (raw)
In-Reply-To: <wvr4shoikhah.fsf@a.muc.corp.google.com> (message from Philipp Stephani on Mon, 16 Jan 2017 19:09:58 +0100)
> From: Philipp Stephani <p.stephani2@gmail.com>
> Date: Mon, 16 Jan 2017 19:09:58 +0100
>
> Please document how {before,after}-save-hook and
> write-{buffer,file}-functions relate to autosave
They don't. These hooks are only run by basic-save-buffer.
> I noticed that even if auto-save-visited-file-name is t, autosaving
> doesn't run before-save-hook.
I added notes (on the release branch) that these hooks are only run by
save-buffer.
> The documentation should provide some guidance which hook to use
> depending on the value of auto-save-visited-file-name and on whether
> the current save operation is an auto-save or not.
It looks like you consider auto-save-visited-file-name as an option
that makes auto-saving exactly equivalent to saving the buffer. But
that is far from reality; in fact, as I wrote elsewhere, this option
has subtle issues, so much so that I don't recommend its use at all.
If we want it to be equivalent to saving, we should reimplement it so
that auto-saving uses basic-save-buffer when this option is non-nil.
But that is probably something for a separate bug report, so I'm
closing this one.
prev parent reply other threads:[~2017-01-20 9:03 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-16 18:09 bug#25460: 26.0.50; Documentation request: Save/write hooks and autosave Philipp Stephani
2017-01-20 9:03 ` Eli Zaretskii [this message]
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=8360la6r3d.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=25460-done@debbugs.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 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.