all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Drew Adams via "Bug reports for GNU Emacs, the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
To: Ship Mints <shipmints@gmail.com>, Eli Zaretskii <eliz@gnu.org>
Cc: "michael_heerdegen@web.de" <michael_heerdegen@web.de>,
	"73709@debbugs.gnu.org" <73709@debbugs.gnu.org>
Subject: bug#73709: 29.4; Doc of `file-newer-than-file-p'
Date: Tue, 15 Oct 2024 16:21:22 +0000	[thread overview]
Message-ID: <DS7PR10MB52324C319B34D998C5D5A638F3452@DS7PR10MB5232.namprd10.prod.outlook.com> (raw)
In-Reply-To: <CAN+1HbrgNqCsu1BExK47ne=JW8ezBHmLHKbUPpJYPy97mt5mdA@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 786 bytes --]

From: Ship Mints Sent: Tuesday, October 15, 2024 8:01 AM
Perhaps something simple like "This function returns t if the file filename1 is newer than file filename2, as reported by your operating system."

IMO that doesn't help. It just suggests that a reader look to the operating system doc for how it defines/reports a "newer" file. Look for the words "newer" and "file" in the OS doc?

The point of the bug report is that this comparison (whatever the OS, presumably) has something/mostly to do with the latest modification date of the file - something equivalent, or similar, to what Unix/Linux`touch' ends up with as the resulting time/date.

That's mostly to do with file content: at a _first approximation_ it's the date of the last content change - on any OS presumably.

[-- Attachment #2: Type: text/html, Size: 3533 bytes --]

  reply	other threads:[~2024-10-15 16:21 UTC|newest]

Thread overview: 39+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-10-08 17:56 bug#73709: 29.4; Doc of `file-newer-than-file-p' Drew Adams via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-10-08 18:20 ` Eli Zaretskii
2024-10-08 18:40   ` Drew Adams via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-10-09  0:45     ` Michael Heerdegen via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-10-09 13:31       ` Eli Zaretskii
2024-10-09 16:32         ` Drew Adams via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-10-09 23:21         ` Michael Heerdegen via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-10-10  8:09           ` Eli Zaretskii
2024-10-10 11:08             ` Michael Albinus via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-10-11  0:23             ` Michael Heerdegen via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-10-11  5:56               ` Eli Zaretskii
2024-10-12  0:31                 ` Michael Heerdegen via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-10-12  8:40                   ` Eli Zaretskii
2024-10-12 22:48                     ` Michael Heerdegen via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-10-13  5:13                       ` Eli Zaretskii
2024-10-13 14:51                         ` Drew Adams via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-10-13 15:31                           ` Eli Zaretskii
2024-10-13 17:01                             ` Drew Adams via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-10-13 18:30                               ` Eli Zaretskii
2024-10-13 22:23                                 ` Drew Adams via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-10-14  2:28                                   ` Eli Zaretskii
2024-10-15  1:10                             ` Michael Heerdegen via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-10-15 13:46                               ` Eli Zaretskii
2024-10-15 14:20                                 ` Drew Adams via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-10-15 14:51                                   ` Eli Zaretskii
2024-10-15 15:01                                     ` Ship Mints
2024-10-15 16:21                                       ` Drew Adams via Bug reports for GNU Emacs, the Swiss army knife of text editors [this message]
2024-10-15 16:23                                       ` Michael Albinus via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-10-15 16:24                                         ` Ship Mints
2024-10-16  4:11                                 ` Michael Heerdegen via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-10-16  5:54                                   ` Eli Zaretskii
2024-10-18  1:32                                     ` Michael Heerdegen via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-10-09 23:42         ` Stefan Kangas
2024-10-10  1:47           ` Drew Adams via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-10-10  8:26           ` Eli Zaretskii
2024-10-11  0:41             ` Michael Heerdegen via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-10-11  6:03               ` Eli Zaretskii
2024-10-12  0:38                 ` Michael Heerdegen via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-10-12  1:13                   ` Drew Adams via Bug reports for GNU Emacs, the Swiss army knife of text editors

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=DS7PR10MB52324C319B34D998C5D5A638F3452@DS7PR10MB5232.namprd10.prod.outlook.com \
    --to=bug-gnu-emacs@gnu.org \
    --cc=73709@debbugs.gnu.org \
    --cc=drew.adams@oracle.com \
    --cc=eliz@gnu.org \
    --cc=michael_heerdegen@web.de \
    --cc=shipmints@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.