From: Bruno Haible <bruno@clisp.org>
To: Paul Eggert <eggert@cs.ucla.edu>
Cc: bug-gnulib@gnu.org, Emacs-devel@gnu.org
Subject: Re: boot-time: straighten code
Date: Tue, 15 Aug 2023 23:12:53 +0200 [thread overview]
Message-ID: <4449898.bgbtPGBEXF@nimes> (raw)
In-Reply-To: <5a77c0b9-8692-83bf-1aca-2f1d27122877@cs.ucla.edu>
Paul Eggert wrote:
> I installed the attached patch into Emacs
> master, which you should be able to test via:
>
> git clone https://git.savannah.gnu.org/git/emacs.git
> cd emacs
> ./autogen.sh
> ./configure
> make
> src/emacs
>
> Please give it a try, especially on any MS-Windows platform you happen
> to have. I have tested only on Ubuntu 23.04 so far.
>
> A simple way to test is to use Emacs to start editing a file (without
> saving) and then inspect the symbolic link .#* that Emacs uses as a lock
> file. The trailing digits of that link's contents should be the boot
> time. These symlinks are Emacs's only use of boot time.
Here are my test results. On each of the following platforms, after
regenerating the current 'configure' file and then building the 'emacs'
directory from today, with the configure options
--disable-silent-rules --without-all --without-x
then running "./emacs $HOME/hello.c", editing that buffer, opening
a 'M-x shell' buffer, and looking at the $HOME/.#hello.c symlink,
I can see that its last component is exactly the time_t value of the
boot time, as displayed by the gnulib 'test-readutmp' test. So, the
test passes on all these platforms:
- Linux: Ubuntu 22.04, Alpine Linux
- Debian GNU/Hurd 2022
- Debian GNU/kFreeBSD 7
- NetBSD 9.3
- OpenBSD 7.2
- Cygwin 2.9.0
I could not test the Windows binaries from corwin, due to problems mentioned in
<https://lists.gnu.org/archive/html/emacs-devel/2023-08/msg00543.html>.
Also, I could not test on Android (in Termux), due to a build failure, cf.
<https://github.com/termux/termux-packages/issues/6592>.
Bruno
next prev parent reply other threads:[~2023-08-15 21:12 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <4536176.VaOIPsP7d9@nimes>
2023-08-13 2:49 ` boot-time: straighten code Paul Eggert
2023-08-13 3:26 ` Po Lu
2023-08-13 6:35 ` Paul Eggert
2023-08-13 13:45 ` Bruno Haible
2023-08-13 14:16 ` Bruno Haible
2023-08-13 14:36 ` Bruno Haible
2023-08-13 23:44 ` Po Lu
2023-08-13 23:59 ` Bruno Haible
2023-08-14 1:07 ` Po Lu
2023-08-14 2:14 ` Corwin Brust
2023-08-15 19:57 ` Windows port binaries Bruno Haible
2023-08-16 6:45 ` Po Lu
2023-08-16 11:36 ` Eli Zaretskii
2023-08-17 14:01 ` Bruno Haible
2023-08-17 14:14 ` Eli Zaretskii
2023-08-14 8:02 ` boot-time: straighten code Andreas Schwab
2023-08-14 9:15 ` Bruno Haible
2023-08-14 9:20 ` Andreas Schwab
2023-08-14 10:19 ` Bruno Haible
2023-08-14 10:33 ` Andreas Schwab
2023-08-14 13:51 ` Bruno Haible
2023-08-15 23:03 ` Paul Eggert
2023-08-15 21:12 ` Bruno Haible [this message]
2023-08-16 10:13 ` Bruno Haible
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=4449898.bgbtPGBEXF@nimes \
--to=bruno@clisp.org \
--cc=Emacs-devel@gnu.org \
--cc=bug-gnulib@gnu.org \
--cc=eggert@cs.ucla.edu \
/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).