Buggy behavior when `jpm_tree` exists

[CFiggers]

Currently two (at least) issues are appearing when there is a jpm_tree containing local files:

1. Some on-hover documentation points toward the jpm_tree, especially module imports (even when the module is not being imported from jpm_tree)
2. When (import)ing, any symbol inserted will be accepted as valid, even when that module does not exist; any modules contained in jpm_tree will then be suggested by autocompletion namespaced under that symbol
   • (This seems to be happening on each keystroke, meaning that if (import random) is typed, r, ra, ran, rand, etc. are all evaluated)

Probably has something to do with the way modules are being identified in jpm_tree---more experimentation needed.

[sogaiu]

Some more data about a possibly related case follows.

Preparation steps:

# time of writing 80ef23e0
git clone https://github.com/CFiggers/janet-lsp
cd janet-lsp
jpm -l deps

Using vscode-janet-plus-plus v1.1.2, take a look at any of the following files from the cloned janet-lsp project:

• doc.janet
• eval.janet
• lookup.janet
• misc.janet

Here, for each file, the last instance of deftest is underlined in red.

There is an associated message:

unknown symbol deftest

For reference, I currently have "Don't Discover Jpm Tree" unchecked for vscode-janet-plus-plus.

---

OS: Void Linux
VSCode: 1.85.1 (vscode-1.85.1 from void-packages)