# VS Code constant pain point
**URL:** https://discourse.julialang.org/t/vs-code-constant-pain-point/77388
**Category:** General Usage
**Tags:** vscode
**Created:** [March 4, 2022, 3:07am UTC](https://discourse.julialang.org/t/vs-code-constant-pain-point/77388 "2022-03-04T03:07:38Z")
**Posts on this page:** 6
**Page:** 1
### Author:  [@PetrKryslUCSD](https://discourse.julialang.org/u/PetrKryslUCSD)
#### Post date: [March 4, 2022, 3:07am UTC](https://discourse.julialang.org/t/vs-code-constant-pain-point/77388/1 "2022-03-04T03:07:38Z")
I like a lot of things about Julia in VS Code, but one thing where it constantly falls short is
lookup of symbols defined in user packages. Standard-library code is fine
but the user code is always a problem
As the status shows, the `meshboundary` function defined in `FinEtools`
_should_ be available, but isn’t.
- Is this actually working for anyone at this point? I mean the lookup of symbols in user packages?
- I recently discovered that this was not possible for packages that were developed. But my understanding was that this should work for packages which are added to the project. Am I wrong?
- Is there some way in which I can check the list of symbols that are currently available?
Latest everything: editor, extension, Julia. On Windows.
---
### Author:  [@PetrKryslUCSD](https://discourse.julialang.org/u/PetrKryslUCSD)
#### Post date: [March 4, 2022, 3:44am UTC](https://discourse.julialang.org/t/vs-code-constant-pain-point/77388/2 "2022-03-04T03:44:46Z")
Update: I have previously tried, repeatedly, to shutdown Julia REPL. That did not help.
But then I shut down the editor and restarted, and voila, the symbols are back.
So something died and needed restarting. Any idea what that might have been?
---
### Author:  [@jules](https://discourse.julialang.org/u/jules)
#### Post date: [March 4, 2022, 5:53am UTC](https://discourse.julialang.org/t/vs-code-constant-pain-point/77388/3 "2022-03-04T05:53:44Z")
You have to check that the correct environment is selected in the toolbar at the bottom. To me it often happens that this for some reason differs from the currently activated env. It should usually be set to the env in the current working directory when starting up, that could be why a restart helped.
---
### Author:  [@fredrikekre](https://discourse.julialang.org/u/fredrikekre)
#### Post date: [March 4, 2022, 10:15am UTC](https://discourse.julialang.org/t/vs-code-constant-pain-point/77388/4 "2022-03-04T10:15:45Z")
Isn’t this just another instance of [LanguageServer does not index active project/package (julia-vscode/LanguageServer.jl#988)](https://github.com/julia-vscode/LanguageServer.jl/issues/988) ? Xref [your post from some days ago](https://discourse.julialang.org/t/vs-code-no-implementation-found-in-developed-package/77198/).
Thats at least the only problem I have seen myself using LS from vim.
---
### Author:  [@PetrKryslUCSD](https://discourse.julialang.org/u/PetrKryslUCSD)
#### Post date: [March 4, 2022, 2:26pm UTC](https://discourse.julialang.org/t/vs-code-constant-pain-point/77388/5 "2022-03-04T14:26:58Z")
No, I don’t think so. Here, the symbols were not visible in `add`ed packages. Previously, I could not get it to work with `dev`ed packages, but `add`ing the package fixed the problem.
---
### Author:  [@PetrKryslUCSD](https://discourse.julialang.org/u/PetrKryslUCSD)
#### Post date: [March 4, 2022, 2:43pm UTC](https://discourse.julialang.org/t/vs-code-constant-pain-point/77388/6 "2022-03-04T14:43:19Z")
No, the environment was correct.