From: Eli Zaretskii <eliz@gnu.org>
To: Gregory Heytings <gregory@heytings.org>
Cc: 51523@debbugs.gnu.org, larsi@gnus.org, monnier@iro.umontreal.ca
Subject: bug#51523: 29.0.50; gnus-mime-view-part-externally very slow
Date: Mon, 01 Nov 2021 17:00:15 +0200 [thread overview]
Message-ID: <831r3zncow.fsf@gnu.org> (raw)
In-Reply-To: <6abcac838b7f89ee4e21@heytings.org> (message from Gregory Heytings on Mon, 01 Nov 2021 12:26:03 +0000)
> Date: Mon, 01 Nov 2021 12:26:03 +0000
> From: Gregory Heytings <gregory@heytings.org>
> Cc: 51523@debbugs.gnu.org, Stefan Monnier <monnier@iro.umontreal.ca>
>
> I attach a better patch, it uses a file-has-change-p function instead of a
> when-file-has-changed macro.
Thanks.
> +(defun file-has-changed-p (file)
> + "Return non-nil if FILE has changed.
> +The modification time of FILE is compared to the modification
> +time of FILE during a previous invocation of `file-has-changed-p'.
> +Therefore the first invocation of `file-has-changed-p' always
> +returns non-nil."
> + (let* ((attr (file-attributes file 'integer))
> + (mtime (file-attribute-modification-time attr))
> + (saved-mtime (gethash (intern file)
> + file-has-changed-p--hash-table)))
> + (when (not (equal mtime saved-mtime))
> + (puthash (intern file) mtime file-has-changed-p--hash-table))))
Bother: I think this implementation might cause both false positives
and false negatives.
. it uses the literal file name without even expanding it to an
absolute file name, so the same FILE might mean different files if
default-directory changes
. file names are generally not reliable enough for unique
identifiers of files (think symlinks on all systems, letter-case
and numerical tails on Windows, etc.), so we should at least use
file-truename
. interning the file names could produce many unnecessary symbols in
the global obarray
Can we make the implementation more robust by fixing these?
The name of the function also doesn't reflect what it does: it only
looks at the file's last modification time, so maybe at least "time"
should be in the name?
I also question the decision of testing modification time for
equality: why not check if the time stamp is newer, and disregard the
changes to an older time stamp? When looking this way at this
function, I ask myself whether extending file-newer-than-file-p to do
this job would be a better idea? Or maybe I don't understand the
general use case for this function.
next prev parent reply other threads:[~2021-11-01 15:00 UTC|newest]
Thread overview: 45+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-31 4:11 bug#51523: 29.0.50; gnus-mime-view-part-externally very slow Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-10-31 15:27 ` Lars Ingebrigtsen
2021-10-31 21:47 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-10-31 23:41 ` Gregory Heytings
2021-11-01 0:01 ` Lars Ingebrigtsen
2021-11-01 0:11 ` Gregory Heytings
2021-11-01 0:15 ` Lars Ingebrigtsen
2021-11-01 2:26 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-11-01 13:38 ` Lars Ingebrigtsen
2021-11-01 0:17 ` Gregory Heytings
2021-11-01 0:21 ` Lars Ingebrigtsen
2021-11-01 0:55 ` Gregory Heytings
2021-11-01 1:24 ` Gregory Heytings
2021-11-01 1:26 ` Gregory Heytings
[not found] ` <6abcac838bb94542451d@heytings.org>
2021-11-01 9:28 ` Gregory Heytings
[not found] ` <6abcac838bb83b0904d7@heytings.org>
[not found] ` <6abcac838bad7cded4c5@heytings.org>
2021-11-01 12:26 ` Gregory Heytings
2021-11-01 13:52 ` Lars Ingebrigtsen
2021-11-01 15:00 ` Eli Zaretskii [this message]
2021-11-01 15:20 ` Gregory Heytings
2021-11-01 15:23 ` Lars Ingebrigtsen
2021-11-01 16:46 ` Eli Zaretskii
2021-11-01 16:59 ` Lars Ingebrigtsen
2021-11-01 17:03 ` Eli Zaretskii
2021-11-01 17:15 ` Eli Zaretskii
2021-11-01 17:19 ` Lars Ingebrigtsen
2021-11-01 17:21 ` Eli Zaretskii
2021-11-01 17:23 ` Lars Ingebrigtsen
2021-11-01 17:28 ` Eli Zaretskii
2021-11-01 17:34 ` Lars Ingebrigtsen
2021-11-01 18:17 ` Eli Zaretskii
2021-11-01 21:14 ` Gregory Heytings
2021-11-02 14:50 ` Lars Ingebrigtsen
2021-11-02 15:12 ` Eli Zaretskii
2021-11-03 10:45 ` Gregory Heytings
2021-11-03 12:02 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-11-03 12:57 ` Gregory Heytings
2021-11-03 13:17 ` Eli Zaretskii
2021-11-03 13:27 ` Gregory Heytings
2021-11-03 13:53 ` Eli Zaretskii
2021-11-03 14:25 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-11-03 14:26 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-11-03 15:20 ` Gregory Heytings
2021-11-03 18:56 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-11-03 13:06 ` Eli Zaretskii
2021-11-01 0:04 ` 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
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=831r3zncow.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=51523@debbugs.gnu.org \
--cc=gregory@heytings.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 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).