From: Juri Linkov <juri@linkov.net>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 30215@debbugs.gnu.org
Subject: bug#30215: Visiting files from zip archives should not modify directory time
Date: Sat, 27 Jan 2018 23:16:20 +0200 [thread overview]
Message-ID: <87mv0z0zq3.fsf@mail.linkov.net> (raw)
In-Reply-To: <834ln9m4or.fsf@gnu.org> (Eli Zaretskii's message of "Fri, 26 Jan 2018 09:59:00 +0200")
>> Creation of a backup file is not a problem, because backups are created
>> on saving.
>
> What about auto-saving in general, and the new auto-save-visited-mode
> in particular?
The default value of `auto-save-visited-interval' is 5 seconds, but the
time of extracting a file from the archive is measured in microseconds.
BTW, while looking at `auto-save-visited-mode', I noticed that the
docstring of `save-some-buffers' could be improved:
diff --git a/lisp/files.el b/lisp/files.el
index 00622cf..98ad209 100644
--- a/lisp/files.el
+++ b/lisp/files.el
@@ -5220,7 +5220,7 @@ save-some-buffers
This command first saves any buffers where `buffer-save-without-query' is
non-nil, without asking.
-Optional argument (the prefix) non-nil means save all with no questions.
+Optional ARG (the prefix) non-nil means save all with no questions.
Optional second argument PRED determines which buffers are considered:
If PRED is nil, all the file-visiting buffers are considered.
If PRED is t, then certain non-file buffers will also be considered.
next prev parent reply other threads:[~2018-01-27 21:16 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-22 21:52 bug#30215: Visiting files from zip archives should not modify directory time Juri Linkov
2018-01-23 16:41 ` Eli Zaretskii
2018-01-23 21:29 ` Juri Linkov
2018-01-24 18:44 ` Eli Zaretskii
2018-01-24 21:36 ` Juri Linkov
2018-01-25 3:30 ` Eli Zaretskii
2018-01-25 21:41 ` Juri Linkov
2018-01-26 7:59 ` Eli Zaretskii
2018-01-27 21:16 ` Juri Linkov [this message]
2018-01-28 17:23 ` Eli Zaretskii
2018-01-28 21:28 ` Juri Linkov
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=87mv0z0zq3.fsf@mail.linkov.net \
--to=juri@linkov.net \
--cc=30215@debbugs.gnu.org \
--cc=eliz@gnu.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 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.