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.

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

Update fnm link in README #2541

Draft
wants to merge 1 commit into
base: master
Choose a base branch
from
Draft

Update fnm link in README #2541

wants to merge 1 commit into from

Conversation

kidonng
Copy link

@kidonng kidonng commented Jul 18, 2021

fnm has been renamed to nvm.fish and the repo has been transferred to https://github.com/jorgebucaran.

@ljharb
Copy link
Member

ljharb commented Jul 18, 2021

That’s unfortunate; i thought @jorgebucaran and i went through this with the name not being “nvm” years ago.

@jorgebucaran
Copy link

Yes, I renamed it to fnm, but when that other fnm came into the picture a few years ago, I went back to nvm, adding .fish to the name, so its actual name is nvm.fish. Not nvm. The README also states in its first sentence that we're not affiliated to this project.

Not that POSIX-compatible script.

@ljharb
Copy link
Member

ljharb commented Jul 18, 2021

So rather than ask the new fnm to rename to avoid the conflict, you decided to create a new conflict?

@jorgebucaran
Copy link

In my view, there is no conflict. nvm is an sh script. nvm.fish is a Fish one.

There's also a thread on Twitter with more background if anyone is interested. Also Schniz/fnm#3.

@kidonng
Copy link
Author

kidonng commented Jul 18, 2021

Yep, I stand with @jorgebucaran here. It may be the case years ago, but I don't think nowadays anyone consider nvm to refer to something else than this project.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants