Aren/NetBSD
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

Fix spelling typos.

Browse Source
This commit is contained in:
castor 1999-11-03 22:01:40 +00:00
parent 94b8f863fa
commit a95e913325
1 changed files with 5 additions and 5 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

10
share/man/man4/wsmux.4
View File

@ -1,4 +1,4 @@
.\" $NetBSD: wsmux.4,v 1.1 1999/07/29 18:22:04 augustss Exp $
.\" $NetBSD: wsmux.4,v 1.2 1999/11/03 22:01:40 castor Exp $
.\"
.\" Copyright (c) 1999 The NetBSD Foundation, Inc.
.\" All rights reserved.
@ -56,23 +56,23 @@ for mouse events and one for keyboard events. All
devices should direct their events to the mouse mux (normally 0)
and all keyboard devices, except the console, should direct their
events to the keyboard mux (normally 1). A device will
send its events to the mux indicated my the
send its events to the mux indicated by the
.Va mux
locator. If none is given the device will not use a multiplexor.
The keyboard multiplexor should be connected to the display, using
the
.Xr wsconscfg 8
command. It will then recieve all keystrokes from all keyboards
command. It will then receive all keystrokes from all keyboards
and, furthermore, keyboards can be dynamically attached and detached without
further user interaction.
In a similar way, the window system will open the mouse multiplexor
and recieve all mouse events; mice can also be dynamically attached
and receive all mouse events; mice can also be dynamically attached
and detached.
.Pp
It is also possible to inject events into a multiplexor from a
user program. This is used by the
.Xr moused 8
deamon to take data from a mouse connected to a serial port and
daemon to take data from a mouse connected to a serial port and
make it appear on the standard mouse mux.
.Pp
.Sh FILES