1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
//! **The box, and the two readings it takes against the engine's answer**
//! (bl-4855; DESIGN §4.30).
//!
//! Split from [`super`] at the design-time budget on the seam the two already
//! have: [`super`] is which file the pane is pointed at and what it composes,
//! and this is the one value that has to hold a conversation with the engine's
//! answer — seeded from it, settled against it, and answering the two
//! questions the controls are enabled and worded by.
//!
//! The whole of it exists because upstream's hash guard does not cross the
//! wire. A `config` act *"carries no hash guard, and needs none"* (REMOTE
//! §9.18) because a gesture states its whole text in one atomic instruction —
//! which is true of the gesture and false of the operator typing it. This is
//! that guard restated as a reading rather than as a refusal.
/// **A config file being edited**: the bytes in the box, and the bytes the box
/// last agreed with the engine about.