Function Entry: GETPOINT

getpoint

Function

(getpoint [pt] [msg])

• pt: optional base point
• msg: optional prompt string

Autodesk documents pt as a 2D or 3D base point in the current UCS. Autodesk also documents that a single integer or real may be supplied as pt, invoking direct-distance entry from LASTPOINT.

Prompts the user to specify a point.

Returns a 3D point list or nil.

• prompts the user
• consumes interactive input

Host-interaction-specific; point representation remains ordinary list data.

• AutoCAD 2026: documented (per Autodesk reference page).
• BricsCAD V26: presumed compatible (no contradicting page found).
• Status: AutoCAD documented; BricsCAD presumed-both pending Phase 4 verification.

• [getpoint (AutoLISP)](https://help.autodesk.com/cloudhelp/2026/PLK/AutoCAD-LT-AutoLISP-Reference/files/GUID-445F32F0-8A9D-4E1D-976F-DE87CC5267D0.htm)

• Autodesk documents that if pt is present as a point, the host draws a rubber-band line from that point to the current crosshair position.
• Autodesk documents that the user cannot respond with another AutoLISP expression.

clautolisp implementation deviation — not part of the normative specification above. AutoCAD and BricsCAD collect this point through the graphical drawing editor: a command-line prompt combined with pointer/keyboard interaction in the drawing window (implicitly a GUI). clautolisp has no drawing editor — it writes the prompt to the standard output and reads the answer as one line of text from the standard input (a TUI interaction). Interactively this is the REPL's terminal; for scripted, deterministic runs it is the file attached with --mock-input. A live CAD host, when connected, restores the native GUI behavior. On the TUI the point is typed as whitespace-separated coordinates — X Y or X Y Z; a 2D entry gets Z = 0.0. There is no crosshair, rubber-band line, or direct-distance entry; invalid input returns nil rather than re-prompting.