ignoring init.lsp

nigelbrown · Post by **nigelbrown** » Thu Apr 01, 2004 2:52 am

Could there be a command line switch (eg -i) that suppressed reading the init.lsp file? That way I could
newlisp -i special-init.lsp my-prog.lsp
to use a specific initialization file without having to fiddle with any init.lsp that happened to be around.
Or is there another way to get that effect?

newdep · Post by **newdep** » Thu Apr 01, 2004 11:06 am

an addon,

A nice addon would be also an userspecified init.lsp file,
actualy located in the users $HOME directory instead of the
/usr/share/newlisp directory.

Norman

nigelbrown · Post by **nigelbrown** » Thu Apr 01, 2004 7:54 pm

clisp uses -i to specify an init file: from the man:
-i init-file
Specifies initialization files to be LOADed at startup.

Lutz, Is there a way to ignore init.lsp?

Lutz · Post by **Lutz** » Thu Apr 01, 2004 9:04 pm

Don't have one in /usr/share/newlisp or in the newlisp startup directory when on Win32.

I like Norman's idea to look for the init.lsp in $HOME on Unix or USERPROFILE on Win32.

Lutz

Lutz · Post by **Lutz** » Thu Apr 01, 2004 9:19 pm

one could achieve this by putting this in the system wide init.lsp

(load (append (getenv "HOME") "/.init.lsp"))

the dot at the beginning would hide the file on LINUX et al

or on Win32

(load (append (getenv "USERPROFILE") "/init.lsp"))

Lutz