Thanks, that helps, I didn't know about that. It does feel counter intuitive that loading juliarc isn't the default, but maybe there's some hidden logic I don't see.
Though, trying this, I do run into further issues that I'd like to post about.
D:\mydir>julia --startup-file=yes -- myfile.jl arg1 arg2
ERROR: could not open file d:\myprojects\julia\--
in include at boot.jl:261
in include_from_node1 at loading.jl:320
in process_options at client.jl:280
in _start at client.jl:378
So using -- didn't work, which seems to contrast the documentation that describes the command line format as:
julia [switches] -- [programfile] [args...]
And trying it without the -- seperator didn't do much better. I added a `print()` statement to juliarc.jl to validate that it's actually loading. At the command line I do see the print statement I added, "juliarc executed", so I know juliarc was loaded (which sets my LOAD_PATH).
In juliarc I have a series of these statements to set the path:
@everywhere push!(LOAD_PATH,"D:\\path\\to\\my\\files")
I can run `import myfile.jl` from the REPL (without being in the `myfile.jl` directory). But from the command line, it still only looks to HOME.
D:\mydir>julia --startup-file=yes myfile.jl arg1 arg2
juliarc executed
ERROR: could not open file d:\myprojects\julia\myfile.jl
in include at boot.jl:261
in include_from_node1 at loading.jl:320
in process_options at client.jl:280
in _start at client.jl:378