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: Tue, 23 Jan 2018 23:29:34 +0200 [thread overview]
Message-ID: <87tvvc8ds1.fsf@mail.linkov.net> (raw)
In-Reply-To: <83h8rco7cg.fsf@gnu.org> (Eli Zaretskii's message of "Tue, 23 Jan 2018 18:41:51 +0200")
>> Visiting a file from zip archive changes the modification time of
>> its directory. It's possible to prevent directory time modification
>> by setting ‘buffer-file-truename’ later after the extractor prepares
>> the file in its buffer:
>
> Sorry, I don't think I understand what you are saying (and if I did, I
> cannot reproduce it). I visited a random zip archive on my system,
> then pressed RET on one of the files, then killed the buffer which
> visited that file -- and didn't see any changes in the time stamps
> recorded in the zip archive. Which is what I'd expect, since visiting
> a file from an archive doesn't rewrite the archive, nor modifies it in
> any other way.
>
> What am I missing?
It modifies the time of the directory where the zip archive is located,
e.g. visiting a file inside ~/dir/file.zip modifies the time of the
directory ~/dir/ because during unzipping in that directory, arc-mode
creates a temporary backup with the file name from ‘buffer-file-truename’.
Setting ‘buffer-file-truename’ later prevents from creating this
unnecessary backup copy that modifies the directory time.
next prev parent reply other threads:[~2018-01-23 21:29 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 [this message]
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
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=87tvvc8ds1.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.