Skip to content
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.

Sign up for GitHub

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

Jump to bottom

nvm v0.31.2, 'nvm ls' throws an exception。 #1126

Closed
TracerLee opened this issue Jun 27, 2016 · 8 comments
Closed

nvm v0.31.2, 'nvm ls' throws an exception。 #1126

TracerLee opened this issue Jun 27, 2016 · 8 comments
Assignees
@ljharb
Labels
bugs Oh no, something's broken :-(

Comments

@TracerLee
Copy link

sed: invalid option -- E
@ljharb
Copy link
Member

ljharb commented Jun 27, 2016

Thanks for the report! What OS and shell are you on? What does nvm debug output?

@ljharb ljharb added bugs Oh no, something's broken :-( needs followup We need some info or action from whoever filed this issue/PR. labels Jun 27, 2016
@ljharb ljharb closed this as completed in c4be39b Jun 28, 2016
@ljharb
Copy link
Member

ljharb commented Jun 28, 2016

Thanks, will be fixed in the next release.

@ljharb ljharb removed the needs followup We need some info or action from whoever filed this issue/PR. label Jun 28, 2016
@ljharb ljharb self-assigned this Jun 28, 2016
@TracerLee
Copy link
Author

@ljharb
I overrided nvm.sh in the directory，and tried the nvm ls again.
The same exception sed: invalid option -- E showed.
How to solve this problem before the next release?

@ljharb
Copy link
Member

ljharb commented Jun 28, 2016 •
edited
Loading

@TracerLee After overriding nvm.sh, you have to re-source it: . "$NVM_DIR/nvm.sh" so that it takes effect. Does that solve it?

@TracerLee
Copy link
Author 

# . nvm.sh
-bash: echo: write error: Broken pipe

# nvm ls
->       v4.4.6
         system
default -> 4.4.6 (-> v4.4.6)
node -> stable (-> v4.4.6) (default)
stable -> 4.4 (-> v4.4.6) (default)
iojs -> N/A (default)

It seems working， is it ?

@ljharb
Copy link
Member

ljharb commented Jun 28, 2016

I'm not sure what the "write error" is from, but yes, that seems to be working :-)

@TracerLee
Copy link
Author

@ljharb Thank you very much~

@TracerLee
Copy link
Author

PS: The OS is CentOS release 5.6

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@ljharb ljharb

Labels
bugs Oh no, something's broken :-(
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@ljharb @TracerLee