blackbox(1)

📦
version 0.77 · 2 versions
, in arch rolling, fedora 43, fedora 44

💖 blackbox 💖

okay bestie, grab a snack because we're reading the blackbox(1) manual together and it's a whole journey. it's a window manager for X11 and honestly? she's iconic. let's go. 🦋

✨ NAME ✨

blackbox — a window manager for X11. that's it, that's the girl. 💅

✨ SYNOPSIS ✨

blackbox -help | -version
blackbox [ -rc rcfile ] [ -display display ]

✨ DESCRIPTION ✨

so Blackbox is a window manager for the Open Group's X Window System, Version 11 Release 6 and up. her whole design philosophy is visually minimalist and fast — lowkey the original clean girl aesthetic. ✨

Blackbox is similar to the NeXT interface and Windowmaker. you launch apps from a menu that you get by right clicking on the root window. workspaces (which is a whole system of virtual desktops, iykyk) are controlled through a menu you get by middle clicking on the root window, plus through the toolbar. and individual windows? you control those with the buttons on the title bar, and there's even more options if you right click on the title bar. so many vibes, so many clicks. 🖱️

Blackbox can generate beautiful window decorations on the fly at high speed — no cap, she's fast. themes, which Blackbox calls styles, are super flexible, but the use of pixmaps has been purposefully avoided to eliminate dependencies and excess memory usage. minimal queen behavior. 👑

here's the thing though — Blackbox itself does not directly handle key bindings like most other window managers do. that task belongs to a separate utility called bbkeys. and even though Blackbox has a built-in workspace (paging) system, bbpager, which gives you a graphical pager, is popular with a lot of users. you can find bbkeys, bbpager and several other bbtools by going to:

http://bbtools.thelinuxcommunity.org/

the slit is an edge of the screen that can hold specially designed programs called dock apps (from Windowmaker). also, the popular program gkrellm will run in the slit too. there is a HUGE selection of dockapps out there and they run the gamut from must-have gadgets to utterly useless (but cute and/or funny) eye candy. 😭💖

http://www.bensinclair.com/dockapp/

http://dockapps.org/

✨ OPTIONS ✨

Blackbox supports the following command line options:

  • -help — display command line options, compiled-in features, and exit. the "who am i" button fr.
  • -version — display version and exit. ✨
  • -rc rcfile — use an alternate resource file. pick your own adventure bestie.
  • -display display — start Blackbox on the specified display, and set the DISPLAY environment variable to this value for programs started by Blackbox.

✨ STARTING AND EXITING BLACKBOX ✨

the most common way to start Blackbox is to put the command "blackbox" (no quotes, obviously) at the end of your ~/.xinitrc or ~/.xsession file. the advantage of putting Blackbox at the end of the file is that the X Server will shut down when you exit Blackbox. 💀 clean exit, no loose ends. Blackbox can also be started from the command line of a terminal program like xterm in an X session that doesn't already have a window manager running.

on startup, Blackbox will look for ~/.blackboxrc and use the resource session.menuFile to figure out where to get the menu for the session. if that file isn't found, Blackbox will use /usr/share/blackbox/menu as the menu file. and if that fails too? Blackbox falls back to a default menu that contains commands to start an xterm as well as restart and exit the window manager. she always has a plan B. 🫶 the other resources available in the ~/.blackboxrc file are discussed later in this manual under the heading RESOURCE FILE.

on exit, Blackbox writes its current configuration to ~/.blackboxrc.

NOTE: if ~/.blackboxrc is modified during a Blackbox session, Blackbox must be restarted with the "restart" command on the main menu, or the changes will be lost on exit. Restart causes Blackbox to re-read ~/.blackboxrc and apply the changes immediately. 😤

Blackbox can be exited by selecting "exit" on the main menu (discussed shortly), by killing it gently from a terminal, or by the X Window System shutdown hot key combo Ctrl+Alt+BackSpace.

✨ USING BLACKBOX ✨

a three button mouse has the following functions when you click on the root window:

  • Button Two (Middle Button) — open workspace menu
  • Button Three (Right Button) — open main menu

just so we're clear: Button One (Left Button) is not used. she's off duty. 🙈

the default installation assumes you have a number of common X Window System programs in their typical locations. the default menu is defined by a plain text file named 'menu'. it is heavily commented and covers a bunch of details of menu file syntax. you can also edit this file graphically using the extension program bbconf, which makes menu creation very easy. menu file syntax is discussed later in this manual.

