summaryrefslogtreecommitdiffstats
path: root/system/vice/fix_texi.diff
blob: c1a264538a2246b17da0582d5fbad86b72bc6141 (plain) (blame)
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
73
74
75
76
77
78
79
diff -Naur vice-3.8/doc/vice.texi vice-3.8.patched/doc/vice.texi
--- vice-3.8/doc/vice.texi	2023-12-24 12:42:36.000000000 -0500
+++ vice-3.8.patched/doc/vice.texi	2024-02-13 20:17:44.907985392 -0500
@@ -1486,7 +1486,7 @@
 * Romset files::                Files defining the machine's ROM set.
 @end menu
 
-@node ROM files, Keymap files, Gtk3 Hotkeys files, System files, System files
+@node ROM files, Keymap files, Hotkeys files, System files
 @section ROM files
 
 Every emulator requires its own ROM set.  For the VIC20 and the C64, the
@@ -2415,17 +2415,6 @@
 Directives are special commands for the parser. They start with
 @strong{@code{!}} and are case-insensitive.
 
-@menu
-* !CLEAR::
-* !DEBUG::
-* !ELSE::
-* !ENDIF::
-* !IF::
-* !INCLUDE::
-* !UNDEF::
-* !WARNING::
-@end menu
-
 @strong{!CLEAR}
 @quotation
 
@@ -4954,7 +4943,7 @@
 
 xplus4 control ports and devices:
 
-@multitable @columnfractions .05 .33 .05 .05 .05 .05 .05 .05 .05 .05 .05
+@multitable @columnfractions .05 .33 .05 .05 .05 .05 .05 .05 .05 .05 .05 .05 .05
 @headitem nr
 @tab device
 @tab N1
@@ -8005,8 +7994,8 @@
 
 The windows driver understands various options passed in the so called "mode string"
 after a colon after the ports name: @code{COMx[:]} @code{[baud=b]} @code{[parity=p]}
-@code{[data=d]} @code{[stop=s]} @code{[to={on|off}]} @code{[xon={on|off}]} @code{[odsr={on|off}]}
-@code{[octs={on|off}]} @code{[dtr={on|off|hs}]} @code{[rts={on|off|hs|tg}]} @code{[idsr={on|off}]}
+@code{[data=d]} @code{[stop=s]} @code{[to=on|off]} @code{[xon=on|off]} @code{[odsr=on|off]}
+@code{[octs=on|off]} @code{[dtr=on|off|hs]} @code{[rts=on|off|hs|tg]} @code{[idsr=on|off]}
 @end table
 
 @table @code
@@ -8142,8 +8131,8 @@
 
 The windows driver understands various options passed in the so called "mode string"
 after a colon after the ports name: @code{COMx[:]} @code{[baud=b]} @code{[parity=p]}
-@code{[data=d]} @code{[stop=s]} @code{[to={on|off}]} @code{[xon={on|off}]} @code{[odsr={on|off}]}
-@code{[octs={on|off}]} @code{[dtr={on|off|hs}]} @code{[rts={on|off|hs|tg}]} @code{[idsr={on|off}]}
+@code{[data=d]} @code{[stop=s]} @code{[to=on|off]} @code{[xon=on|off]} @code{[odsr=on|off]}
+@code{[octs=on|off]} @code{[dtr=on|off|hs]} @code{[rts=on|off|hs|tg]} @code{[idsr=on|off]}
 @end table
 
 @table @code
@@ -9332,7 +9321,7 @@
 
 @c ----------------------------------------------------------------
 
-@c @node Misc settings,  , Monitor settings, Settings and resources
+@node Misc settings,  , Monitor settings, Settings and resources
 @c @section Miscellaneous settings
 
 @node Machine-specific features, Platform-specific features, Settings and resources, Top
@@ -20784,7 +20773,7 @@
 @end table
 
 
-@c @node Miscellaneous commands,  , Profiling commands, Monitor
+@node Miscellaneous commands,  , Profiling commands, Monitor
 @section Resources commands
 
 @table @code