-
-
Notifications
You must be signed in to change notification settings - Fork 7.7k
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
[spam] #2644
Labels
non-issue / invalid
This isn't relevant to nvm, or turned out to be something unrelated.
Comments
ljharb
changed the title
nvm is nota supported when installed from homebrew altho this issue seems unrelated please brew uninstall it and reinstall it from the only supported install method the install script in the readme
[spam]
Nov 2, 2021
ljharb
added
the
non-issue / invalid
This isn't relevant to nvm, or turned out to be something unrelated.
label
Nov 2, 2021
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
nvm is not supported when installed from homebrew (altho this issue seems unrelated); please brew uninstall it and reinstall it from the only supported install method (the install script in the readme).
I'm not sure why
nodenv init
would matter, since this is nvm, not nodenv? Similarly, I'm not sure why there'snodenv
in your path anywhere if you're using nvm. Can you elaborate?I can reproduce this issue, and I completely agree that when it's in a pipe, it shouldn't output colors. I don't think "TTY-ness" should dictate that, since it's not about interactivity (but your suggestion would certainly work, albeit with a lot of added complexity in nvm).
Using some form of this technique should work here - when I naively use it in
nvm_has_colors
, the "ls" part of thenvm ls
output works properly, but in an actual terminal it causes the "alias" part of thenvm ls
output to drop its colorization, so some finesse might be needed. tagging in @gitburd and @naomiquinones for help.Publicado originalmente por @ljharb en #2497 (comment)
The text was updated successfully, but these errors were encountered: