# Startup.jl with \`@spawn @eval\`

**URL:** <https://discourse.julialang.org/t/startup-jl-with-spawn-eval/110076>\
**Category:** General Usage\
**Created:** [February 11, 2024, 7:49pm UTC](https://discourse.julialang.org/t/startup-jl-with-spawn-eval/110076 "2024-02-11T19:49:31Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![jar1](https://avatars.discourse-cdn.com/v4/letter/j/c0e974/32.png) [@jar1](https://discourse.julialang.org/u/jar1)\
**Post date:** [February 11, 2024, 7:49pm UTC](https://discourse.julialang.org/t/startup-jl-with-spawn-eval/110076/1 "2024-02-11T19:49:31Z")

</div>

To reduce startup latency, I’m trying a new startup.jl with

```julia
atreplinit(repl-> Threads.@spawn @eval begin
using Revise
using OhMyREPL
using Compat
...
end)

```

Are there any issues I need to be aware of when doing this?

Edit: It seems to be interfering with autocomplete and syntax highlighting in certain cases.
