-
Notifications
You must be signed in to change notification settings - Fork 447
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
the mistake about Shell Setup #1110
Comments
it says fnm is not available. Maybe the initialization happens before cargo is added to PATH? |
nonono, I installed the cargo first, and then I ran |
Hello, this error has been resolved. When there is Chinese in the environment variable, |
Can you please attach the output you get? So we can escape it properly 🙏 |
Hey. Similar issue here, almost opened a new ticket. For me, my userprofile directory on windows contains the letter 'á':
To the environment variables it added After fixing it manually I reloaded the path Then I tried playing around a bit more:
After trying fnm env, it kinda killed my PATH as it is, and I had to reload it. Trying to use fnm env from the startup powershell script results in the same error. I then tried using it from a terminal with administrator priviliges just to see what would happen. After installing fnm there and trying to
So yeah... it is kind of broken, not only with chinese characters. Probably something something windows' own character encoding messing with stuff. |
I haven’t used windows in almost 10 years. Would be great to get your assistance in what needs to change in the fnm env output 🙏 |
Sadly fnm env's output does not seem to be the only thing broken. I tried uninstalling via winget and that also failed. The env variable path that was set was also incorrect. It's probably the handling of the OS path strings in general that's the problem. That said in the fnm env case specifically this line is to blame: My rust and knowledge on character encodings are far from anywhere close to even understand what needs to be changed, but I'll take a look when my time permits. Edit: Also I just noticed that some |
Hi, bumping on this issue as it is recent and seems related, but I'm getting some similar issues with this. It definitely was working on windows as I've successfully used it previously, but it now isn't. When trying the install step in PowerShell I get:
|
Just further on this - the line |
What fnm version are you on? |
Hi Gal 1.37.1
Ralph
On 05/07/2024 20:34, Gal Schlezinger wrote:
What fnm version are you on?
--
Reply to this email directly, view it on GitHub [1], or unsubscribe
[2].
You are receiving this because you commented.Message ID:
***@***.***>
|
interesting. would be great to understand what is special about your setup. i have some tests and i need to know how to repro 🙏 |
Same problem for me -___- and its the same with the special characters. My username on my pc has a ü. The path winget made changed it to Ã1⁄4 and changing the path manually made it so I can run fnm. I will update here again if I run into more problems. If I can help with anything eg. setting up to repro then I will gladly help ^^ Edit 1 When i run this line it just accepts it and returns nothing. Then when i try to call fnm its no longer in path. |
There is nothing special about customizing it. The issue is the username, which has characters other than English. 90% of tools designed for programmers (especially on windows) suffer from this problem. It's just not so obvious. Either it works, but incorrectly (as in this case), or it simply refuses to work you can check this by using the same command First of all: it's just inconvenient to write such a thing in each console configuration, because you can open any console in the terminal and the tool won't work (for example in vs code). Second: unusual behavior when there is no content in with the absence of the |
I suggest you just reinstall windows if you can and change your username to English letters. I guarantee you will breathe a lot easier. |
I installed fnm with cargo, used powershell.
But after I add the following to the end of my profile file:
fnm env --use-on-cd | Out-String | Invoke-Expression
the mistake would come out:
I'm sure the env var is corrent
The text was updated successfully, but these errors were encountered: