moon-buggy(6) [debian man page]

moon-buggy(6)							   Games Manual 						     moon-buggy(6)

NAME

       moon-buggy - drive some car across the moon

SYNOPSIS

       moon-buggy [-hnsV] [--help] [--no-title] [--show-scores] [--version]

DESCRIPTION

       Moon-buggy  is  a simple character graphics game, where you drive some kind of car across the moon's surface.  Unfortunately there are dan-
       gerous craters there.  Fortunately your car can jump over them!

OPTIONS

       The program understands the following command line options.

       -h, --help
	      shows a short usage message.

       -m, --mesg
	      disable write access to your terminal by other users, so your boss can't disturb your game play with the help of	"write"  or  "fin-
	      ger".

       -n, --no-title
	      skips the title screen.

       -s, --show-scores
	      shows the current highscore list and exits.

       -V, --version
	      prints the program's version to standard output and exits.

KEYS

       The  moon-buggy	is  controlled	by  a couple of keys, which are described near the bottom of the screen.  Most important are the following
       keys.

       SPC, j makes your car jump.  The length of a jump is fixed and you can only start a new jump, while the wheels have contact to the ground.

       a, l   fires the mining laser.  The laser is used to remove stones, which may block your way.

       q      quits the game prematurely.  But you still keep your score and may enter the highscore list.

FILES

       The following files on your system are related to moon-buggy.

       /usr/games/moon-buggy
	      the moon-buggy executable.

       /var/games/moon-buggy/mbscore
	      the global score file

       $HOME/.mbscore
	      the local score file.  This is used, if moon-buggy has no write access to the global score file.

SEE ALSO

       Moon-buggy Usage and Maintenance by Jochen Voss.

COPYING

       Copyright (C) 2004  Jochen Voss

       Moon-buggy is free software.  Read the file COPYING of the source code distribution for details or press 'c' at moon-buggy's title screen.

AUTHOR

       The program moon-buggy was implemented by Jochen Voss (voss@seehuhn.de).

moon-buggy 1.0.51+esd						    Dec 27 2004 						     moon-buggy(6)

AnyEvent::Impl::Tk(3pm) 				User Contributed Perl Documentation				   AnyEvent::Impl::Tk(3pm)

NAME

       AnyEvent::Impl::Tk - AnyEvent adaptor for Tk

SYNOPSIS

	  use AnyEvent;
	  use Tk;

	  # this module gets loaded automatically as required

DESCRIPTION

       This module provides transparent support for AnyEvent. You don't have to do anything to make Tk work with AnyEvent except by loading Tk
       before creating the first AnyEvent watcher.

       Tk is buggy. Tk is extremely buggy. Tk is so unbelievably buggy that for each bug reported and fixed, you get one new bug followed by
       reintroduction of the old bug in a later revision. It is also basically unmaintained: the maintainers are not even interested in improving
       the situation - reporting bugs is considered rude, and fixing bugs is considered changing holy code, so it's apparently better to leave it
       broken.

       I regularly run out of words to describe how bad it really is.

       To work around some of the many, many bugs in Tk that don't get fixed, this adaptor dup()'s all filehandles that get passed into its I/O
       watchers, so if you register a read and a write watcher for one fh, AnyEvent will create two additional file descriptors (and handles).

       This creates a high overhead and is slow, but seems to work around most known bugs in Tk::fileevent on 32 bit architectures (Tk seems to be
       terminally broken on 64 bit, do not expect more than 10 or so watchers to work on 64 bit machines).

       Do not expect these workarounds to avoid segfaults and crashes inside Tk.

       Note also that Tk event ids wrap around after 2**32 or so events, which on my machine can happen within less than 12 hours, after which Tk
       will stomp on random other events and kill them. So don't run Tk programs for more than an hour or so.

       To be able to access the Tk event loop, this module creates a main window and withdraws it immediately. This might cause flickering on some
       platforms, but Tk perversely requires a window to be able to wait for file handle readyness notifications. This window is always created
       (in this version of AnyEvent) and can be accessed as $AnyEvent::Impl::Tk::mw.

SEE ALSO

       AnyEvent, Tk.

AUTHOR

	Marc Lehmann <schmorp@schmorp.de>
	http://anyevent.schmorp.de

perl v5.14.2							    2012-04-08						   AnyEvent::Impl::Tk(3pm)