# julia.additionalArgs -e (...) REPL not recognised

**URL:** <https://discourse.julialang.org/t/julia-additionalargs-e-repl-not-recognised/124466>\
**Category:** VS Code\
**Tags:** question\
**Created:** [January 6, 2025, 12:49pm UTC](https://discourse.julialang.org/t/julia-additionalargs-e-repl-not-recognised/124466 "2025-01-06T12:49:36Z")\
**Posts on this page:** 1\
**Showing post:** 8

<div class="post-metadata">

**Author:** ![eldee](https://avatars.discourse-cdn.com/v4/letter/e/b5a626/32.png) [@eldee](https://discourse.julialang.org/u/eldee)\
**Post date:** [January 7, 2025, 12:23pm UTC](https://discourse.julialang.org/t/julia-additionalargs-e-repl-not-recognised/124466/8 "2025-01-07T12:23:29Z")

</div>

Such an approach (see also [Understanding the startup.jl file -- is there a environment-specific version? - #2 by c42f](https://discourse.julialang.org/t/understanding-the-startup-jl-file-is-there-a-environment-specific-version/77998/2)) could indeed work. Presumably there is also a way to check which terminal is being used, and if is the VS Code one you could then load development-specific startup code.

---

_[View the full topic](https://discourse.julialang.org/t/julia-additionalargs-e-repl-not-recognised/124466)._