From: Maxim Cournoyer <maxim.cournoyer@gmail.com>
To: Leo Prikler <leo.prikler@student.tugraz.at>
Cc: 47458@debbugs.gnu.org
Subject: bug#47458: Terrible UX upgrading Emacs in Guix
Date: Tue, 06 Apr 2021 08:09:02 -0400 [thread overview]
Message-ID: <87k0pfpqch.fsf@gmail.com> (raw)
In-Reply-To: <0491bf7a885f44dbf62e2ca3b21fb5671daed5ec.camel@student.tugraz.at> (Leo Prikler's message of "Sun, 04 Apr 2021 09:49:31 +0200")
Hi Leo!
Leo Prikler <leo.prikler@student.tugraz.at> writes:
[...]
>> Shouldn't we wrap all the binaries to be on the safe side? Things
>> such
>> as emacsclient probably ought to have EMACSLOADPATH set correctly,
>> no?
> The remaining binaries are
> - emacsclient, which inherits its EMACSLOADPATH from the server it
> connects to
> - ctags, ebrowse and etags, which are helper binaries, that don't seem
> to rely on EMACSLOADPATH at all. (Or is there an indicator, that they
> do?)
> - .-real binaries, that should only be wrapped once.
> We could relax the regex to include the upper two, but I don't think
> it's necessary to do so.
OK, thanks for the explanation, it makes sense.
[...]
> I'd like to avoid pushing this to master just yet, because we also have
> changes in the Emacs build system to discuss and I don't want to cause
> an "Emacs world" rebuild twice in a row. That said, I'm including this
> patch in wip-emacs with the plan to push to master or staging once
> everything there is resolved.
Sure! Which changes do you have in mind? Are they already on the
tracker for review?
Thank you,
Maxim
next prev parent reply other threads:[~2021-04-06 12:10 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-29 2:02 bug#47458: Terrible UX upgrading Emacs in Guix Mark H Weaver
2021-03-29 8:07 ` Leo Prikler
2021-03-29 8:24 ` Maxime Devos
2021-03-29 8:43 ` Leo Prikler
[not found] ` <20210330184101.7643-1-leo.prikler@student.tugraz.at>
2021-04-04 4:35 ` Maxim Cournoyer
2021-04-04 7:49 ` Leo Prikler
2021-04-06 12:09 ` Maxim Cournoyer [this message]
2021-04-06 15:49 ` Leo Prikler
2021-04-07 19:46 ` Maxim Cournoyer
2021-05-20 13:24 ` Maxim Cournoyer
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://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87k0pfpqch.fsf@gmail.com \
--to=maxim.cournoyer@gmail.com \
--cc=47458@debbugs.gnu.org \
--cc=leo.prikler@student.tugraz.at \
/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/guix.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).