1
2
3\environment workflowsstyle
4
5\startcomponent workflowsrunning
6
7\startchapter[title={Running}]
8
9\startsection[title={Errors}]
10
11A \CONTEXT\ runs normally spits out quite some information to the console. In
12fact, even more information can go to the log file. It makes sense to have a look
13at the end of the log file occasionally because there you can find information
14about the (file) structure loaded, modules, issues with references andor
15fonts, etc.
16
17One problem with the terminal is that you can miss an issue easily, but there is
18a way out of this:
19
20\starttyping
21\enabledirectives[logs.errors]
22\stoptyping
23
24The command line argument \type {errors} has the same consequence. If you want
25to quit in an error, you can say for instance:
26
27\starttyping
28\enabledirectives[logs.errors=missing characters]
29\stoptyping
30
31If you run \CONTEXT\ with \type {trackers} or \type {directives} you get some
32information about the possible extra tracing. It might be illustrative to run a
33file with:
34
35\starttyping
36\enabletrackers[*]
37\stoptyping
38
39There are all kind of trackers and directives and you can get a list with:
40
41\starttyping
42context trackers directives
43\stoptyping
44
45An example is:
46
47\starttyping
48\enabletrackers[fonts.missing=replace]
49\stoptyping
50
51or just:
52
53\starttyping
54\enabletrackers[fonts.missing]
55\stoptyping
56
57
58\stopsection
59
60\startsection[title={Silent}]
61
62The \type {silent} options blocks most message. You can also pass a list (or
63pattern) of categories to silence. The \type {noconsole} option only disables
64logging to the console. The error reporting mentioned in the previous section
65will never be silenced.
66
67\stopsection
68
69\stopchapter
70
71\stopcomponent
72
73 |