Page Comparison

...

1. Run ARES Commander 2024 or later.

2. In the Options dialog box, select System Options > Lisp Debugger and select Enable Debugging.
   

   

3. Close ARES Commander to save the settings and launch it again.

4. From the Visual Studio Code Menu select Run > Add Configuration.

5. Add the Launch and Attach configuration options:

   • FLISP Debug: Attach

   • FLISP Debug: Launch

     

     Launch and Attach configuration options are added.

     

6. FLISP Debug: Attach
   From the Run and Debug side palette of Visual Studio Code, select FLISP Debug:Attach and click Run (or press F5).
   The list of all running ARES Commander applications and OEMs appears. On attach, the status bar color changes from blue to orange. LISP files automatically load.
   You can run the LISP command in ARES Commander and debug the LISP functions.
   

   Tip: Pressing Ctrl+Shift+D displays the Run and Debug palette.
   

   

7. FLISP Debug: launch
   First, you need to specify the path to ARES Commander executable file (ARESC.exe or the file corresponding to any other Graebert OEM application) in the Extension setting of Graebert LISP Extension.
   From the Run and Debug side palette of Visual Studio Code, select FLISP Debug: Launch and click Run (or press F5).
   When launching ARES Commander, the status bar color changes from blue to orange. LISP files automatically load. You can run the LISP command in ARES Commander and debug the LISP functions.
   

   

LISP Protection

1. Click the right mouse button of the top
FeaturesFLISP Debug: launch
First, you need to specify the path to ARES Commander executable file (ARESC.exe or the file

LISP Editor:

• Syntax Highlighting

• Snippet Completion for LISP & DCL

• Smart Brackets

• Comment Toggling

• AutoComplete for LISP & DCL

• Go-To-Definition and Peek Definition

• Localization

• LISP Encryption

• Add & Update Header

• Insert Region

• Online Help

• Load Current LISP File

• Create Workspace

...