From: Liliana Marie Prikler <liliana.prikler@ist.tugraz.at>
To: Csepp <raingloom@riseup.net>, 61882@debbugs.gnu.org
Subject: bug#61882: emacs-next-pgtk does not find emacs-org-roam, other path issues
Date: Wed, 01 Mar 2023 10:25:41 +0100 [thread overview]
Message-ID: <6525e61f911b5c03547594432ff9102636c9a5cf.camel@ist.tugraz.at> (raw)
In-Reply-To: <87bkld896j.fsf@riseup.net>
Am Mittwoch, dem 01.03.2023 um 02:58 +0000 schrieb Csepp:
> emacs-org-roam is installed in my default profile and all the other
> emacs packages work with the emacs-next-pgtk package in the same
> profile.
> guix shell emacs-org-roam emacs-next-pgtk does not work, guix shell
> emacs-org-roam emacs does.
>
> Possibly related: when I had flatpak installed it was not showing up
> in my profile's bin directory, so I had to open it through guix
> shell.
>
> Maybe this is related to the bug where shell and build produce
> differen derivations?
You probably messed up some of your paths. As a hint,
guix shell --pure -E DISPLAY emacs-next-pgtk emacs-org-roam -- emacs
should run without any issues (apart from your init.el not working as
intended – in that case, supply -Q).
Try adding --check to your invocation of guix shell to see whether your
rc files are borked.
next prev parent reply other threads:[~2023-03-01 9:26 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-01 2:58 bug#61882: emacs-next-pgtk does not find emacs-org-roam, other path issues Csepp
2023-03-01 9:25 ` Liliana Marie Prikler [this message]
2023-03-01 11:16 ` Csepp
2023-03-01 14:40 ` bokr
2023-03-01 16:11 ` Csepp
2023-03-02 7:11 ` Liliana Marie Prikler
2023-03-02 12:39 ` Csepp
[not found] ` <handler.61882.B.167763983720587.ack@debbugs.gnu.org>
2023-04-06 14:59 ` bug#61882: profile is frozen / packages can't be installed Csepp
2023-10-04 2:54 ` bug#61882: emacs-next-pgtk does not find emacs-org-roam, other path issues Maxim Cournoyer
2023-10-08 14:29 ` Csepp
2023-10-08 20:51 ` Maxim Cournoyer
2023-10-10 22:52 ` Csepp
2023-10-11 1:47 ` Maxim Cournoyer
2023-10-15 20:06 ` Csepp
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=6525e61f911b5c03547594432ff9102636c9a5cf.camel@ist.tugraz.at \
--to=liliana.prikler@ist.tugraz.at \
--cc=61882@debbugs.gnu.org \
--cc=raingloom@riseup.net \
/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/guix.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.