From: Lars Ingebrigtsen <larsi@gnus.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: v.pupillo@gmail.com, 55163@debbugs.gnu.org, eggert@cs.ucla.edu
Subject: bug#55163: 29.0.50; master 4a1f69ebca (TICKS . HZ) for current-time broke lsp-mode
Date: Fri, 29 Apr 2022 12:59:39 +0200 [thread overview]
Message-ID: <87y1zof944.fsf@gnus.org> (raw)
In-Reply-To: <83y1zo9n3o.fsf@gnu.org> (Eli Zaretskii's message of "Fri, 29 Apr 2022 13:54:03 +0300")
Eli Zaretskii <eliz@gnu.org> writes:
> I don't understand how this is related to making the time rfesolution
> explicit in time objects. The main problem in that area wa how we can
> know the resolution of each timestamp, not how to expose that to Lisp.
>
> In the particular example you mention, how can Emacs know what is the
> resolution of a file's last modification time?
>
> What did I miss?
This isn't related to that at all (except tangentially).
--
(domestic pets only, the antidote for overdose, milk.)
bloggy blog: http://lars.ingebrigtsen.no
next prev parent reply other threads:[~2022-04-29 10:59 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-28 10:53 bug#55163: 29.0.50; master 4a1f69ebca (TICKS . HZ) for current-time broke lsp-mode Vincenzo Pupillo
2022-04-28 12:10 ` Lars Ingebrigtsen
2022-04-28 13:38 ` Eli Zaretskii
2022-04-28 20:15 ` Paul Eggert
2022-04-28 20:42 ` Vincenzo Pupillo
2022-04-28 21:55 ` Lars Ingebrigtsen
2022-04-28 21:51 ` Lars Ingebrigtsen
2022-04-29 9:54 ` Lars Ingebrigtsen
2022-04-29 10:54 ` Eli Zaretskii
2022-04-29 10:59 ` Lars Ingebrigtsen [this message]
2022-04-29 11:10 ` Eli Zaretskii
2022-04-29 19:38 ` Paul Eggert
2022-04-29 19:53 ` Eli Zaretskii
2022-04-29 22:45 ` Paul Eggert
2022-04-30 5:29 ` Eli Zaretskii
2022-04-30 9:10 ` Lars Ingebrigtsen
2022-04-30 10:00 ` Eli Zaretskii
2022-04-30 20:51 ` Paul Eggert
2022-05-01 5:38 ` Eli Zaretskii
2022-05-01 15:00 ` Paul Eggert
2022-05-01 15:42 ` Eli Zaretskii
2022-05-01 16:17 ` Paul Eggert
2022-05-01 16:43 ` Eli Zaretskii
2022-05-02 17:27 ` Paul Eggert
2022-05-02 17:58 ` Eli Zaretskii
2022-05-02 23:17 ` Paul Eggert
2022-05-03 2:32 ` Eli Zaretskii
2022-05-03 2:52 ` Paul Eggert
2022-04-30 1:44 ` Paul Eggert
2022-04-30 5:40 ` Eli Zaretskii
2022-04-30 11:21 ` Vincenzo Pupillo
2022-04-30 11:25 ` Eli Zaretskii
2022-04-30 12:32 ` Vincenzo Pupillo
2022-04-30 12:50 ` Eli Zaretskii
2022-04-30 13:22 ` Vincenzo Pupillo
2022-04-30 9:15 ` Lars Ingebrigtsen
2022-04-30 21:03 ` Paul Eggert
2022-05-01 5:40 ` Eli Zaretskii
2022-05-01 15:08 ` 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
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=87y1zof944.fsf@gnus.org \
--to=larsi@gnus.org \
--cc=55163@debbugs.gnu.org \
--cc=eggert@cs.ucla.edu \
--cc=eliz@gnu.org \
--cc=v.pupillo@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 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).