From: Eli Zaretskii <eliz@gnu.org>
To: Jonas Bernoulli <jonas@bernoul.li>
Cc: 58073@debbugs.gnu.org
Subject: bug#58073: 29.0.50; Uninstalled emacs sends startup messages to stderr
Date: Sun, 02 Oct 2022 17:54:43 +0300 [thread overview]
Message-ID: <83mtae1djg.fsf@gnu.org> (raw)
In-Reply-To: <877d1img9g.fsf@bernoul.li> (message from Jonas Bernoulli on Sun, 02 Oct 2022 16:50:19 +0200)
> From: Jonas Bernoulli <jonas@bernoul.li>
> Cc: 58073@debbugs.gnu.org
> Date: Sun, 02 Oct 2022 16:50:19 +0200
>
> #!/bin/sh
> unset EMACSLOADPATH
> exec -a "emacs" "/home/jonas/src/emacs/emacs/src/emacs" "$@"
>
> One problem with that approach is that the wrapper cannot be named
> "emacs". If it is named "emacs", then that somehow trips up Emacs
> and it loads all the preloaded files explicitly during startup (so
> it appears that it cannot find the pdumper file in this case).
>
> Eli, this isn't terribly important, but I was wondering if there is
> something you could do so the name of the wrapper does not matter?
> There might be other legitimate uses of a wrapper around the binary
> from the build directory, other than "I currently have not other
> choice because of what my distro does".
One thing I can suggest is to use the --dump-file=FILE command-line
option inside the script to direct Emacs to its .pdmp file. If you
don't do that, Emacs tries to intuit it using the value of argv[0] it
receives from the OS, and I guess your naming somehow trips that?
next prev parent reply other threads:[~2022-10-02 14:54 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-25 15:15 bug#58073: 29.0.50; Uninstalled emacs sends startup messages to stderr Jonas Bernoulli
2022-09-25 16:02 ` Eli Zaretskii
2022-09-25 18:30 ` Jonas Bernoulli
2022-09-26 7:56 ` Eli Zaretskii
2022-10-02 14:50 ` Jonas Bernoulli
2022-10-02 14:54 ` Eli Zaretskii [this message]
2022-10-02 20:55 ` Jonas Bernoulli
2022-10-02 22:14 ` Stefan Kangas
2022-10-03 2:30 ` Eli Zaretskii
2022-10-03 16:03 ` Jonas Bernoulli
2022-10-03 17:26 ` Eli Zaretskii
2022-10-03 18:51 ` Jonas Bernoulli
2022-10-03 19:01 ` Eli Zaretskii
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=83mtae1djg.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=58073@debbugs.gnu.org \
--cc=jonas@bernoul.li \
/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.