Caveat: menus can run arbitrary command lines, but if you wish to use a complex command line it is best to place it in a shell script. remember to put #!/bin/bash on the first line and chmod 755 on the file to make it executable. 🔥

🌸 Workspace Menu

this menu gives the user control of the workspace system. you can create a new workspace, remove the last workspace, or go to an application via either the icon menu or a workspace entry. workspaces are listed by name. clicking on the workspace name will take you to that workspace with focus on the program under the mouse. if there are programs already running in the workspace, they'll appear in a pop-out menu. clicking on the application name will jump to the workspace and focus that application. and if you use a middle click instead? the window gets brought to the current workspace. ✨

Blackbox uses an external program, bbpager, to provide a traditional, graphical paging interface to the workspace system. many Blackbox users also run another extension program — bbkeys — to provide keyboard shortcuts for workspace control.

Caveat: to name a workspace, the user must right click on the toolbar, select "Edit current workspace name," type the workspace name, and press Enter to finish. (And_Press_Enter — do not skip this step bestie, it will not work and you will be sad 😭)

workspaces can also be named in the .blackboxrc file as described in RESOURCES.

🌸 The Slit

the Slit provides a user positionable window for running utility programs called "dockapps". to learn more about dockapps, refer to the web sites mentioned in the Description. dockapps automatically run in the slit in most cases, but may require a special command switch. often, -w is used for "withdrawn" into the slit.

gkrellm is a very useful and modern dockapp that gives the user near real time information on machine performance. other dockapps include clocks, notepads, pagers, key grabbers, fishbowls, fire places and many, many others. 🐠🔥

only mouse button three is captured by the Blackbox slit. this menu lets the user change the position of the slit, and sets the state of Always on top and Auto hide. these all do what the user expects. slay.

Caveat: when starting dockapps from an external script, a race condition can take place where the shell rapidly forks all of the dockapps, which then take varied and random times to draw themselves for the first time. to get the dockapps to start in a given order, follow each dockapp with sleep 2; this ensures that each dockapp is placed in the correct order by the slit. i.e.
#!/bin/bash
speyes -w & sleep 2
gkrellm -w & sleep 2

🌸 The Toolbar

the toolbar provides an alternate method for cycling through multiple workspaces and applications. the left side of the toolbar is the workspace control, the center is the application control, and the right side is a clock. the format of the clock can be controlled as described under RESOURCES. ⏰

Mouse button 3 raises a menu that allows configuration of the toolbar. it can be positioned either at the top or the bottom of the screen, and can be set to auto hide and/or to always be on top.

Caveat: the toolbar is a permanent fixture. it can only be removed by modifying the source and rebuilding, which is beyond the scope of this document. setting the toolbar to auto hide is the next best thing. 💀

🌸 Window Decorations

window decorations include handles at the bottom of each window, a title bar, and three control buttons. the handles at the bottom of the window are divided into three sections. the two corner sections are resizing handles. the center section is a window moving handle. the bottom center handle and the title bar respond to a number of mouse clicks and key + mouse click combinations. the three buttons in the title bar, left to right, are iconify, maximize, and close. the resize button has special behavior detailed below. 👑

💅 Button One (Left Button)

click and drag on the titlebar to move, or resize from the bottom corners. click the iconify button to move the window to the icon list. click the maximize button to fully maximize the window. click the close button to close the window and application. double-click the title bar to shade the window.

💅 Alt + Button One

click anywhere on the client window and drag to move the window.

💅 Button Two (Middle Button)

click the titlebar to lower the window. click the maximize button to maximize the window vertically.

💅 Button Three (Right Button)

click on the title bar or bottom center handle to pull down a control menu. click the maximize button to maximize the window horizontally.

💅 Alt + Button Three

click anywhere on the client window and drag to resize the window.

the control menu contains:

🎀 Send To ...

  • Button One (Left Button) — click to send this window to another workspace.
  • Button Two (Middle Button) — click to send this window to another workspace, change to that workspace, and keep the application focused as well.

🎀 Shade

this is the same action as double-click with Button One.

🎀 Iconify

hide the window. it can be accessed with the icon menu.

🎀 Maximize

toggle window maximization.

🎀 Raise

bring the window to the front above the other windows and focus it.

🎀 Lower

drop the window below the other ones.

🎀 Stick

stick this window to the glass on the inside of the monitor so it does not hide when you change workspaces. 🪟✨

🎀 Kill Client

this kills the client program with -SIGKILL (-9).

