On 16 December 2013 23:45, David van Leeuwen <[email protected]> wrote: > which worked on MacOS, but not on Linux. For the latter, I had to make a > sh-script called "julia -F" (including a space in the file name!) that read > > #!/bin/sh > exec julia -F $*
Interesting. > I tend to put more and more in modules that sooner/later end up in ~/.julia > , and I don't use the .juliarc.jl LOAD_PATH adjustment anymore. If the > script needs a specific loadpath, I just add the line at the beginning of > the script. > > ---david In my case, having the modules elsewhere is an important goal. I am hoping that one day my module will become part of a larger project. The project is a Fortran 90 code for doing hydrodynamic simulations. The project has two subdirectories called "idl" and "python". These directories contain scripts in IDL and Python which are used for post-processing and analysis of the simulations. I am trying to bring my Julia module to a level comparable to IDL and Python, so I can add a "julia" directory as well. Cheers, Daniel. -- When an engineer says that something can't be done, it's a code phrase that means it's not fun to do.
