Differences between version 2 and predecessor to the previous major change of xscreensaver(1).
Other diffs: Previous Revision, Previous Author, or view the Annotated Edit History
| Newer page: | version 2 | Last edited on Tuesday, June 4, 2002 12:23:03 am | by perry | Revert |
| Older page: | version 1 | Last edited on Tuesday, June 4, 2002 12:23:03 am | by perry | Revert |
@@ -1144,10 +1144,10 @@
running as a normal, unprivileged user.
For more information on the X server's access control
-mechanisms, see the man pages for __
X__
(1),
-__
Xsecurity__
(1), xauth(1), and
+mechanisms, see the man pages for X(1),
+Xsecurity(1), xauth(1), and
xhost(1).
!!USING GDM(1)
@@ -1543,9 +1543,9 @@
__Attention, window manager authors!__
-You should only call __
XInstallColormap__
(3) in response
+You should only call XInstallColormap(3) in response
to user events. That is, it is appropriate to install a
colormap in response to __FocusIn__, __FocusOut__,
__EnterNotify__, and __LeaveNotify__ events; but it is
not appropriate to call it in response to
@@ -1605,9 +1605,9 @@
over a phone line) then the screensaver might not turn off
right away when the user becomes active again (the
ico(1) demo has this problem if being run in
full-speed mode). This can be alleviated by inserting
-strategic calls to __
XSync__
(3) in code intended for use
+strategic calls to XSync(3) in code intended for use
as a screensaver. This prevents too much graphics activity
from being buffered up.
@@ -1814,12 +1814,12 @@
http://www.jwz.org/xscreensaver/
!!SEE ALSO
-__
X__
(1), __xscreensaver-demo__(1),
+X(1), __xscreensaver-demo__(1),
__xscreensaver-command__(1),
__xscreensaver-gl-helper__(1), xdm(1),
-xset(1), __
Xsecurity__
(1), xauth(1),
+xset(1), Xsecurity(1), xauth(1),
xhost(1). ant(1), atlantis(1),
attraction(1), blitspin(1),
bouboule(1), braid(1), bsod(1),
__bubble3d__(1), bubbles(1), cage(1),
