AfterStep is a window manager for the Unix X Window System. Originally based on the look and feel of the NeXTStep interface, it provides end users with a consistent, clean, and elegant desktop. The goal of AfterStep development is to provide for flexibility of desktop configuration, improving aestetics, and efficient use of system resources.

All official releases can be downloaded from ftp://ftp.afterstep.org. AfterStep 2.0 beta releases : beta5 tar.gz or tar.bz2 released on August 17, 2004.

This is intended as an overview of what AfterStep has to offer, the documentation holds information how to achieve these things.

1.2. What is AfterStep? AfterStep is a Window Manager for the X Window System (hereafter referred to as X). It was started to emulate the look and feel of NeXTSTEP(tm), but has evolved into something that while still being able to emulate NeXT, can do much much more.

AfterStep 2.0 comes with many changes and improvements over the previous 1.8* series of AfterStep, yet everything you've come to expect and love in AfterStep is still there. Some of the new features and improvements are: AfterStep 2.0beta1: New high performance and high quality image handling engine. Support for TrueType fonts. Text antialiasing.

AfterStep comes with a variety of resources and helpfiles to get your AfterStep up and running and configured to your liking. Outside of these 'static' resources, help can also be found on the AfterStep mailinglists or our IRC channel.

This should give those not using AfterStep, a good perspective of what can be done. AfterStep is, as you can see, very configurable and can be adjusted to suit your taste and needs.

AfterStep AutoExec Base Configuration Function STANDARD OPTIONS The following is the list of command line options supported by all AfterStep modules and applications.

If you have AfterStep 2.0.1 or later installed - aterm should be able to detect it and integrate into AfterStep. That allows you to setup MyStyle structures in AfterStep look, making aterm automagically use them upon startup.

AfterStep will search through the directories specified in the ModulePath configuration in the base (where # is your colordepth) to attempt to locate Pager. CONFIGURATION FILES. Pager reads the base file and pager file when it starts up and looks for its configuration options.