-
-
Notifications
You must be signed in to change notification settings - Fork 261
/
github-0735.tlg
71 lines (71 loc) · 2.16 KB
/
github-0735.tlg
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
This is a generated file for the l3build validation system.
Don't change this file in any respect.
============================================================
TEST 1: pre-expansion one argument
============================================================
> \foo=document command:
#1:o
#2:m
->???.
<recently read> }
l. ... }
> \foo=document command:
#1:o
#2:m
->???.
<recently read> }
l. ... }
> \baz=document command:
#1:o
#2:m
->???.
<recently read> }
l. ... }
Ok?
============================================================
============================================================
TEST 2: pre-expansion two arguments
============================================================
> \baz=document command:
#1:o
#2:m
->???.
<recently read> }
l. ... }
> \baz=document command:
#1:o
#2:m
->???.
<recently read> }
l. ... }
============================================================
============================================================
TEST 3: Unknown variant
============================================================
! Use of \??? doesn't match its definition.
<argument> \???
! LaTeX Error: Unknown arg expansion "XX"
l. ... }
If you say, e.g., `\def\a1{...}', then you must always
put `1' after `\a', since control sequence names are
made up of letters only. The macro here has not been
followed by the required stuff, so I'm ignoring it.
! Argument of \declare@commandcopy@let has an extra }.
<inserted text>
\par
l. ... }
I've run across a `}' that doesn't seem to match anything.
For example, `\def\a#1{...}' and `\a}' would produce
this error. If you simply proceed now, the `\par' that
I've just inserted will cause me to report a runaway
argument that might be the root of the problem. But if
your `}' was spurious, just type `2' and it will go away.
Runaway argument?
! Paragraph ended before \declare@commandcopy@let was complete.
<to be read again>
\par
l. ... }
I suspect you've forgotten a `}', causing me to apply this
control sequence to too much text. How can we recover?
My plan is to forget the whole thing and hope for the best.
============================================================