Lisp
Is there any error message?
Without a careful review, it's hard to say whether, for example, some invalid definition might be stopping it part-way through. But I would also think you could shorten it, because a number of those look the same as default command aliases already in the ACAD.PGP file. You could also use that for some of them that are not already given your preferred shortcuts [all those that just call up a command, without built-in feeding-in of some option(s)], You can change the assignments of aliases in the .PGP, but make sure you don't duplicate any that are already there for other commands, unless you change those to something else or remove them.
Kent Cooper, AIA 
You have an extra right paren in
(defun c:lo () (prompt "Layer Off\n") (command "_layoff") (prin1))
(prin1))
Henrique
@Anonymous wrote:
.... When I deleted ;***
(defun c:zl () (prompt "Zoom Limits\n")
(command ".zoom" "w" (getvar "limmin") (getvar "limmax"))
(prin1))
Then the lisp routine works perfectly
....
I wouldn't think you'd need to get rid of that one to make the rest of them work. I have a nearly identical command defined in my acaddoc.lsp [except without the (prompt) -- it just does it], which I use all the time. Another slight difference is that mine doesn't have the "w" option specified -- Zoom assumes that if no other option is specified, so you can simply give it two points.
Kent Cooper, AIA
@Anonymous wrote:
Well, I didn't see anything in my lisp file to cause any problems. It wasn't until I deleted that particular command that the lisp routine started working.
That makes me wonder whether the file may have been edited, in part or at some time, using a Word Processor or Rich-Text editor rather than a plain-text editor. I believe certain characters can "survive" in something like MS Word when saved as an ASCII file with a certain amount of "intelligence" [such as double-quotes, which differentiate themselves in Word between opening and closing ones, and apostrophes] that AutoLISP won't be happy with. Some things like that show up as little rectangles when such a file is opened in a plain-text editor, but I think some may be able to look like their plain-text equivalents without really being that way. So I'm curious -- if you edit that command in a truly plain-text editor like Notepad, and delete all the double-quotes and re-type them to makre sure they're really plain-text ones, and re-insert it into the larger file, does it work?
Kent Cooper, AIA
