From: Po Lu <luangruo@yahoo.com>
To: Paul Eggert <eggert@cs.ucla.edu>
Cc: emacs-devel@gnu.org
Subject: Re: master 4a1f69ebca 2/2: Use (TICKS . HZ) for current-time etc.
Date: Wed, 27 Apr 2022 09:29:32 +0800 [thread overview]
Message-ID: <87wnfb1fgj.fsf@yahoo.com> (raw)
In-Reply-To: <2bd8adf5-718d-2c7f-b93c-df5689249044@cs.ucla.edu> (Paul Eggert's message of "Tue, 26 Apr 2022 18:18:05 -0700")
Paul Eggert <eggert@cs.ucla.edu> writes:
> Not a good sign. I installed the attached, which should fix a bug with
> a desktop saved with older Emacs and restored with newer. Does this
> patch fix things for you? If not, is ~/.emacs.d/.emacs.desktop
> something you can send me? And even if so, this suggests we need a
> better way to tell Emacs to use old-format timestamps for
> compatibility.
The change you installed fixes my problem (though I really don't see why
it did, since nothing is saved.)
Also, shouldn't the desktop file version be bumped when the format of
the time data changes?
Thanks.
next prev parent reply other threads:[~2022-04-27 1:29 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <165091562900.12167.2356992007535632125@vcs2.savannah.gnu.org>
[not found] ` <20220425194030.030A8C01687@vcs2.savannah.gnu.org>
2022-04-26 9:38 ` master 4a1f69ebca 2/2: Use (TICKS . HZ) for current-time etc Lars Ingebrigtsen
2022-04-26 10:20 ` Manuel Uberti
2022-04-26 10:38 ` Po Lu
2022-04-26 14:42 ` Bozhidar Batsov
2022-04-26 20:29 ` Paul Eggert
2022-04-27 0:36 ` Po Lu
2022-04-27 1:18 ` Paul Eggert
2022-04-27 1:29 ` Po Lu [this message]
2022-04-27 4:10 ` Paul Eggert
2022-04-26 20:28 ` Paul Eggert
2022-04-27 12:17 ` Lars Ingebrigtsen
2022-04-26 23:54 ` Michael Heerdegen
2022-04-27 6:37 Mark Barton
2022-04-27 7:20 ` Po Lu
2022-04-27 7:39 ` Paul Eggert
2022-04-27 16:55 ` Stefan Monnier
2022-04-28 22:27 ` Paul Eggert
2022-04-29 14:22 ` Max Nikulin
2022-04-29 18:10 ` Paul Eggert
2022-04-30 10:56 ` Max Nikulin
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=87wnfb1fgj.fsf@yahoo.com \
--to=luangruo@yahoo.com \
--cc=eggert@cs.ucla.edu \
--cc=emacs-devel@gnu.org \
/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).