From: Stefan Monnier via "Bug reports for GNU Emacs, the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
To: "Gerd Möllmann" <gerd.moellmann@gmail.com>
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 12:56:22 -0400 [thread overview]
Message-ID: <jwvmsxgairs.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: <923759b2-d4b4-4b7a-b3f2-1f594d8acc16@gmail.com> ("Gerd Möllmann"'s message of "Wed, 20 Sep 2023 16:22:24 +0200")
>> Any idea which place in the Makefile's or in loadup.el does that?
>
> I think nextstep/Makefile.in contains
>
> # FIXME: Don't install the dump file into the app bundle when
> # self-contained install is disabled.
> ${ns_applibexecdir}/Emacs.pdmp: ${ns_appdir} ${ns_check_file}
> ../src/emacs${EXEEXT}.pdmp
> ${MKDIR_P} ${ns_applibexecdir}
> cp -f ../src/emacs${EXEEXT}.pdmp $@
>
> and the "all" target has that the pdmp as a dependency.
Sounds like a bug, yes: either the same thing should be done for all the
files in ${ns_applibexecdir} or it should be done for none.
This said, I'm, 100% unfamiliar with the way the `Emacs.app` directory
is built, so maybe this is a feature rather than a bug.
> I have no idea though what the comment means, or if the cp if necessary
> for something.
The FIXME sounds to me like it's hinting at the same bug you're seeing
(tho maybe another manifestation of it), and since there's a FIXME
I presume that fixing it isn't as simple as removing this rule :-)
Stefan
next prev parent reply other threads:[~2023-09-20 16:56 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
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 [this message]
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
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=jwvmsxgairs.fsf-monnier+emacs@gnu.org \
--to=bug-gnu-emacs@gnu.org \
--cc=66022@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=gerd.moellmann@gmail.com \
--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 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).