GNU bug report logs - #61882
emacs-next-pgtk does not find emacs-org-roam, other path issues

Previous Next

Full log

View this message in rfc822 format

From: Csepp <raingloom <at> riseup.net>
To: bokr <at> bokr.com
Cc: Liliana Marie Prikler <liliana.prikler <at> ist.tugraz.at>, 61882 <at> debbugs.gnu.org, Csepp <raingloom <at> riseup.net>
Subject: bug#61882: emacs-next-pgtk does not find emacs-org-roam, other path issues
Date: Wed, 01 Mar 2023 17:11:12 +0100

bokr <at> bokr.com writes:

> Hi,
>
> On +2023-03-01 12:16:56 +0100, Csepp wrote:
> [...]
>> How the hell would my paths affect what's in the bin folder?  Like, the
>> flatpak binary is literally not present in the profile, that's why it's
>> not showing up in $PATH.
>
> Could something in one of your path directories
> accidentally have gotten a name starting with '-' ?
> (or full name '-')?
>
> Surprising things can happen depending on how an
> app rejects an unexpected option, or tries to use it :)
>
> BTW: If you can't delete a file named '-'
>      try emacs dirmode. IIRC emacs seems to see
>      anything and be able to delete it.
>
> Do you have any scripts that are both sourced and executed?
> If so, are they doing return or exit respectively or
> something trickier as intended?

So, first things first:
% guix package -I | grep -E '(flatpak|roam)'
emacs-org-roam      	2.2.2-0.74422df   	out       	/gnu/store/bxxjy8ydm62fr0bckxfrj27xnlvqbfmy-emacs-org-roam-2.2.2-0.74422df
flatpak             	1.14.1            	out       	/gnu/store/mf0k987xvpgk79l74lmdjv9jz8gy8cdf-flatpak-1.14.1

Both are installed.

ls $(guix build flatpak)/bin/
flatpak  flatpak-bisect  flatpak-coredumpctl

The store paths also match.

This path also exists:
$(guix build emacs-org-roam)/share/emacs/site-lisp/org-roam-2.2.2-0.74422df

I don't know the details of how Emacs loads things, but org-roam has an
org-roam-autoloads.el while lsp-mode (a package that does work) does
not.

Some relevant paths:
EMACSLOADPATH=/home/raingloom/.guix-profile/share/emacs/site-lisp
PATH=/home/raingloom/.local/bin:/run/setuid-programs:/home/raingloom/.config/guix/current/bin:/home/raingloom/.guix-profile/bin:/home/raingloom/.guix-profile/sbin:/run/current-system/profile/bin:/run/current-system/profile/sbin

The only additional item is on PATH and at worst it would shadow an
existing flatpak binary.  But it doesn't, there is just a single utility
script there that I should probably get rid of.

Also:
guix shell --check -p .guix-profile
This seems to hang.  Or at least it's taking an awful long time for
something so simple.

I'm running Guix as my system distro and I'm not in the habit of adding
random junk to my dotfiles, so I would be rather surprised if this
turned out to be a path issue, especially when it's obvious the packages
are literally not even showing up in the profile they are supposed to
show up in.

% ls ~/.guix-profile/share/emacs/site-lisp/

This does not print any org-roam directory.

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.