Can't use `nvim` from non-administrative terminal on Windows about bob

[MordechaiHadad]

@ok-nick yeah this shouldn't happen at all.. the only time you would need to run terminal in admin mode is when running use cmd, could you run bob erase and try reinstalling a version and see if this happens again?
Also at what folder did bob symbolically linked neovim?

[ok-nick]

It seems to work fine now after trying the steps you suggested. Could've just been a problem with PowerShell?

Also, why does bob require administrative access at all?

[MordechaiHadad]

Could've just been a problem with PowerShell?

I genuinely have no idea, as I got no idea how to reproduce this.

Also, why does bob require administrative access at all?

Only required for linking, I can use mklink but that will require you to use cmd(truly great design idea by microsoft) and dealing with subprocesses errors is a bit more annoying than native rust errors.

[ok-nick]

What needs to be symlinked anyways?

[MordechaiHadad]

@ok-nick neovim binary/exe is symbolically linked to a specific path so you don't really have to manage the PATH variable everytime u switch to a new version.
Anyway can I close this issue(if ur issues is fixed)?

[ok-nick]

The issue is not fixed but it's also not reproducible. I'll close it for now since there's not much more information that could be obtained.