Feature request .init.lsp

Started by newdep, May 18, 2005, 02:57:44 AM

Previous topic - Next topic

newdep

Hello Lutz,



Is t possible to leave the .init.lsp allown during a "make install" ?

It overwrites personal adjusted .init.lsp / init.lsp files everytime a new install is don. Which is a little inconvenient..



Norman.
-- (define? (Cornflakes))

Lutz

#1
Yes, I think the install could check for an existing init.lsp to avoid overwriting.



The next development release due this weekend also has a binary installer for Mac OSX.



Lutz

Lutz

#2
... and thanks for all the segfault scernarios.



(1) the [cmd] thing can be fixed



(2) [text] shouldnt not be used multiline and interactively at all, this is expensive to fix and will stay as it it.



(3) All you macros are overwriting themselves while executing, of course this will cause the system to crash. So don't overwrite a function in the middle of it's execution.



Lutz

newdep

#3
I was stretching Newlisp a little ;-)
-- (define? (Cornflakes))

Lutz

#4
My previous response suppressing the init.lsp was not correct. This question came up earlier and since then init.lsp will at the end of the file look for a '.init.lsp' in your home directory. The installed 'init.lsp' itself resides in /usr/share/newlisp/init.lsp. So the solution to your problem is creating a .init.lsp (note the dot prefix) in your home directory.



Lutz

newdep

#5
Yes your right and im using that one.. Strange though its default?

Must be a mistake on my part !! sorry...



Norman.
-- (define? (Cornflakes))

statik

#6
QuoteThe next development release due this weekend also has a binary installer for Mac OSX.




/cheer :)
-statik