nix-community / home-manager

Manage a user environment using Nix [maintainer=@rycee]
https://nix-community.github.io/home-manager/
MIT License
6.92k stars 1.8k forks source link

bug: getconf PATH does not return home manager profiles #5275

Open ibizaman opened 6 months ago

ibizaman commented 6 months ago

Are you following the right branch?

Is there an existing issue for this?

Issue description

Emacs remote editing relies on running getconf PATH on the remote machine to know where to find binaries. This is what that command returns:

$ getconf PATH

/run/current-system/sw/bin:/bin:/usr/bin

Which is far from including everything that's on the path:

$ echo $PATH | tr ':' '\n'

/run/wrappers/bin
/home/ibizaman/.nix-profile/bin
/nix/profile/bin
/home/ibizaman/.local/state/nix/profile/bin
/etc/profiles/per-user/ibizaman/bin
/nix/var/nix/profiles/default/bin
/run/current-system/sw/bin

This issue relates to the paths pertaining to home-manager. Emacs can't find those binaries out of the box.

I found this related issue from a while ago https://releases.nixos.org/nix-dev/2013-June/011250.html which provides a workaround https://releases.nixos.org/nix-dev/2013-June/011251.html. Following that thread, there was a PR merged in a while ago which hardcodes paths in glibc https://github.com/NixOS/nixpkgs/pull/586/files.

I'm not sure how we can even make this configurable if it's currently hardcoded in glibc but I at least wanted to raise this issue for awareness. Feel free to close this as "won't do" if there's no easy way to handle this. I added a section to the Emacs wiki about this https://nixos.wiki/wiki/Emacs

Maintainer CC

No response

System information

- system: `"x86_64-linux"`
 - host os: `Linux 6.1.67, NixOS, 24.05 (Uakari), 24.05.20240408.4cba8b5`
 - multi-user?: `yes`
 - sandbox: `relaxed`
 - version: `nix-env (Nix) 2.18.2`
 - nixpkgs: `/nix/var/nix/profiles/per-user/root/channels/nixos`
stale[bot] commented 3 months ago

Thank you for your contribution! I marked this issue as stale due to inactivity. Please be considerate of people watching this issue and receiving notifications before commenting 'I have this issue too'. We welcome additional information that will help resolve this issue. Please read the relevant sections below before commenting.

If you are the original author of the issue

* If this is resolved, please consider closing it so that the maintainers know not to focus on this. * If this might still be an issue, but you are not interested in promoting its resolution, please consider closing it while encouraging others to take over and reopen an issue if they care enough. * If you know how to solve the issue, please consider submitting a Pull Request that addresses this issue.

If you are not the original author of the issue

* If you are also experiencing this issue, please add details of your situation to help with the debugging process. * If you know how to solve the issue, please consider submitting a Pull Request that addresses this issue.

Memorandum on closing issues

Don't be afraid to manually close an issue, even if it holds valuable information. Closed issues stay in the system for people to search, read, cross-reference, or even reopen – nothing is lost! Closing obsolete issues is an important way to help maintainers focus their time and effort.

dmvianna commented 2 months ago

Please reopen, this makes NixOS unusable with Emacs.

dmvianna commented 2 months ago

Possible solution: https://releases.nixos.org/nix-dev/2013-June/011251.html