only use this as a last resort. fr fr. 😭

🎀 Close

send a close signal to the client application.

🌈 STYLES 🌈

okay bestie, a style is a whole collection of colors, fonts, and textures that controls how Blackbox looks. it's the outfit. the lewk. and all of it gets recorded in style files. the default system style files live in /usr/share/blackbox/styles. the menu system identifies each style by its filename, and you can sort styles into different directories at your own discretion, because it's your desktop and you're the main character 💅

there are over 700 styles available for Blackbox. the official distribution point for Blackbox styles is

http://blackbox.themes.org/

all themes should install by simply downloading them to ~/.blackbox/ then unzip it, and de-tar it. (unzip it AND de-tar it. both. she said what she said.)

on open Unixes this will be:

tar zxvf stylename.tar.gz

on commercial Unixes this will be something like:

gunzip stylename.tar.gz && tar xvf stylename.tar

check your system manuals for specifics or check with your network administrator. 🫶

an entry should appear in the styles menu immediately.

⚠️ Security Warning ⚠️

style files can execute shell scripts and other executables. it would be wise to check the rootCommand in the style file and make sure that it is benign. no cap, please actually look at it. 🔥

💀 Things that go wrong 💀

  1. The theme is pre Blackbox 0.51.

style file syntax changed with version 0.51

  1. The style tarball was formatted incorrectly.

some styles use the directories ~/.blackbox/Backgrounds and ~/.blackbox/Styles

this can be fixed by adding a [stylemenu] (~/.blackbox/Styles) to your menu file. to be a complete purist, hack the style file with the correct paths and move the files into the correct directories

  1. The rootCommmand line is broken.

the rootCommand line in the style file will run an arbitrary executable. it is important that this executable be set to bsetbg to maintain portability between systems with different graphics software. in addition bsetbg can execute a shell script and do it in a portable fashion as well.

the documented method for creating styles is as follows:

  1. Create or acquire the background for the style if it will not be using bsetroot to draw a patterned background for the root window.
NOTE: Blackbox runs on a wide variety of systems ranging from PCs with 640x480 256 color displays to ultra high speed workstations with 25" screens and extreme resolution. for best results a style graphic should be at least 1024x768. ✨
  1. Create a style file.

the best way to do this is to make a copy of a similar style and then edit it.

the style file is a list of X resources and other external variables. manipulating these variables allows users to completely change the appearance of Blackbox. the user can also change the root window image by using the wrapper program bsetbg.

bsetbg knows how to use a number of programs to set the root window image. this makes styles much more portable since various platforms have different graphics software. for more info see bsetbg (1).

  1. Background images should be placed in ~/.blackbox/backgrounds. The style file should be placed in ~/.blackbox/styles, any other information about the style should be placed in ~/.blackbox/about/STYLE_NAME/. This would include README files, licenses, etc.

previous versions of Blackbox put backgrounds and styles in different directories. the directories listed above are the only officially supported directories. however you may put them wherever you like as long as you update your menu file so it knows where to find your styles.

  1. To create a consistent experience and to ensure portability between all systems it is important to use the following format to create your style archive.

first create a new directory named after your style NEW_STYLE

in this directory create the directories

backgrounds
styles
about/NEW_STYLE

next put everything for the theme in these locations. finally type

tar cvzf NEW_STYLE.tar.gz *

if you are using commercial Unix you may need to use gzip and tar separately.

now when a user downloads a new style file she knows that all she has to do is put the tarball in her Blackbox directory, unzip->un-tar it and then click on it in her style menu. iconic. 👑

🌸 Style File Syntax and Details 🌸

