# Is there an Official Shebang for Julia

**URL:** <https://discourse.julialang.org/t/is-there-an-official-shebang-for-julia/51581>\
**Category:** General Usage\
**Created:** [December 10, 2020, 3:24am UTC](https://discourse.julialang.org/t/is-there-an-official-shebang-for-julia/51581 "2020-12-10T03:24:15Z")\
**Posts on this page:** 1\
**Showing post:** 4

<div class="post-metadata">

**Author:** ![GHTaarn](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/ghtaarn/32/216007_2.png) [@GHTaarn](https://discourse.julialang.org/u/GHTaarn)\
**Post date:** [May 16, 2023, 9:30am UTC](https://discourse.julialang.org/t/is-there-an-official-shebang-for-julia/51581/4 "2023-05-16T09:30:54Z")

</div>

For the benefit of future readers of this thread, the FAQ has now changed and recommends

```julia
#!/usr/bin/env -S julia -t 4 -- project

```

as the header for executable Julia scripts (where you may change the Julia command line options to suit your needs).

None of the above headers work if `julia` is an alias, so I made the following to handle this situation as well:

```julia
#!/usr/bin/bash -i
#=
    exec bash -ic 'julia -t 4 --project "$@"' Julia "${BASH_SOURCE[0]}" "$@"
=#

println.(ARGS, '.')

```

Again, `-t 4 --project` is just an example of some Julia command line options that one could use and `println.(ARGS, '.')` is just an example of some Julia code.

This header is much more complex than the one from the FAQ, but as far as I can see it is more general. Please let me know if you find any issues with it, I have only tested it on myself.

---

_[View the full topic](https://discourse.julialang.org/t/is-there-an-official-shebang-for-julia/51581)._