|
|
1
|
+Author: Bjarni Ingi Gislason <bjarniig@simnet.is>
|
|
|
2
|
+Last-Update: 2023-06-12
|
|
|
3
|
+Bug-Debian: https://bugs.debian.org/1037354
|
|
|
4
|
+Description: Some formatting fixes for the manual
|
|
|
5
|
+
|
|
|
6
|
+--- a/man/X.man
|
|
|
7
|
++++ b/man/X.man
|
|
|
8
|
+@@ -36,7 +36,6 @@
|
|
|
9
|
+ .SH NAME
|
|
|
10
|
+ X \- a portable, network-transparent window system
|
|
|
11
|
+ .SH OVERVIEW
|
|
|
12
|
+-.PP
|
|
|
13
|
+ The X Window System is a network transparent window system which runs
|
|
|
14
|
+ on a wide range of computing and graphics machines. It should be
|
|
|
15
|
+ relatively straightforward to build the X.Org Foundation software
|
|
|
16
|
+@@ -72,9 +71,9 @@ X supports overlapping hierarchical subw
|
|
|
17
|
+ graphics operations, on both monochrome and color
|
|
|
18
|
+ displays.
|
|
|
19
|
+ For a full explanation of the functions that are available, see
|
|
|
20
|
+-the \fIXlib - C Language X Interface\fP manual,
|
|
|
21
|
++the \fIXlib \(en C Language X Interface\fP manual,
|
|
|
22
|
+ the \fIX Window System Protocol\fP specification,
|
|
|
23
|
+-the \fIX Toolkit Intrinsics - C Language Interface\fP manual,
|
|
|
24
|
++the \fIX Toolkit Intrinsics \(en C Language Interface\fP manual,
|
|
|
25
|
+ and various toolkit documents.
|
|
|
26
|
+ .\" Use .UR macro from groff's man(7) if available, otherwise just
|
|
|
27
|
+ .\" display URL as plain text for other processors.
|
|
|
28
|
+@@ -124,7 +123,6 @@ as packages in many operating system dis
|
|
|
29
|
+ available on the Internet.
|
|
|
30
|
+ See your site administrator or distro package manager for details.
|
|
|
31
|
+ .SH "STARTING UP"
|
|
|
32
|
+-.PP
|
|
|
33
|
+ There are two main ways of getting the X server and an initial set of
|
|
|
34
|
+ client applications started. The particular method used depends on what
|
|
|
35
|
+ operating system you are running and whether or not you use other window
|
|
|
36
|
+@@ -158,7 +156,6 @@ finish. Since either or both of the use
|
|
|
37
|
+ script, this gives substantial flexibility at the expense of a
|
|
|
38
|
+ nice interface. For this reason, \fIxinit\fP is not intended for end users.
|
|
|
39
|
+ .SH "DISPLAY NAMES"
|
|
|
40
|
+-.PP
|
|
|
41
|
+ From the user's perspective, every X server has a \fIdisplay name\fP of the
|
|
|
42
|
+ form:
|
|
|
43
|
+ .sp
|
|
|
44
|
+@@ -430,7 +427,6 @@ hand corner:
|
|
|
45
|
+ xload \-geometry 48x48\-96+0 &
|
|
|
46
|
+ xbiff \-geometry 48x48\-48+0 &
|
|
|
47
|
+ .fi
|
|
|
48
|
+-.PP
|
|
|
49
|
+ .SH "WINDOW MANAGERS"
|
|
|
50
|
+ The layout of windows on the screen is controlled by special programs called
|
|
|
51
|
+ \fIwindow managers\fP. Although many window managers will honor geometry
|
|
|
52
|
+@@ -481,8 +477,8 @@ font database, reset the font path with
|
|
|
53
|
+ to add a font to a private directory, the following commands could be used:
|
|
|
54
|
+ .sp
|
|
|
55
|
+ .nf
|
|
|
56
|
+- % cp newfont.pcf ~/myfonts
|
|
|
57
|
+- % mkfontdir ~/myfonts
|
|
|
58
|
++ % cp newfont.pcf \(ti/myfonts
|
|
|
59
|
++ % mkfontdir \(ti/myfonts
|
|
|
60
|
+ % xset fp rehash
|
|
|
61
|
+ .fi
|
|
|
62
|
+ .PP
|
|
|
63
|
+@@ -650,8 +646,8 @@ the following syntax:
|
|
|
64
|
+ center;
|
|
|
65
|
+ l l.
|
|
|
66
|
+ CIEXYZ:\fI<X>/<Y>/<Z>\fP (\fInone\fP, 1, \fInone\fP)
|
|
|
67
|
+-CIEuvY:\fI<u>/<v>/<Y>\fP (~.6, ~.6, 1)
|
|
|
68
|
+-CIExyY:\fI<x>/<y>/<Y>\fP (~.75, ~.85, 1)
|
|
|
69
|
++CIEuvY:\fI<u>/<v>/<Y>\fP (\(ti.6, \(ti.6, 1)
|
|
|
70
|
++CIExyY:\fI<x>/<y>/<Y>\fP (\(ti.75, \(ti.85, 1)
|
|
|
71
|
+ CIELab:\fI<L>/<a>/<b>\fP (100, \fInone\fP, \fInone\fP)
|
|
|
72
|
+ CIELuv:\fI<L>/<u>/<v>\fP (100, \fInone\fP, \fInone\fP)
|
|
|
73
|
+ TekHVC:\fI<H>/<V>/<C>\fP (360, 100, 100)
|
|
|
74
|
+@@ -669,7 +665,6 @@ followed by an optional '+' or '\-' foll
|
|
|
75
|
+ For more information on device independent color,
|
|
|
76
|
+ see the \fIXlib\fP reference manual.
|
|
|
77
|
+ .SH KEYBOARDS
|
|
|
78
|
+-.PP
|
|
|
79
|
+ The X keyboard model is broken into two layers: server-specific codes
|
|
|
80
|
+ (called \fIkeycodes\fP) which represent the physical keys, and
|
|
|
81
|
+ server-independent symbols (called \fIkeysyms\fP) which
|
|
|
82
|
+@@ -700,7 +695,7 @@ The first four elements of the list are
|
|
|
83
|
+ Group 1 contains the first and second keysyms;
|
|
|
84
|
+ Group 2 contains the third and fourth keysyms.
|
|
|
85
|
+ Within each group,
|
|
|
86
|
+-if the first element is alphabetic and the
|
|
|
87
|
++if the first element is alphabetic and
|
|
|
88
|
+ the second element is the special keysym \fINoSymbol\fP,
|
|
|
89
|
+ then the group is treated as equivalent to a group in which
|
|
|
90
|
+ the first element is the lowercase letter and the second element
|
|
|
91
|
+@@ -709,7 +704,7 @@ is the uppercase letter.
|
|
|
92
|
+ Switching between groups is controlled by the keysym named MODE SWITCH,
|
|
|
93
|
+ by attaching that keysym to some key and attaching
|
|
|
94
|
+ that key to any one of the modifiers Mod1 through Mod5.
|
|
|
95
|
+-This modifier is called the ``group modifier.''
|
|
|
96
|
++This modifier is called the ``group modifier''.
|
|
|
97
|
+ Group 1 is used when the group modifier is off,
|
|
|
98
|
+ and Group 2 is used when the group modifier is on.
|
|
|
99
|
+ .PP
|
|
|
100
|
+@@ -769,7 +764,7 @@ possible, often by swapping the foregrou
|
|
|
101
|
+ programs honor this or implement it correctly. It is usually only used on
|
|
|
102
|
+ monochrome displays.
|
|
|
103
|
+ .TP 8
|
|
|
104
|
+-.B \+rv
|
|
|
105
|
++.B +rv
|
|
|
106
|
+ .br
|
|
|
107
|
+ This option indicates that the program should not simulate reverse video.
|
|
|
108
|
+ This is used to
|
|
|
109
|
+@@ -814,7 +809,7 @@ Program components are named in a hierar
|
|
|
110
|
+ with each node in the hierarchy identified by a class and an instance name.
|
|
|
111
|
+ At the top level is the class and instance name of the application itself.
|
|
|
112
|
+ By convention, the class name of the application is the same as the program
|
|
|
113
|
+-name, but with the first letter capitalized (e.g. \fIBitmap\fP or \fIEmacs\fP)
|
|
|
114
|
++name, but with the first letter capitalized (e.g. \fIBitmap\fP or \fIEmacs\fP)
|
|
|
115
|
+ although some programs that begin with the letter ``x'' also capitalize the
|
|
|
116
|
+ second letter for historical reasons.
|
|
|
117
|
+ .PP
|
|
|
118
|
+@@ -859,24 +854,24 @@ same ResourceName, the last line in the
|
|
|
119
|
+ Any whitespace character before or after the name or colon in a ResourceSpec
|
|
|
120
|
+ are ignored.
|
|
|
121
|
+ To allow a Value to begin with whitespace,
|
|
|
122
|
+-the two-character sequence ``\\\^\fIspace\fP'' (backslash followed by space)
|
|
|
123
|
++the two-character sequence ``\e\^\fIspace\fP'' (backslash followed by space)
|
|
|
124
|
+ is recognized and replaced by a space character,
|
|
|
125
|
+-and the two-character sequence ``\\\^\fItab\fP''
|
|
|
126
|
++and the two-character sequence ``\e\^\fItab\fP''
|
|
|
127
|
+ (backslash followed by horizontal tab)
|
|
|
128
|
+ is recognized and replaced by a horizontal tab character.
|
|
|
129
|
+ To allow a Value to contain embedded newline characters,
|
|
|
130
|
+-the two-character sequence ``\\\^n'' is recognized and replaced by a
|
|
|
131
|
++the two-character sequence ``\e\^n'' is recognized and replaced by a
|
|
|
132
|
+ newline character.
|
|
|
133
|
+ To allow a Value to be broken across multiple lines in a text file,
|
|
|
134
|
+-the two-character sequence ``\\\^\fInewline\fP''
|
|
|
135
|
++the two-character sequence ``\e\^\fInewline\fP''
|
|
|
136
|
+ (backslash followed by newline) is
|
|
|
137
|
+ recognized and removed from the value.
|
|
|
138
|
+ To allow a Value to contain arbitrary character codes,
|
|
|
139
|
+-the four-character sequence ``\\\^\fInnn\fP'',
|
|
|
140
|
++the four-character sequence ``\e\^\fInnn\fP'',
|
|
|
141
|
+ where each \fIn\fP is a digit character in the range of ``0''\-``7'',
|
|
|
142
|
+ is recognized and replaced with a single byte that contains
|
|
|
143
|
+ the octal value specified by the sequence.
|
|
|
144
|
+-Finally, the two-character sequence ``\\\\'' is recognized
|
|
|
145
|
++Finally, the two-character sequence ``\e\e'' is recognized
|
|
|
146
|
+ and replaced with a single backslash.
|
|
|
147
|
+ .PP
|
|
|
148
|
+ When an application looks for the value of a resource, it specifies
|
|
|
149
|
+@@ -942,10 +937,10 @@ or the environment variable XAPPLRESDIR
|
|
|
150
|
+ directory and should end with a '/' on POSIX systems), plus directories in a
|
|
|
151
|
+ standard place (usually under __datadir__/X11/,
|
|
|
152
|
+ but this can be overridden with the XFILESEARCHPATH environment variable)
|
|
|
153
|
+-are searched for for application-specific resources.
|
|
|
154
|
++are searched for application-specific resources.
|
|
|
155
|
+ For example, application default resources are usually kept in
|
|
|
156
|
+ __datadir__/X11/app-defaults/.
|
|
|
157
|
+-See the \fIX Toolkit Intrinsics - C Language Interface\fP manual for
|
|
|
158
|
++See the \fIX Toolkit Intrinsics \(en C Language Interface\fP manual for
|
|
|
159
|
+ details.
|
|
|
160
|
+ .TP 8
|
|
|
161
|
+ .B XENVIRONMENT
|
|
|
162
|
+@@ -972,15 +967,12 @@ begins with a lowercase letter and class
|
|
|
163
|
+ Multiple word resources are concatenated with the first letter of the
|
|
|
164
|
+ succeeding words capitalized. Applications written with the X Toolkit
|
|
|
165
|
+ Intrinsics will have at least the following resources:
|
|
|
166
|
+-.PP
|
|
|
167
|
+ .TP 8
|
|
|
168
|
+ .B background (\fPclass\fB Background)
|
|
|
169
|
+ This resource specifies the color to use for the window background.
|
|
|
170
|
+-.PP
|
|
|
171
|
+ .TP 8
|
|
|
172
|
+ .B borderWidth (\fPclass\fB BorderWidth)
|
|
|
173
|
+ This resource specifies the width in pixels of the window border.
|
|
|
174
|
+-.PP
|
|
|
175
|
+ .TP 8
|
|
|
176
|
+ .B borderColor (\fPclass\fB BorderColor)
|
|
|
177
|
+ This resource specifies the color to use for the window border.
|
|
|
178
|
+@@ -1165,7 +1157,7 @@ The default value is\fI __datadir__/X11/
|
|
|
179
|
+ .TP
|
|
|
180
|
+ .B XCMSDB
|
|
|
181
|
+ This must point to a color name database file. The default value is
|
|
|
182
|
+-\fI __libdir__/X11/Xcms.txt\fP.
|
|
|
183
|
++\fI__libdir__/X11/Xcms.txt\fP.
|
|
|
184
|
+ .TP
|
|
|
185
|
+ .B RESOURCE_NAME
|
|
|
186
|
+ This serves as main identifier for resources belonging to the program
|
|
|
187
|
+@@ -1271,7 +1263,6 @@ the appropriate instance name can be pla
|
|
|
188
|
+ xterm*StringConversionWarnings: on
|
|
|
189
|
+ .fi
|
|
|
190
|
+ .SH "SEE ALSO"
|
|
|
191
|
+-.PP
|
|
|
192
|
+ .\" introductions
|
|
|
193
|
+ .BR XOrgFoundation (__miscmansuffix__),
|
|
|
194
|
+ .BR XStandards (__miscmansuffix__),
|
|
|
195
|
+@@ -1360,10 +1351,8 @@ website at
|
|
|
196
|
+ .UR "http://www.x.org/releases/current/doc/"
|
|
|
197
|
+ .UE .
|
|
|
198
|
+ .SH TRADEMARKS
|
|
|
199
|
+-.PP
|
|
|
200
|
+ X Window System is a trademark of The Open Group.
|
|
|
201
|
+ .SH AUTHORS
|
|
|
202
|
+-.PP
|
|
|
203
|
+ A cast of thousands, literally. Releases 6.7 and later are
|
|
|
204
|
+ brought to you by the X.Org Foundation. The names of all people who
|
|
|
205
|
+ made it a reality will be found in the individual documents and |