From: Eli Zaretskii <eliz@gnu.org>
To: Paul Eggert <eggert@cs.ucla.edu>
Cc: manikulin@gmail.com, emacs-devel@gnu.org
Subject: Re: Time resolution in Emacs
Date: Mon, 25 Apr 2022 19:10:08 +0300 [thread overview]
Message-ID: <83mtg9m9en.fsf@gnu.org> (raw)
In-Reply-To: <3008dea1-572b-9010-f3c4-15272145fd8a@cs.ucla.edu> (message from Paul Eggert on Mon, 25 Apr 2022 08:34:04 -0700)
> Date: Mon, 25 Apr 2022 08:34:04 -0700
> From: Paul Eggert <eggert@cs.ucla.edu>
> Cc: manikulin@gmail.com, emacs-devel@gnu.org
>
> On 4/22/22 23:51, Eli Zaretskii wrote:
>
> >> There are Gnulib library functions to
> >> deal with this sort of thing; it's not a new problem.
> >
> > Doesn't that slow down applications?
>
> Not significantly, no. file-attributes already has the file's filesystem
> ID and timestamps so Emacs can easily cache that (it's a small cache
> with only one entry per filesystem). There's no need to traipse through
> the filesystem looking at other files. This is what coreutils does and
> it works well in practice. It's not expensive and not that complicated.
Sorry, I don't understand. Suppose the given Emacs session called
file-attributes on only 1 file: how do we know the resolution of the
file timestamps from that single file? The fact that a timestamp has
N last digits zero says nothing at all about the resolution.
> Your suggestion of maintaining a static table for known filesystem types
> is a good one; we could do that to improve common cases. I would like to
> take a look into doing this.
Thanks, I think for starters we don't need anything else, like dynamic
determination of the actual resolution.
> If successful, it should improve coreutils
> and other GNU apps even if Emacs makes no changes in this area. In the
> meantime I'll withdraw the proposed changes that would cause Emacs to
> communicate OS timestamp resolution to the user; that sort of thing can
> wait until after I've had that look (assuming I ever find the time :-).
Yes, it can definitely wait. I'd like first to see if my proposal is
good enough, and if not, to hear really good reasons why not.
> For example, if Emacs imports from the network a timestamp with three
> digits after the decimal point, it should convert it to an internal
> timestamp with millisecond resolution.
I'm not sure this is TRT. What do you do if you get a timestamp whose
fractional part looks like .123000 -- do you consider this to be
millisecond resolution or microsecond resolution? If the latter, we'd
get in trouble as result of trivial arithmetics on timestamps; if the
former, you risk losing resolution for now good reason, just because
the time stamp was too "round".
> Conversely when sending a textual timestamp, Emacs should generate
> only as many trailing digits as needed.
It's very hard to keep only that many significant digits when working
with fractional numbers.
next prev parent reply other threads:[~2022-04-25 16:10 UTC|newest]
Thread overview: 106+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-07 12:37 bug#54764: encode-time: make DST and TIMEZONE fields of the list argument optional ones Max Nikulin
2022-04-09 7:52 ` Paul Eggert
2022-04-09 11:36 ` Max Nikulin
2022-04-10 3:57 ` Max Nikulin
2022-04-13 14:40 ` Max Nikulin
2022-04-13 14:40 ` Max Nikulin
2022-04-13 18:35 ` Paul Eggert
2022-04-13 18:35 ` Paul Eggert
2022-04-14 13:19 ` Max Nikulin
2022-04-14 13:19 ` Max Nikulin
2022-04-14 22:46 ` Paul Eggert
2022-04-15 2:14 ` Tim Cross
2022-04-15 2:14 ` Tim Cross
2022-04-15 17:23 ` Max Nikulin
2022-04-15 17:23 ` Max Nikulin
2022-04-16 19:23 ` Paul Eggert
2022-04-16 19:23 ` Paul Eggert
2022-04-21 16:59 ` Max Nikulin
2022-04-21 16:59 ` Max Nikulin
2022-04-19 2:02 ` Paul Eggert
2022-04-19 2:02 ` Paul Eggert
2022-04-19 5:50 ` Eli Zaretskii
2022-04-19 5:50 ` Eli Zaretskii
2022-04-19 22:22 ` Paul Eggert
2022-04-19 22:22 ` Paul Eggert
2022-04-20 7:23 ` Eli Zaretskii
2022-04-20 7:23 ` Eli Zaretskii
2022-04-20 18:19 ` Paul Eggert
2022-04-20 18:19 ` Paul Eggert
2022-04-20 18:41 ` Eli Zaretskii
2022-04-20 18:41 ` Eli Zaretskii
2022-04-20 19:01 ` Paul Eggert
2022-04-20 19:01 ` Paul Eggert
2022-04-20 19:14 ` Eli Zaretskii
2022-04-20 19:14 ` Eli Zaretskii
2022-04-20 19:23 ` Paul Eggert
2022-04-20 19:30 ` Eli Zaretskii
2022-04-20 19:30 ` Eli Zaretskii
2022-04-21 0:11 ` Paul Eggert
2022-04-21 6:44 ` Eli Zaretskii
2022-04-21 15:30 ` Max Nikulin
2022-04-21 15:58 ` Eli Zaretskii
2022-04-21 17:23 ` Max Nikulin
2022-04-21 18:46 ` Eli Zaretskii
2022-04-21 23:56 ` Paul Eggert
2022-04-22 5:01 ` Eli Zaretskii
2022-04-22 5:01 ` Eli Zaretskii
2022-04-22 5:23 ` Time resolution in Emacs " Eli Zaretskii
2022-04-22 18:22 ` Paul Eggert
2022-04-22 18:52 ` Corwin Brust
2022-04-22 21:26 ` Paul Eggert
2022-04-23 6:27 ` Time resolution in Emacs Eli Zaretskii
2022-04-24 0:56 ` Paul Eggert
2022-04-24 6:10 ` Eli Zaretskii
2022-04-24 11:47 ` Max Nikulin
2022-04-24 12:23 ` Eli Zaretskii
2022-04-25 15:32 ` Paul Eggert
2022-04-25 16:01 ` Eli Zaretskii
2022-04-22 19:35 ` Time resolution in Emacs argument optional ones Eli Zaretskii
2022-04-22 21:52 ` Paul Eggert
2022-04-23 6:51 ` Time resolution in Emacs Eli Zaretskii
2022-04-25 15:34 ` Paul Eggert
2022-04-25 16:10 ` Eli Zaretskii [this message]
2022-04-25 16:38 ` Paul Eggert
2022-04-25 16:57 ` Eli Zaretskii
2022-04-25 16:54 ` Max Nikulin
2022-04-25 17:02 ` Eli Zaretskii
2022-04-25 19:27 ` Paul Eggert
2022-04-29 15:19 ` Max Nikulin
2022-04-29 16:07 ` Eli Zaretskii
2022-04-21 23:56 ` bug#54764: encode-time: make DST and TIMEZONE fields of the list argument optional ones Paul Eggert
2022-04-21 6:44 ` Eli Zaretskii
2022-04-21 0:11 ` Paul Eggert
2022-04-20 19:23 ` Paul Eggert
2022-04-23 14:35 ` Bernhard Voelker
2022-04-23 14:35 ` Bernhard Voelker
2022-04-20 15:07 ` Max Nikulin
2022-04-20 15:07 ` Max Nikulin
2022-04-20 18:29 ` Paul Eggert
2022-04-20 18:29 ` Paul Eggert
2022-04-25 15:30 ` Max Nikulin
2022-04-25 15:30 ` Max Nikulin
2022-04-25 15:37 ` Paul Eggert
2022-04-25 15:37 ` Paul Eggert
2022-04-25 19:49 ` Paul Eggert
2022-04-25 19:49 ` Paul Eggert
2022-04-30 11:22 ` Max Nikulin
2022-04-30 11:22 ` Max Nikulin
2022-05-01 2:32 ` Paul Eggert
2022-05-01 2:32 ` Paul Eggert
2022-05-01 17:15 ` Max Nikulin
2022-05-01 17:15 ` Max Nikulin
2022-04-14 22:46 ` Paul Eggert
2022-04-13 15:12 ` Max Nikulin
2022-04-13 15:12 ` Max Nikulin
2022-04-16 16:26 ` Max Nikulin
2022-04-16 16:26 ` Max Nikulin
2022-04-17 1:58 ` Paul Eggert
2022-04-20 16:56 ` Max Nikulin
2022-04-20 16:56 ` Max Nikulin
2022-04-20 19:17 ` Paul Eggert
2022-04-20 19:17 ` Paul Eggert
2022-04-17 1:58 ` Paul Eggert
2022-04-09 7:52 ` Paul Eggert
[not found] ` <handler.54764.D54764.165091617725815.notifdone@debbugs.gnu.org>
2022-04-25 21:16 ` Glenn Morris
2022-04-26 1:18 ` Paul Eggert
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=83mtg9m9en.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=eggert@cs.ucla.edu \
--cc=emacs-devel@gnu.org \
--cc=manikulin@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.