# \`Revise.jl\` dosn't work on \`include\`ed files

**URL:** <https://discourse.julialang.org/t/revise-jl-dosnt-work-on-include-ed-files/26872>\
**Category:** General Usage\
**Created:** [July 27, 2019, 3:18am UTC](https://discourse.julialang.org/t/revise-jl-dosnt-work-on-include-ed-files/26872 "2019-07-27T03:18:36Z")\
**Posts on this page:** 1\
**Showing post:** 4

<div class="post-metadata">

**Author:** ![tim.holy](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/tim.holy/32/52_2.png) [@tim.holy](https://discourse.julialang.org/u/tim.holy)\
**Post date:** [July 27, 2019, 9:26am UTC](https://discourse.julialang.org/t/revise-jl-dosnt-work-on-include-ed-files/26872/4 "2019-07-27T09:26:22Z")

</div>

You should think of `using` and `import` as the “real” ways to track code. `includet` is deliberately intended to be “track just this file”—it’s designed as the manual alternative to the automated smarts of `using` and `import`. You can turn `Tvaccine` into a package in seconds ([GitHub - invenia/PkgTemplates.jl: Create new Julia packages, the easy way](https://github.com/invenia/PkgTemplates.jl)) or use `push!(LOAD_PATH, dir-of-Tvaccine.jl)`. Then `using Tvaccine` should do what you want.

The second issue is a [known bug](https://github.com/timholy/Revise.jl/issues/107). Since that state of affairs is rather transitory (once you add the file and restart everything works going forward), it’s not really been a priority of mine. For anyone really bugged by this, there was a [start on a fix](https://github.com/timholy/Revise.jl/pull/232) that could use help getting over the line. Unfortunately, the internal architecture of Revise has changed substantially since then so I suspect it’s not a small project.

---

_[View the full topic](https://discourse.julialang.org/t/revise-jl-dosnt-work-on-include-ed-files/26872)._