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
output.

Signed-off-by: Matthieu Herrb <matthieu@herrb.eu>
Reviewed-by: Mark Kettenis <kettenis@openbsd.org>
Signed-off-by: Keith Packard <keithp@keithp.com>
This commit is contained in:
Ingo Schwarze 2015-08-30 15:26:40 +02:00 committed by Keith Packard
parent c74c074d8e
commit 634e357be2
2 changed files with 2 additions and 2 deletions

View File

@ -46,7 +46,7 @@ On most platforms, the "Local" connection type is a UNIX-domain socket.
On some System V platforms, the "local" connection types also include On some System V platforms, the "local" connection types also include
STREAMS pipes, named pipes, and some other mechanisms. STREAMS pipes, named pipes, and some other mechanisms.
.TP 4 .TP 4
.I TCP\/IP .I TCP/IP
.B Xorg .B Xorg
listens on port listens on port
.RI 6000+ n , .RI 6000+ n ,

View File

@ -433,7 +433,7 @@ elapse between autorepeat-generated keystrokes).
loads keyboard description in \fIfilename\fP on server startup. loads keyboard description in \fIfilename\fP on server startup.
.SH "NETWORK CONNECTIONS" .SH "NETWORK CONNECTIONS"
The X server supports client connections via a platform-dependent subset of The X server supports client connections via a platform-dependent subset of
the following transport types: TCP\/IP, Unix Domain sockets, DECnet, the following transport types: TCP/IP, Unix Domain sockets, DECnet,
and several varieties of SVR4 local connections. See the DISPLAY and several varieties of SVR4 local connections. See the DISPLAY
NAMES section of the \fIX\fP(__miscmansuffix__) manual page to learn how to NAMES section of the \fIX\fP(__miscmansuffix__) manual page to learn how to
specify which transport type clients should try to use. specify which transport type clients should try to use.