I am long time Juno user. I keep coming back to VScode as that is supposedly where things are going. Everytime I come back the intellisense never works. Half the time when you import namspaces with the using statement the methods will not auto populate. I want use VScode but auto completion is such …

There are definitely things I’m missing with VSCode autocomplete (although @pfitzseb might hit me over the head if I bring up autocompletion of DataFrame columns names again…), but could you give a more specific example of what isn’t working? I understand your post to be talking about autocompletio…

Thank you both for your reply. I see now at the bottom of VScode were the environment is. Once I chose this, I saw it that it indexed the namespaces. When I used Juno I used a small script to automate the environment start up and Juno automatically detected the environment. I didn’t realize VScode …

Yeah, the main issue is that there are two separate “environments” in VS Code. Glad things are working for you now.

Something that doesn’t work quite well for me is path completion, e.g. if I start typing CSV.read("tem it correctly gives me CSV.read("templates but then I type / and it gives me nothing, only when I close the " it lists the files in the directory and wrongly insert them after the quote.

Hm, that works fine for me. Are you on Windows? Anyways, please open issues for things like that.

On mac, I realised I wasn’t even in the right directory, but it still correctly list the files there somehow (I guess because they are in my VS workspace). It doesn’t work much better with the right folder though.

The completions for include etc should always be relative to the file path, not anything related to the Julia runtime state.

I noticed that the intellisense works in src/ with my defined module. Unfortunately, in the test folder the intellesense does not work. This makes it cumbersome write test when none of the module your are writing autocomplete. Is there any workaround or solution to this?

has there been any fix to this? I also find this annoying and it costs time.

As far as I can tell no. You can dev the package your developing ( which you should do anyway.) You can use the using statement in the test environment. Again though it get kind of hairy when you split thing into multiple files for organization. I have gotten the habit of keeping two instances vs co…

VScode IntelliSense very frustrating

General Usage

pfitzseb November 24, 2021, 2:01pm 3

The most important thing for getting intellisense for packages is that the environment selected in the lower left of the status bar is correct (in the sense that it contains whatever packages you’re trying to load).

How best to use a custom module?

Topic		Replies	Views
For which packages does VSCode autocomplete work? VS Code intellisense , autocomplete	48	3369	December 5, 2025
Help needed with tracking autocomplete/IntelliSense issue in VS Code VS Code intellisense , autocomplete	0	75	May 25, 2025
VS Code Intellisense for custom package New to Julia package , vscode	5	998	March 23, 2021
VSCode package autocompletion doesnt work if package is not declared in that cell VS Code package , ide , vscode , autocomplete	1	149	July 6, 2025
Intellisense not working for dev'd package VS Code languageserver , intellisense	1	460	August 9, 2022

VScode IntelliSense very frustrating

Related topics