Commit cdf00c10 authored by Ingo Schwarze's avatar Ingo Schwarze Committed by Matthieu Herrb

remove bogus \/ escapes

some X manuals use then escape sequence \/ when they want to render
a slash.  That's bad because \/ is not a slash but an italic
correction, never producing any output, having no effect at all in
terminal output, and only changing spacing in a minor way in typeset
Reviewed-by: Mark Kettenis's avatarMark Kettenis <>
Signed-off-by: Matthieu Herrb's avatarMatthieu Herrb <>
parent 703974ae
......@@ -224,7 +224,7 @@ The hostname part of the display name should be the empty string.
For example: \fI:0\fP, \fI:1\fP, and \fI:0.1\fP. The most efficient
local transport will be chosen.
.TP 8
The hostname part of the display name should be the server machine's
hostname or IP address. Full Internet names, abbreviated names, IPv4
......@@ -487,7 +487,7 @@ implementation dependent.
If the name is not found, the color is looked up in the
X server's database.
The text form of this database is commonly stored in the file
A numerical color specification
consists of a color space name and a set of values in the following syntax:
......@@ -1164,7 +1164,7 @@ A wide variety of error messages are generated from various programs.
The default error handler in \fIXlib\fP (also used by many toolkits) uses
standard resources to construct diagnostic messages when errors occur. The
defaults for these messages are usually stored in
\fI\__datadir__/X11/XErrorDB\fP. If this file is not present,
\fI__datadir__/X11/XErrorDB\fP. If this file is not present,
error messages will be rather terse and cryptic.
When the X Toolkit Intrinsics encounter errors converting resource strings to
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment