interrupt

The interrupt command is accepted and does nothing, because it belongs to an interactive session that James does not have.

Syntax

interrupt

interrupt takes no arguments. James discards the rest of the line.

What it does

In an interactive tool, interrupt stops a batch script and hands control to a person. James has no person to hand control to, so a script that holds the command runs straight through, as if the command were deleted.

When James applies it

When it is read, and then nothing happens. It is legal in any phase: Control, Part or Merge.

Rules James adds

• The command is a complete no-op, not an error.
• Inside a for or while body, it is ignored on every pass.

Diagnostics

• None: James raises no diagnostic for interrupt.

Example

The script tests/corpus/111-session-control-noop/input.tg, which make test runs:

block 1 2;1 2;1 2;0 1;0 1;0 1;
interrupt
resume
endpart

James builds the block as if lines 2 and 3 were absent. The prep dump keeps both words, and the IR holds one part.

See also

• resume: the partner command, also a no-op.
• caption: a picture command that is also accepted and ignored.