Main Help → GENerel Reference → Log Command

Log Command

The Log command is used to output information to the Console application. It is useful for debugging of templates (but Dump command to use the scripting window is usually better).

Log #1,<#2>,<#3>, ...

where

• #1 can specify the type of data to print to the Console. The options are
  • parsed - log all commands as parsed by the command interpreter.
  • evaluated - log all commands after all expressions have been evaluated.
  • both - log commands after parsing and after evaluating.
  • none - stop logging commands
• If #1 is not one of the above options, the expressions in all arguments (#1, #2, #3, ...) will be evaluated and the results will be logged to the Console.

When using Log in internal scripts, the #1 options above are not supported; instead all arguments are evaluated and logged to the Console.

Notes

1. The debugging process is to use Log commands in the templates, load the browser style into GEDitCOM II, start the Console application (in the Utilities folder in the Applications folder), and open records that use the templates. The output of logging commands will appear in the Console window.
2. In recent MacOS versions, logging from other tasks happen so often, it can be hard to find the ones from GEDitCOM II. You can filter the logging by typing "GEDitCOM" into the search field of the Console application window. Another option is to debug using the Dump command to send messages to the scripting panel instead of the Console application.