newlispfanclub.alh.net

I installed the newlisp 8.2 on windows. When I start the IDE
I get this error message which doesn't seem to effective anything
else negatively.

Error sourcing /freewrap/newlisp-tk.tcl: couldn't change
working directory to "c:/newlisp/": no such file or directory

I installed newlisp in a directory different from "c:/newlisp".

Can I safely ignore this error message?

Short answer: you can ignore the message.

But here an explanation what it means:

newLISP-tk is trying to goto an initial directory, which will be used when you do a "File/Load" from the main menu, or which would be the current directory for any other operations you do with files. newLISP-tk gets this directory from a specification in 'newlisp-tk.config'. This file is in your intsallation directory and contains the following spec:

set Ide(initialDir) "c:/newlisp/"

You can edit this with notepad.exe or any other plain text editor to a directory of your liking, i.e. the installation directory, because that is also the place where all the demo programs are.

Lutz

I was able to correct this problem by editting the newlisp-tk.config file and replacing the incorrect for Windows "/" directory delimiters with "\"; however, newLisp seems to interprute "\" as an escape code as in C, so I actually had to use "\\", e.g. "C:\\Program Files\\newlisp". This works like a charm. Seems the "Save Settings" option within tk doesn't handle the path delimiter properly for Windows.

P. Todd

Actually forward slashes on Windows are allowed as long as they don't come after a drive letter. The newlisp-tk.conf file is Tcl and is sourced by newlisp-tk.tcl on startup.

In the current development release 8.5.5 when doing Options/Save-settings specs are written put with {,} braces and backslashes will appear single. I have been fighting with that stuff, to get it right on all platforms Linux/Win32/MacOSX, for some time/versions now. I hope that in the lates development release it is fine on all of them. Please let me know if there is anything left to do.

Lutz

Thank you, Lutz! Don't we all just love Windows! BTW--Everything works fine as far as I can tell under OS X on my Mac.