[.tool-versions] problems

[wakefun]

The configuration file for vfox is .tool-versions. After setting up this file in the project, I've encountered two issues:

1. The sdk version set within the project does not install automatically.
   For example, if I configure nodejs 16.20.1, but if my system hasn't previously installed this specific version of nodejs via vfox install, then vfox's feature of automatic version switching will fail and it will default to using the global nodejs version.

2. When I have set the global nodejs version to v18.19.1 and enter a project directory where the nodejs version is automatically changed to 16.20.1 according to the configuration file within that project, upon exiting back to another directory such as by typing cd $HOME, the nodejs version remains at 16.20.1 instead of reverting back to the globally configured v18.19.1.

Additionally, here's a small suggestion:
When using vfox use -p sdk@version, if there's an existing .tool-versions file in the current directory and if there’s a discrepancy between versions set by current command and those configured in that file, consider adding a default action which would be: automatically update the file with currently set versions.

[aooohan]

The configuration file for vfox is .tool-versions. After setting up this file in the project, I've encountered two issues:

1. The sdk version set within the project does not install automatically.
   For example, if I configure nodejs 16.20.1, but if my system hasn't previously installed this specific version of nodejs via vfox install, then vfox's feature of automatic version switching will fail and it will default to using the global nodejs version.

Yes, there is no auto-installation feature yet. But we can raise an issue to record this feature.

2. When I have set the global nodejs version to v18.19.1 and enter a project directory where the nodejs version is automatically changed to 16.20.1 according to the configuration file within that project, upon exiting back to another directory such as by typing cd $HOME, the nodejs version remains at 16.20.1 instead of reverting back to the globally configured v18.19.1.

This is the current strategy. You can raise an issue to record it and optimize it later.

Additionally, here's a small suggestion: When using vfox use -p sdk@version, if there's an existing .tool-versions file in the current directory and if there’s a discrepancy between versions set by current command and those configured in that file, consider adding a default action which would be: automatically update the file with currently set versions.

That's the way it is now. When vfox use -p is executed at that time, the file is created if it does not exist, and updated if it does.

[airtonix]

This is the current strategy. You can raise an issue to record it and optimize it later.

Are you saying it's by design that vfox results in surprising behaviour?

asdf doesn't behave like this (largely due to it being a more reliable shim based approach)