AutoCAD built-in command list with AutoLISP

[lido]

Hello all!
I have an AutoLISP code that goes to the client along with drawings. The code contains a sequence for attribute editing with either EATTEDIT built-in command or an AutoLISP snippet.

On this stage, I don't know if the EATTEDIT built-in command is implemented under the client CAD platform, so that I must check the availability of the command.

Is there any possibility to obtain via AutoLISP a complete list of AutoCAD internal (built-in) commands?

Thank you in advance.

[rlx]

http://www.cadtutor.net/forum/showth...t=atoms-family

[lido]

Sorry, but atoms-family function don't return the built-in command names. Please try it.

[rkmcswain]

Is there any possibility to obtain via AutoLISP a complete list of AutoCAD internal (built-in) commands?

ARX command, "C" option.

Here is an entire thread on this topic, including some good lisp routines.

[rlx]

Sorry, but atoms-family function don't return the built-in command names. Please try it.

oh darn... hope other reply does better... maybe vl-cmdf can offer a quick test because it first tests if a command can be successful before it executes it else just check autocad version

[lido]

I know the trick with ARX, option "C".
EATTEDIT still missing from the list (AutoCAD 2015). Please give it a try.

[ronjonp]

Not a full list .. but here's a quick check:

...

[Roy_043]

How about?:

(getcname "_eattedit")

[lido]

(vl-cmdf "abcde") return: Unknown command "abcde". Press F1 for help. T

(command "abcde") return: Unknown command "abcde". Press F1 for help. nil

Finally, always vl-cmdf function return T and command function return nil.
How could I manage an error like "Unknow command" without an error code??

Testing the AutoCAD version may be a path... But if the client uses an other CAD platform? First test the platform (PROGRAM system variable). Then test the version (VERNUM system variable) and decide if EATTEDIT is implemented or not by reading specific CAD manuals. No, please...

[ronjonp]

Use Roy's suggestion .. or better yet get rid of command calls in your code.