From: "Gerd Möllmann" <gerd.moellmann@gmail.com>
To: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: Eli Zaretskii <eliz@gnu.org>, 66022@debbugs.gnu.org
Subject: bug#66022: 30.0.50; kmacro overwriting global keybindings
Date: Wed, 20 Sep 2023 11:57:28 +0200 [thread overview]
Message-ID: <4418cdb1-ddba-41ce-acfe-8f8b4453292c@gmail.com> (raw)
In-Reply-To: <jwvy1h3cpcc.fsf-monnier+emacs@gnu.org>
On 23-09-18 20:24 , Stefan Monnier wrote:
>> Do you think the following plan make ssense?
>>
>> - I assume that a build from git clean -xdf shows all the steps that
>> must happen with 100% certainty.
>>
>> - I'd then make bootstrap + look for a difference.
>>
>> - Then same procedure for simple make in the toplevel dir,
>> - after there is only a C file changed
>> - after only a Lisp file is changed
>
> Sounds good.
>
> You might also want to compare the timestamp of `loaddefs.elc` compared to
> the timestamp of `emacs.pdmp` in your build directory (assuming you
> still have it around).
I think I've found something.
Assume I git pull, and emacs-lisp/comp.el is modified in a way that
loaddefs gets regenerated and written to disk. Then do a toplevel
gmake. After that, I see the following:
~/emacs/master/ > ll lisp/loaddefs.el* src/emacs.pdmp
lisp/emacs-lisp/comp.*
nextstep/Emacs.app/Contents/Resources/lisp/loaddefs*
nextstep/Emacs.app/Contents/MacOS/libexec/Emacs.pdmp
-rw-r--r-- 1 gerd staff 1.4M Sep 20 11:31 lisp/loaddefs.el
-rw-r--r-- 1 gerd staff 1.4M Sep 20 11:32 lisp/loaddefs.elc
-rw-r--r-- 2 gerd staff 16M Sep 20 11:32 src/emacs.pdmp
-rw-r--r-- 1 gerd staff 188K Sep 20 11:31 lisp/emacs-lisp/comp.el
-rw-r--r-- 1 gerd staff 399K Sep 20 11:32 lisp/emacs-lisp/comp.elc
-rw-r--r-- 1 gerd staff 369K Sep 20 10:55
nextstep/Emacs.app/Contents/Resources/lisp/loaddefs.el.gz
-rw-r--r-- 1 gerd staff 1.4M Sep 20 10:56
nextstep/Emacs.app/Contents/Resources/lisp/loaddefs.elc
-rw-r--r-- 1 gerd staff 16M Sep 20 11:32
nextstep/Emacs.app/Contents/MacOS/libexec/Emacs.pdmp
Note that the pdmp in Emacs.app is new, while the loaddefs under
nextstep are old.
After gmake install:
~/emacs/master/ > ll lisp/loaddefs.el* src/emacs.pdmp
lisp/emacs-lisp/comp.*
nextstep/Emacs.app/Contents/Resources/lisp/loaddefs*
nextstep/Emacs.app/Contents/MacOS/libexec/Emacs.pdmp
-rw-r--r-- 1 gerd staff 1.4M Sep 20 11:31 lisp/loaddefs.el
-rw-r--r-- 1 gerd staff 1.4M Sep 20 11:32 lisp/loaddefs.elc
-rw-r--r-- 2 gerd staff 16M Sep 20 11:32 src/emacs.pdmp
-rw-r--r-- 1 gerd staff 188K Sep 20 11:31 lisp/emacs-lisp/comp.el
-rw-r--r-- 1 gerd staff 399K Sep 20 11:32 lisp/emacs-lisp/comp.elc
-rw-r--r-- 1 gerd staff 369K Sep 20 11:31
nextstep/Emacs.app/Contents/Resources/lisp/loaddefs.el.gz
-rw-r--r-- 1 gerd staff 1.4M Sep 20 11:32
nextstep/Emacs.app/Contents/Resources/lisp/loaddefs.elc
-rw-r--r-- 1 gerd staff 16M Sep 20 11:32
nextstep/Emacs.app/Contents/MacOS/libexec/Emacs.pdmp
Means to me that if I just gmake, expecting that could not possibly
change Emacs.app, I'm quite mistaken. Instead, I now have an
inconsistent Emacs.app.
Does that make sense?
Has someone maybe an idea why the pdmp gets installed so early?
next prev parent reply other threads:[~2023-09-20 9:57 UTC|newest]
Thread overview: 54+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-16 6:38 bug#66022: 30.0.50; kmacro overwriting global keybindings Gerd Möllmann
2023-09-16 7:01 ` Andreas Schwab
2023-09-16 7:36 ` Gerd Möllmann
2023-09-16 18:44 ` Gerd Möllmann
2023-09-16 20:06 ` Andreas Schwab
2023-09-16 20:18 ` Gerd Möllmann
2023-09-16 20:37 ` Andreas Schwab
2023-09-16 20:55 ` Gerd Möllmann
2023-09-17 6:05 ` Eli Zaretskii
2023-09-17 6:31 ` Gerd Möllmann
2023-09-17 6:40 ` Gerd Möllmann
2023-09-17 6:47 ` Eli Zaretskii
2023-09-17 6:52 ` Gerd Möllmann
2023-09-17 8:53 ` Eli Zaretskii
2023-09-17 8:58 ` Gerd Möllmann
2023-09-17 9:18 ` Eli Zaretskii
2023-09-17 9:50 ` Gerd Möllmann
2023-09-17 10:02 ` Gerd Möllmann
2023-09-17 10:45 ` Eli Zaretskii
2023-09-17 11:07 ` Gerd Möllmann
2023-09-17 11:23 ` Eli Zaretskii
2023-09-17 11:26 ` Gerd Möllmann
2023-09-17 17:13 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-09-17 18:10 ` Gerd Möllmann
2023-09-17 19:10 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-09-18 14:36 ` Gerd Möllmann
2023-09-18 14:42 ` Gerd Möllmann
2023-09-18 14:52 ` Eli Zaretskii
2023-09-18 14:56 ` Gerd Möllmann
2023-09-18 15:09 ` Eli Zaretskii
2023-09-18 15:18 ` Gerd Möllmann
2023-09-18 15:25 ` Gerd Möllmann
2023-09-18 16:25 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-09-18 16:33 ` Gerd Möllmann
2023-09-18 17:00 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-09-18 17:54 ` Gerd Möllmann
2023-09-18 18:24 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-09-18 18:27 ` Gerd Möllmann
2023-09-20 9:57 ` Gerd Möllmann [this message]
2023-09-20 14:11 ` Eli Zaretskii
2023-09-20 14:22 ` Gerd Möllmann
2023-09-20 15:04 ` Eli Zaretskii
2023-09-20 15:09 ` Gerd Möllmann
2023-09-20 16:56 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-09-20 18:24 ` Gerd Möllmann
2023-09-20 18:50 ` Alan Third
2023-09-20 19:04 ` Gerd Möllmann
2023-09-21 5:13 ` Gerd Möllmann
2023-09-20 19:05 ` Alan Third
2023-09-18 17:03 ` Eli Zaretskii
2023-09-18 17:42 ` Gerd Möllmann
2023-09-18 16:23 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-09-18 17:19 ` Eli Zaretskii
2023-10-04 5:01 ` Gerd Möllmann
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=4418cdb1-ddba-41ce-acfe-8f8b4453292c@gmail.com \
--to=gerd.moellmann@gmail.com \
--cc=66022@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=monnier@iro.umontreal.ca \
/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.