# Why navigating to function doesn't always work?

**URL:** <https://discourse.julialang.org/t/why-navigating-to-function-doesnt-always-work/131670>\
**Category:** VS Code\
**Created:** [August 18, 2025, 6:49am UTC](https://discourse.julialang.org/t/why-navigating-to-function-doesnt-always-work/131670 "2025-08-18T06:49:52Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![Alex1](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/alex1/32/11771_2.png) [@Alex1](https://discourse.julialang.org/u/Alex1)\
**Post date:** [August 18, 2025, 6:49am UTC](https://discourse.julialang.org/t/why-navigating-to-function-doesnt-always-work/131670/1 "2025-08-18T06:49:52Z")

</div>

When I shift + click on some function names VS Code opens its definition. But sometimes, maybe even most of the time, it doesn’t.

Why and how to fix it?

Does it matter if function declared as `function some() ... end` vs `some() = ...`?

Or if Revise used `includet('./somelib.jl")` - with function in main scope. Or module `includet('./somemodule.jl'); using .Somemodule`.

Ot broadcasted version `includet.(["../lib/a.jl", "../lib/b.jl",])`.