-
-
Notifications
You must be signed in to change notification settings - Fork 99
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
MacOS - Migration from direnv
#36
Comments
Have you added |
Unfortunately I already tried doing that (after installing from source = https://github.com/nix-community/nix-direnv#installation-from-source) but it didn't help. I keep having the same result. |
To exclude any potential error sources, can you just clone the repository and than use the full path to the i.e.:
|
It looks a lot better this way! Thank you for your help 👍 BTW because I did not install it using |
I don't know why it is not picking up your |
Sorry for my late feedback. Here is my
|
@zimbatm I suppose also on macOS, direnv reads |
it's the same logic as on Linux |
I updated https://github.com/nix-community/nix-direnv#with-nix-env to be more clear how to install nix. |
Wouldn't it make sense to consider upstreaming this directly to |
The cache invalidation is not sound. direnv/direnv#238 |
I think the questions has been answered. |
Hello,
I've been using
direnv
for some times now and I wanted to usenix-direnv
to benefit from the caching mechanism but I can't figure out why it does not work on my side.It looks like it keeps using
direnv
whereas I tried to install and configurenix-direnv
following the documentation..envrc
file as below:nix-direnv
usingnix-env
and tried but I still get the following output:direnv allow
in my project directorydirenv
as before:I also tried to install it "from source" as explained in the documentation but I got the same result in the end.
Here are more details about my
nix-env
installed packages:I must have mis-installed something as I am new to
nix
stuff so any help debugging my problem is very much appreciated!Thank you!
The text was updated successfully, but these errors were encountered: