Re: [Maxima-discuss] Location of init files?

[Raymond T. <toy...@gm...>]

On Tue, Jul 19, 2022 at 9:37 AM Robert Dodier <rob...@gm...>
wrote:

> On Tue, Jul 19, 2022 at 8:39 AM Raymond Toy <toy...@gm...> wrote:
>
> > Oh, that complicates things.  --init just sets the file name; it's still
> searched in the same places, so it would only be found in the user's home
> dir.  What I did for update-examples is use the -p flag to load
> maxima-init.lisp from the current dir.  We'd need an equivalent flag (-P?)
> to load up a mac file.  Or some other solution.  Or leave everything as is.
>
> I'm in favor of changing things so that init files are sought only in
> the user's home directory, since that's the behavior of other
> programs.
>
> I am inclined to expand --preload-lisp to load Maxima files as well as
> Lisp files. I guess then we'll rename it to --preload (and continue to
> recognize --preload-lisp for backwards compatibility). Incidentally
> I'd make it so that multiple --preload options are recognized.
> --preload can just punt to $LOAD to figure out how to load the file
> (i.e., not necessary for --preload to distinguish Lisp from Maxima, or
> figure out the load path).
>

Yes, I've done exactly that.  It works as expected.

maxima-local --no-init -p maxima-init.lisp -p maxima-init.mac

searches for those files and successfully loads both using $LOAD.

I think all options can be specified more than once and they'll do run the
action each time.  I suppose for some actions, only the last one will have
effect, but -p just loads a file each time.

>
> FWIW
>
> Robert
>


-- 
Ray