From: Michael Heerdegen via "Bug reports for GNU Emacs, the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
To: 73709@debbugs.gnu.org
Cc: eliz@gnu.org, drew.adams@oracle.com
Subject: bug#73709: 29.4; Doc of `file-newer-than-file-p'
Date: Wed, 09 Oct 2024 02:45:44 +0200 [thread overview]
Message-ID: <87set6aytj.fsf@web.de> (raw)
In-Reply-To: <DS7PR10MB52321FA91E43D4B591C0FF54F37E2@DS7PR10MB5232.namprd10.prod.outlook.com> (Drew Adams via's message of "Tue, 8 Oct 2024 18:40:18 +0000")
Drew Adams via "Bug reports for GNU Emacs, the Swiss army knife of text
editors" <bug-gnu-emacs@gnu.org> writes:
> It's not about any implementation details. It's about
> what's meant here by "newer". And the answer is that
> it's about the recentness of the last modification.
It's not obvious that the time that a file existed is not meant.
Creation time is what came to my mind, and I find the actual meaning a
bit surprising. Maybe I even didn't use this function where I should
have and reinvented the thing because of a wrong expectation. So a +1
from me for trying to make it clearer.
I know already saving files may create a new file and rename the
existing one to a backup name - or keep the file etc. But anyway, let's
at least say that creation time is not meant, but most of the time, last
file modification.
Michael.
next prev parent reply other threads:[~2024-10-09 0:45 UTC|newest]
Thread overview: 29+ 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 [this message]
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-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
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=87set6aytj.fsf@web.de \
--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 \
/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).