by far the easiest way to create a new style is to use bbconf. bbconf allows complete control of every facet of style files and gives immediate updates of the current style as changes are made. (it's giving instant gratification and we love her for it.)

the style file format is not currently documented in a man page. there is a readme document included with the Blackbox source containing this information.

the default menu file is installed in /usr/share/blackbox/menu. this menu can be customized as a system default menu or the user can create a personal menu.

to create a personal menu, copy the default menu to a file in your home directory. then, open ~/.blackboxrc and add or modify the resource

session.menuFile:  ~/.blackbox/menu

next, edit the new menu file. this can be done during a Blackbox session and the menu will automatically be updated when the code checks for file changes. obsessed.

the default menu included with Blackbox has numerous comments describing the use of all menu commands. menu commands follow this general form:

[command]  (label|filename) {shell command|filename}

Blackbox menu commands

  • # string... — hash (or pound or number sign) is used as the comment delimiter. it can be used as a full line comment or as an end of line comment after a valid command statement.
  • [begin] string — this tag is used only once at the beginning of the menu file. string is the name or description used at the top of the menu.
  • [end] — this tag is used at the end of the menu file and at the end of a submenu block.
  • [exec] label string {command string} — a very flexible tag that allows the user to run an arbitrary shell command including shell scripts. if a command is too large to type on the command line by hand it is best to put it in a shell script.
  • [nop] label string — this tag is used to put a divider in the menu. label string is an optional description.
  • [submenu] submenu name {title string} — this creates a sub-menu with the name submenu name and if given, the string title string will be the title of the pop up menu itself.
  • [include] filename — this command inserts filename into the menu file at the point at which it is called. filename should not contain a begin end pair. this feature can be used to include the system menu or include a piece of menu that is updated by a separate program.
  • [stylesdir] description path — causes Blackbox to search path for style files. Blackbox lists styles in the menu by their file name as returned by the OS.
  • [stylesmenu] description {path} — this command creates a submenu with the name description with the contents of path. by creating a submenu and then populating it with stylesmenu entries the user can create an organized library of styles. 📚
  • [workspaces] description — inserts a link into the main menu to the workspace menu. if used, description is an optional description.
  • [config] label — this command causes Blackbox to insert a menu that gives the user control over focus models, dithering and other system preferences.
  • [reconfig] label {shell command} — the reconfig command causes Blackbox to reread its configuration files. this does not include ~/.blackboxrc which is only reread when Blackbox is restarted. if shell command is included Blackbox will run this command or shell script before rereading the files. this can be used to switch between multiple configurations.
  • [restart] label {shell command} — this command is actually an exit command that defaults to restarting Blackbox. if provided, shell command is run instead of Blackbox. this can be used to change versions of Blackbox. not that you would ever want to do this but, it could also be used to start a different window manager. 🙈
  • [exit] label — shuts down Blackbox. if Blackbox is the last command in your ~/.xinitrc file, this action will also shutdown X.

here is a working example of a menu file:

[begin] (MenuName)
   [exec] (xterm) {xterm -ls -bg black -fg green}
   [submenu] (X utilities)
      [exec] (xcalc) {xcalc}
   [end]
   [submenu] (styles)
      [stylesmenu] (built-in styles) {/usr/share/blackbox/styles}
      [stylesmenu] (custom styles) {~/.blackbox/styles}
   [end]
   [workspaces] (workspace list)
   [config] (configure)
   [reconfig] (config play desktop) {play-config-blackbox}
   [reconfig] (config work desktop) {work-config-blackbox}
   [restart] (start Blackbox beta 7) {blackbox-beta7}
   [restart] (start Blackbox cvs) {blackbox-cvs}
   [restart] (restart)
   [exit] (exit)
[end]

🎀 RESOURCE FILE 🎀

$HOME/.blackboxrc — okay so all these options live in your ~/.blackboxrc file, bestie. They control basically every vibe of Blackbox, and most of them you can change straight from the menus. Some of them? Nope, those ones you gotta go edit .blackboxrc with your own two hands.

⚠️ NOTE: Blackbox only reads this file during start up. So if you want your changes to actually do anything mid-session, you have to pick "restart" on the main menu. Skip that step and your changes get yeeted into the void the second Blackbox exits. 💀

Some resources have a <num> chillin' after screen. Swap that out for the number of the screen you're configuring. Default is 0 (zero).

Right click (button 3) on the slit border.

  • session.screen<num>.slit.placement — SEE BELOW. This sets where the slit sits. Fair warning: certain combos of slit.placement and slit.direction are genuinely not it — like, TopCenter with Vertical direction just puts the slit straight through the middle of your screen. Some of y'all will think that's iconic purely for the chaos. No judgement. ✨ Default is CenterLeft.
[  TopLeft  |   TopCenter  |   TopRight  |
 CenterLeft |              | CenterRight |
 BottomLeft | BottomCenter | BottomRight ]
  • session.screen<num>.slit.direction [Horizontal|Vertical] — which way the slit goes. Default is Vertical.
  • session.screen<num>.slit.onTop [True|False] — is the slit always visible over your windows, or can the focused window cover it up? Default is True.
  • session.screen<num>.slit.autoHide [True|False] — does the slit hide itself when nobody's using it? The session.autoRaiseDelay time is what decides how long you gotta hover to make it pop up, and how long it lingers after your mouse dips out. Default is False.
  • session.screen<num>.focusModel — SEE BELOW. Sloppy focus (aka mouse focus) is the classic X Window behavior, and you can tweak it with AutoRaise or Click-Raise.
    • AutoRaise makes the window raise itself automatically after session.autoRaiseDelay milliseconds.
    • ClickRaise makes the window raise when you click anywhere inside the client area of the window.
    • Sloppy focus all on its own means you gotta click the titlebar, border, or lower grip to raise the window.
    • ClickToFocus means you have to click a Blackbox decoration or the client area to focus and raise the window. And nope, ClickToFocus cannot be modified by AutoRaise or ClickRaise. It said what it said. 💅
    • Default is SloppyFocus.
[SloppyFocus [[AutoRaise & ClickRaise]  |
              [AutoRaise | ClickRaise]] |
ClickToFocus]
  • session.screen<num>.windowPlacement — SEE BELOW.
    • RowSmartPlacement tries to squeeze new windows into empty space by making rows. The direction depends on session.screen<num>.rowPlacementDirection.
    • ColSmartPlacement tries to squeeze new windows into empty space by making columns. The direction depends on session.screen<num>.colPlacementDirection.
    • CascadePlacement drops the new window down and to the right of the most recently created window.
    • Default is RowSmartPlacement.
[RowSmartPlacement | ColSmartPlacement | CascadePlacement]
  • session.screen<num>.rowPlacementDirection [LeftToRight|RightToLeft] — sets the placement direction for new windows. Default is LeftToRight.
  • session.screen<num>.colPlacementDirection [TopToBottom|BottomToTop] — same deal, but for columns. Default is TopToBottom.
  • session.imageDither [True|False] — only matters when you're running in low color modes. Image dithering helps an image look right even when the system doesn't have enough colors to go around. Default is False.
  • session.opaqueMove [True|False] — do the window's contents get drawn while it's being moved? When it's False, you get a little box representing the window instead. Default is False.
  • session.screen<num>.fullMaximization [True|False] — does the maximize button let an app maximize over the slit and toolbar? Default is False.
  • session.screen<num>.focusNewWindows [True|False] — do brand new windows get focus once they've drawn themselves for the first time? Default is False.
  • session.screen<num>.focusLastWindow [True|False] — okay this one is literally "when I move between workspaces, remember which window had focus when I left, and give focus back to that window when I come back to that workspace." Default is False.
  • session.screen<num>.disableBindingsWithScrollLock [True|False] — turn this on and scroll lock stops Blackbox from grabbing the Alt and Ctrl keys it normally uses for mouse controls. This exists so people using drawing and modeling programs (the ones that use keystrokes to modify mouse actions) can keep their sanity. 🧚 *NOTE* this has _no_ effect on bbkeys. If you need bbkeys to act like this too, it has a similar option in its config file — go read the bbkeys manpage for the deets. Default is False.

Middle click (button 2) on the root window (AKA the Desktop) to reach this menu.

  • session.screen<num>.workspaces [integer] — you can make or delete workspaces by middle clicking the desktop and choosing "New Workspace" or "Remove Last". After you make one, right click the toolbar to give it a name. Default is 1.
  • session.screen<num>.workspaceNames [string[, string...]] — workspaces get named in the order you list them in this resource, and the names gotta be separated by commas. If you've got more workspaces than you've got explicit names, the un-named ones get called "Workspace [number]". Default is Workspace 1.
  • session.screen<num>.toolbar.placement — SEE BELOW. Sets the toolbar's screen position. Default is BottomCenter.
[  TopLeft  |   TopCenter  |   TopRight  |
 BottomLeft | BottomCenter | BottomRight ]
  • session.screen<num>.toolbar.onTop [True|False] — is the toolbar always visible over your windows, or can the focused window hide it? Default is True.
  • session.screen<num>.toolbar.autoHide [True|False] — does the toolbar hide when it's not in use? The session.autoRaiseDelay time decides how long you hover before it raises, and how long it stays up after your mouse leaves. Default is False.

✨ Configurable in ~/.Blackboxrc only ✨

  • session.screen<num>.toolbar.widthPercent [1-100] — what percentage of the screen the toolbar eats up. A number from 1-100 sets the width. Heads up: 0 (zero) does not make the toolbar vanish — it just resets the toolbar to the default. If you genuinely want the toolbar gone, there are patches for that. Default is 66.
  • session.screen<num>.strftimeFormat [string] — a C language date format string, and you can use any combination of specifiers. The default is %I:%M %p, which gives you a 12 hour clock with minutes and an am/pm indicator appropriate to your locale.
24 hours and minutes    %H:%M
12 hours and minute     %I:%M %p
month/day/year          %m/%d/%y
day/month/year          %d/%m/%y

Default is hours:minutes am/pm. See strftime 3 for more details. 📖

  • session.screen<num>.dateFormat [American|European] — NOTE: only used if the strftime() function isn't available on your system. Default is American, (mon/day/year).
  • session.screen<num>.clockFormat [12/24] — NOTE: only used if the strftime() function isn't available on your system. Default is 12-hour format.
  • session.screen<num>.edgeSnapThreshold [integer] — set it to 0 and edge snap is off. Set it to one or greater and edge snap makes a window that's being moved snap to the nearest screen edge, the slit, or the toolbar. Windows will not snap to each other, just so we're clear. The value is a number in pixels — the distance required between the window and a screen edge before it snaps. If you like this feature, values between 6 - 10 work nicely. Default value is 0.
  • session.menuFile [filepath] — full path to the current menu file. Default is /usr/share/blackbox/menu.
  • session.colorsPerChannel [2-6] — how many colors get taken from the X server for use on pseudo color displays. This value must be set to 4 for 8 bit displays. Default is 4.
  • session.doubleClickInterval [integer] — the max time Blackbox waits after one click to catch a double click. This only applies to Blackbox actions (like double click shading), not to the X server in general. Default is 250 milliseconds.
  • session.autoRaiseDelay [integer] — the time in milliseconds used for auto raise and auto hide behaviors. More than about 1000 ms is probably useless, ngl. Default is 250 millisecond.
  • session.cacheLife [integer] — the max number of minutes the X server will cache unused decorations. Default is 5 minutes.
  • session.cacheMax [integer] — how many kilobytes Blackbox may take from the X server for storing decorations. Bump this number up and you might get better performance if you've got plenty of memory and you use a ton of different windows. Default is 200 Kilobytes.

🌈 ENVIRONMENT 🌈

  • HOME — Blackbox uses $HOME to find its .blackboxrc rc file and its .blackbox directory for menus and style directories.
  • DISPLAY — if a display isn't specified on the command line, Blackbox will use the value of $DISPLAY.

🍓 FILES 🍓

  • blackbox — Application binary
  • ~/.blackboxrc — User's startup and resource file.
  • /usr/share/blackbox/menu — Default system wide menu

💜 WEB SITES 💜

General info website:

http://blackboxwm.sourceforge.net/

Development website:

http://sourceforge.net/projects/blackboxwm/

💀 BUGS 💀

If you think you've found a bug, please help a girl out by heading to the development website and selecting "Bugs" in the upper menu. Check the bug list to see if your problem's already been reported. If it has, read the summary and add any info you think would help. If your bug hasn't been submitted yet, select "Submit New" and fill out the form. 🫶

👑 AUTHORS AND HISTORY 👑

Okay bestie, storytime, because this software has lore and honestly it's giving origin-myth energy. ✨

  • Sean Shaleh Perry <shaleh@debian.org> — he's the current maintainer, and he's actively working together with Brad to keep Blackbox up-to-date and stable as a rock. Periodt. 🪨
  • Brad Hughes <bhughes@trolltech.com> — the original icon. He designed and coded Blackbox in 1997, with the intent of creating a memory efficient window manager with no dependencies on external libraries. Like… the audacity?? The vision?? Brad's original idea has become a popular alternative to other window managers. He ate and left no crumbs. 💅
  • Jeff Raven <jraven@psu.edu> — then picked up the torch for the 0.61.x series after Brad took a full time job at TrollTech. Passing the torch, main character handoff, we love to see it. 🔥
  • This manual page was written by: R.B. Brig Young <secretsaregood@yahoo.com> — and ngl, he is solely responsible for errors or omissions. Comments, corrections, and suggestions are welcomed. So if you spot something goofy, be nice about it and send it in! 🫶

🌈 SEE ALSO 🌈

Sibling pages, the whole family, go read them:

And that's a wrap on the whole page, bestie!! 🎀 This was written for Blackbox 0.65.0, dated September 18, 2002 — yes, she's vintage, yes she's still iconic, no notes. Now go forth and tile nothing, float everything, and be the main character of your own desktop. 💖🦋🌸

📦 where this page comes from