Command Recorder
The Command Recorder logs user inputs and interactions with MathJet in the form of command statements. It displays the full history of statements run in the current and previous sessions, each preceded by the date and time of its session.
What gets recorded
Section titled “What gets recorded”Several sources feed the Command Recorder:
- Statements typed directly into the Command Editor.
- Statements run via Run Selected or Rerun from the Debug menu and toolbar.
- Statements re-run from inside the Command Recorder itself.
- Statements automatically generated by MathJet when you interact with the GUI — clicking a chart’s axis, dragging a graph between subplots, changing a property, etc.
By default both explicit and auto-generated statements are recorded. You can disable GUI auto-recording, or stop and start recording entirely, from the Options drop-down.
Bidirectional execution
Section titled “Bidirectional execution”In addition to simple re-runs, the Command Recorder supports bidirectional execution of logged statements:
- Reverse execution. Click the reverse-execution tool button to unrun the most recent active statement — undo every effect caused by that statement. After an unrun, the right-pointing arrow on the left margin moves up by one line to the preceding active statement. Repeat until no preceding active statement remains.
- Forward execution. Click the forward-execution tool button to re-run the next active statement below the arrow. Repeat until no more active statements remain below.
After a combination of unrun and rerun, when a new statement is appended in response to a fresh user action, any statements after the last-run statement become inactive and grey out in the list — the linear timeline branches.
Statements from previous sessions, loaded from the command history file, are always inactive: no live data backs them, so undo isn’t available.
Persistence
Section titled “Persistence”By default, MathJet auto-saves all statements to the command history file after each statement is added. Entries persist until you delete them, or until the file exceeds the configured limit. When the limit is hit, the oldest entries are removed automatically. The default cap is 25,000 statements.
See also
Section titled “See also”- Command Editor — primary entry point for new statements.
- Debug Windows — for stepping through code with finer granularity than reverse-execution.