Should "emacsWrapper" also wrap PATH and PYTHONPATH?

[adisbladis]

Issue description

Currently emacsWrapper wraps the $EMACSLOADPATH environment variable. I also think it would be useful to wrap other environment variables such as $PATH and $PYTHONPATH.

This would make it a whole lot easier and intuitive to work with certain modes like flycheck which checks $PATH for checkers and linters and jedi-mode which requires some python dependencies both in $PATH and $PYTHONPATH.

I want to be able to add non-elisp packages to emacsWithPackages and have things just work.

Technical details

• System:
  18.03.git.fd3bb25895M (Impala)
• Nix version:
  nix-env (Nix) 1.11.15
• Nixpkgs version:
  "18.03.git.fd3bb25895M"

[peterhoeg]

The problem with that approach is that we would potentially need to wrap everything in existence.

I use a combination of emacs, direnv and emacs-direnv to set up things up on a project level. Works OK so far.

[bkchr]

I also use direnv and emacs-direnv to load all the required tools into the path for emacs. That works relative good.

[adisbladis]

Direnv + emac-direnv sounds like a very nice combination but it doesn't solve the core issue of making non-elisp tooling available.
I personally want to use the same tooling regardless of project setup.

@peterhoeg What makes you think you'd probably need to "wrap everything in existence"?
Are you thinking about scope creep?

[peterhoeg]

Direnv + emac-direnv sounds like a very nice combination but it doesn't solve the core issue of making non-elisp tooling available.

Actually it does. It means you can have all your python stuff available in one project and haskell in another without them ever stepping on each other and the dependencies defined per project, so whoever else is working on that same project will have everything available as well.

I personally want to use the same tooling regardless of project setup.

For some things, sure. So you wrap what you need - I don't think we can decide on what everybody needs which is the problem.

[lukateras]

I'd like emacsWithPackages to wrap $PATH, too.

[stale]

Thank you for your contributions.

This has been automatically marked as stale because it has had no activity for 180 days.

If this is still important to you, we ask that you leave a comment below. Your comment can be as simple as "still important to me". This lets people see that at least one person still cares about this. Someone will have to do this at most twice a year if there is no other activity.

Here are suggestions that might help resolve this more quickly:

1. Search for maintainers and people that previously touched the related code and @ mention them in a comment.
2. Ask on the NixOS Discourse.
3. Ask on the #nixos channel on irc.freenode.net.

[adisbladis]

I've since been convinced that wrapping $PATH is the wrong thing to do.