Fluxbox is a windowmanager for X that was based on the Blackbox 0.61.1 code. It is very light on resources and easy to handle but yet full of features to make an easy, and extremely fast, desktop experience.

Fluxbox’ featurelist. # Some of the main features lay under the hood and might not seem to be obvious at first glance. APPS-FILE # One of the most underestimated - although one of the most powerful features - is the apps-file.

See fluxbox-keys(5) and fluxbox-menu(5) for details. The “keys” file also provides two commands that can alter the current environment of fluxbox: SetEnv and Export. Any changes made by these commands will also affect the environment as seen by fluxbox and all child processes started after that point. See fluxbox-keys(5) for details.

Get your copy of fluxbox. # The current version of Fluxbox is 1.3.7. Read the NEWS-file to get an overview of the improvements.

Fluxbox installs a default root menu file in @pkgdatadir@/menu. You can also use fluxbox -i to confirm this location. Of course this system-wide menu can be customized for all users at once, but it is also possible to create an individual menu file for each user. By convention, users create a menu file in ~/.fluxbox/menu. Once you’ve created ...

startfluxbox is a script which runs the file ~/.fluxbox/startup If it doesn’t exist it will be generated. startfluxbox should be started from your \/.xinitrc if you use startx, or ~/.xsession if you run a display manager, like xdm.

You can customize fluxbox’s key handling through the ~/.fluxbox/keys file. The file consists of lines of the basic format: [ modifiers ] key :‘command’ [ arguments …

Styles are simple ASCII text files that tell fluxbox(1) how to generate the appearance of different components of the window manager. The default installation of fluxbox(1) is shipped with many classic examples that show a great deal of what one could do.

You do not need to “reload” fluxbox after editing the apps file, the changes should be rescanned when the next window is opened. The file is made up of two main types of sections, apps and groups, detailed below.

fluxbox-remote(1) is designed to allow scripts to execute most key commands from fluxbox(1). fluxbox-remote(1) will only work with fluxbox(1) : its communications with fluxbox(1) are not standardized in any way.