James Hegedus

It depends on what the intent is. For each file, are we saying `.bash` because the script requires Bash features to execute? `.sh` is nondescript given the confusion with bourne...

@Stratus3D I agree 100% with your assessment.

https://github.com/asdf-vm/asdf/issues/822 May also be solved by this.

@xtyrrell I would like the soln to only show one error and for the correct case. Adding "also try `asdf reshim`" would be easier but not the ideal soln. How...

So, correct me if I am understanding this wrong, we would need to modify the `search_path` command's search for `.tool-versions` when shims are executed from another tool. Anyone have suggestions...

@Stratus3D Is this something we can actually resolve by changing code in this repository, is it a problem with asdf core, or can we call this something we need to...

We could have a "kitchen sink" page in the docs under a recipes section that captures these edge cases where we document and update the caveats. It might help direct...

This issue happens to me with some tools and not others. I have experienced this with Rust Analyzer myself, but didn't stick with Rust long enough to resolve or investigate...

@spikespaz As you say in the initial issue: >The IDEs and other tools should be able to find software managed by asdf They can if they look in the right...

>it's such a fundamental issue for users of asdf, like it's one of the first things I stumbled on I am not sure what we can do about it though....