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.
Feature request .init.lsp
Feature request .init.lsp
-- (define? (Cornflakes))
... 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
(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
init.lsp overwritten by new install
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
Lutz