-
Notifications
You must be signed in to change notification settings - Fork 138
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
Missing environment variables (PS1, ...) #3
Comments
Off the top of my head no, to be honest all I did for nodenv was copy rbenv and change a few bits to work with node instead of ruby, so I'm not that familiar with the inner workings of the code. I'll try and take a look next week when I have some more time |
Sorry it's been so long, keep meaning to look at this and never quite getting to it. Have been looking at boxen a bit lately and I noticed that the default nodenv it uses is @wfarr's version. Are you sure you're using my version? |
@OiNutter is there a Boxen module for your version of nodenv? |
@armanm No, it's something that's currently being discussed but I need to do some investigating to see what's required to support precompiled binaries, assuming the library doesn't already. Unfortunately my day job has been crazy busy so my OS stuff is taking a hellish back seat. |
As this seems to clearly be an issue with @wfarr's version, can this be closed? |
I'm using
nodenv
withboxen
. I have anode
application that inspects thePS1
environment variable to see what the current command line prompt is. (It needs to pass this environment variable then to other programs it forks).However it seems like either
nodenv
orboxen
are removing this variable. All environment variables of the formPS*
(where*
is a digit) are blocked and not accessible throughprocess.env.PS1
.Any idea of what may be causing this ?
The text was updated successfully, but these errors were encountered: