Leaderboard

Blast from the past! I remember buying this at the UNC Charlotte bookstore probably in 1995, it was $50 USD.

nice to hear your still living Grrr

Welcome to the "recursive" curse.

I have moved your thread to the Civil 3D & LDD Forum. Please post in the appropriate forum.

Glad I could help, and a belated welcome to the CadTutor Forums

The problem is with the *error* function. The *error* function has been defined within the NUMINC Lisp. This definition is still in place when you are running your other lisps. So when you error out of your other lisps it triggers the *error* function but this definition is using varables that were defined locally within the NUMINC. Within the defined *error* function CMDECHO is to be set to a variable within a list called ov. This ov varable was defined locally and is no longer present when you are running your other lisps. What seems odd is that Lee had defined the *error* function locally, so why would that definition still be present? I don't nessecarily recomend it but a quick fix is to set the *error* function to nil. (setq *error* nil) Or just wait untill you hear from Lee Mac himself.

That is a fireable offense in my company. I can't stand when people do that.

I very much doubt that it is my program causing your error, since, as Hippe correctly points out, my *error* function is localised within the NumInc function definition, and furthermore the statement to restore the System Variables in my program is error trapped in itself. It sounds like you are using a program in which the *error* function is not localised and that is attempting to restore the CMDECHO System Variable using a perhaps localised variable with no checking for a non-nil value before attempting to set the CMDECHO System Variable. Lee

Started a YouTube channel covering GIS and IFC for DWG mainly https://youtu.be/cyzB_2ytgKc