FLUXBOX-STYLE(5)

📦
version 1.3.7+248+g5ba8c921 · 3 versions
, in arch rolling

💅 FLUXBOX-STYLE(5) — the fluxbox manual, but make it make sense

okay so bestie, welcome to fluxbox-style(5) 💖 this is the whole entire lore drop on styles/themes for fluxbox(1), and ngl it's a lot, so grab a snack. we're doing this properly.

✨ NAME ✨

fluxbox-style — a comprehensive look at styles/themes for fluxbox(1). like, comprehensive comprehensive. buckle up 🎀

✨ SYNOPSIS ✨

This document describes various options available for fluxbox styles. that's it, that's the synopsis. short king 🫶

✨ DESCRIPTION ✨

🦋 What is a Style?

Styles — sometimes called Themes, same vibe different label — are a graphical overlay for the fluxbox(1) window manager. If you wanted to get to know fluxbox, the styles would be the look of the look and feel. literally the outfit, the hair, the makeup of your desktop 👑

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. To use one of the standard styles, navigate to the System Styles menu under your main fluxbox(1) menu. it's right there, go click it 💅

fluxbox(1) uses its own graphics class to render its images on the fly. By using styles you can determine, at a great level of configurability, what your desktop will look like. and since fluxbox(1) was derived from blackbox, many of y'all often wonder: do old themes still work on the latest releases of fluxbox(1)? Well — they basically do, but you will have to tune them, since the fluxbox(1) code has changed quite a bit since the initial grab. so, like, vintage but not archive-level vintage 😭

✨ STRUCTURE ✨

A style is made up of a few major components which then have their own sub-directives. The major components are as follows, and yes I'm listing them all:

  • The window.* directives control the appearance of the window frames.
  • window.tab.* controls the appearance of the window tabs.
  • menu.* controls the appearance of the popup menu that you see when you right click on the desktop.
  • toolbar.* is the bar you will see at the top or bottom of your screen.
  • Finally the slit.* has options you can use to customize the appearance of the slit. However — if you don't set the slit directives specifically, the slit's appearance is controlled by the toolbar directives instead. sneaky little inheritance moment 🧚

To understand how the style mechanism works, it is nice to know a little about how X11 resources work. so, mini lesson, no cap: X11 resources consist of a key and a value. The key is constructed of several smaller keys (sometimes referred to as children), delimited by a period (.). Keys may also contain an asterisk (*) to serve as a wildcard, which means that one line of text will match several keys. This is useful for styles that are based on one or two colors. efficiency queen 🌸

A more complete reference to this can be found in X(7), section RESOURCES. go read it, iykyk.

✨ LOCATION ✨

There are many places to store your styles, the most common is in your ~/.fluxbox/styles directory. The initial installation will place the default styles in /usr/share/fluxbox/styles, providing a basic usable configuration. 🏠

When creating your own style, create a directory (normally the name of your style) in ~/.fluxbox/styles/ (If the styles directory doesn't exist, create that also). While there isn't an official structure, it is common to create a directory named after your style and place your pixmaps directory (if required) in there, along with a file called theme.cfg (may also be named style.cfg). This file is where you will construct your style using the components covered later in this manual page. it's giving arts and crafts but make it config 🎨

An example of steps taken when beginning a style project of your own may look like:

$ cd
$ mkdir -p ~/.fluxbox/styles/YourStyle/pixmaps
$ cd ~/.fluxbox/styles/YourStyle
$ nano theme.cfg

Output of a packaged style should look like the following:

$ cd
$ tar -tjvf YourStyle.tar.bz2
 .fluxbox/styles/YourStyle/theme.cfg
 .fluxbox/styles/YourStyle/pixmaps
 .fluxbox/styles/YourStyle/pixmaps/stick.xpm
...

Of course, all of these are just preferences — fluxbox(1) allows for the customization of many things, including how you handle your styles. Just remember, however, that if you plan to distribute your style you may find some community bickering if you don't follow practices. :) fr fr, the style community has opinions and they will share them 💀

✨ CREATING YOUR STYLE ✨

As discussed above, fluxbox(1) allows you to configure its four main components: the toolbar, menus, slit and window decorations. Remember that you can customize the slit with its own directives, otherwise the slit will take the appearance of the toolbar. 🔥

Here are some quick examples to illustrate basic syntax:

toolbar.clock.color: green

This sets the color resource of the toolbar clock to green. slay, one line, one job.

Another example:

menu*color:     rgb:3/4/5

This sets the color resource of the menu and all of its children to rgb:3/4/5. (For a description of color names, see X(1).) So this one also applies to menu.title.color and menu.frame.color. see how the wildcard eats? iconic behavior.

And with

*font:  -b&h-lucida-medium-r-normal-*-*-140-*

you set the font resource for all keys to this font name all at once. (For information about the fonts installed on your system, you can use a program like xfontsel(1), gtkfontsel, or xlsfonts(1).) 🦋

In the last example you will notice the wildcard (*) before font. In a Fluxbox style you can set a value with a wildcard. The example means that every font in the style will be what is specified. You can do this with any component/value. For example, if you wanted all of the text to be one color you would do:

*textColor:  rgb:3/4/5

This means that you can setup a very simple style with very few properties. See the EXAMPLES below for an example of this in practice. (yes, they're coming, patience bestie 💜)

fluxbox(1) also allows you to override wildcards in your style. Let's take our example above and add an override for the toolbar.clock.textColor component:

*textColor: rgb:3/4/5
toolbar.clock.textColor: rgb:255/0/0

With that, all of the text will be rgb:3/4/5 except the toolbar clock text, which will be rgb:255/0/0. the clock said "not like the other girls" and honestly? respect. 💅

Now, what makes fluxbox(1) so spectacular is its ability to render textures on the fly. A texture is a fillpattern that you see on some styles. Texture descriptions are specified directly to the key that they should apply to, e.g.:

toolbar.clock:  Raised Gradient Diagonal Bevel1
toolbar.clock.color:    rgb:8/6/4
toolbar.clock.colorTo:  rgb:4/3/2

Don't worry, we will explain what these mean. 🫶 A texture description consists of up to five fields, which are as follows:

  • Flat | Raised | Sunken — gives the component either a flat, raised or sunken appearance.
  • Gradient | Solid — tells fluxbox(1) to draw either a solid color or a gradient texture.
  • Horizontal | Vertical | Diagonal | Crossdiagonal | Pipecross | Elliptic | Rectangle | Pyramid — select one of these texture types. They only work when Gradient is specified. no gradient, no party 🎉
  • Interlaced — tells fluxbox(1) to interlace the texture (darken every other line). This option is most commonly used with gradiented textures, but it also works in solid textures.
  • Bevel1 | Bevel2 — tells fluxbox(1) which type of bevel to use. Bevel1 is the default bevel. The shading is placed on the edge of the image. Bevel2 is an alternative. The shading is placed one pixel in from the edge of the image. one whole pixel of difference and it changes everything, that's design baby ✨

Instead of a texture description, also the option ParentRelative is available, which makes the component appear as a part of its parent, e.g. totally transparent. ghost mode 👻

Or for even more possibilities: Pixmap. If pixmap texture is specified (it might not be necessary on every occasion) the pixmap file is specified in a separate pixmap resource.

toolbar.clock: pixmap
toolbar.clock.pixmap: clock_background.xpm
This feature might need some investigation — reports say that sometimes the resources color and colorTo must be set and then they may not be set. yes this is as confusing as it sounds, and no I can't fix it, it's in the manpage 😭

All gradiented textures are composed of two color values: the color and colorTo resources. When Interlaced is used in Solid mode, the colorTo resource is used to find the interlacing color.

✨ FONT EFFECTS ✨

In addition to specifying the font-family and the font-weight via the supported font-rendering-engine (eg, Xft), fluxbox(1) supports some effects: halo and shadow. glow-up literally 🌈

To set the shadow effect:

menu.title.font: sans-8:bold
menu.title.effect: shadow
menu.title.shadow.color: green
menu.title.shadow.x: 3
menu.title.shadow.y: 3

To set the halo effect:

menu.title.font: sans-8:bold
menu.title.effect: halo
menu.title.halo.color: green

🌸 FONT PROBLEMS

If you have problems installing fonts or getting them to work, you should read the docs page at xfree.org. Here is a link to one of these: http://xfree.org/4.3.0/fonts2.html#3

that's the link. copy it exactly. don't @ me if the site's old, it's canon. 💀

✨ FULL COMPONENT LIST ✨

Here is the exhaustive component list for fluxbox(1) styles. Each one is listed with their type of value required. Comments in a style file are preceded with an exclamation point (!) which we also use here so that these can be pasted into a new theme.cfg to be customized appropriately. Please note that in order to keep styles consistent it is often the practice of stylists to provide all of the theme-items in their style file even if they are not used. This allows the user the ease of changing different components. yes, even the unused ones, that's just how the girlies do it 💅

okay don't go anywhere, the actual giant list is coming in the next part 🎀

🪟 WINDOW OPTIONS 🪟

okay so, this is the section where your windows stop looking like sad grey rectangles and start having main character energy. there are so many knobs in here for window design in fluxbox(1) — like genuinely a slightly unhinged amount — and every single one of them belongs to you. have fun, bestie 💅

here's the whole lineup, exactly how they spell it:

-----------------------------------------
window.bevelWidth:              <integer>
window.borderColor:             <color>
window.borderWidth:             <integer>
window.button.focus:            <texture type>
window.button.focus.color:      <color>
window.button.focus.colorTo:    <color>
window.button.focus.picColor:   <color>
window.button.focus.pixmap:     <filename>
window.button.pressed: <texture type>
window.button.pressed.color:    <color>
window.button.pressed.colorTo:  <color>
window.button.pressed.pixmap:   <filename>
window.button.unfocus:          <texture type>
window.button.unfocus.color:    <color>
window.button.unfocus.colorTo:  <color>
window.button.unfocus.picColor: <color>
window.button.unfocus.pixmap:   <filename>
window.close.pixmap:            <filename>
window.close.pressed.pixmap:    <filename>
window.close.unfocus.pixmap:    <filename>
window.frame.focusColor:        <color>
window.frame.unfocusColor:      <color>
window.grip.focus:              <texture type>
window.grip.focus.color:        <color>
window.grip.focus.colorTo:      <color>
window.grip.focus.pixmap:       <filename>
window.grip.unfocus:            <texture type>
window.grip.unfocus.color:      <color>
window.grip.unfocus.colorTo:    <color>
window.grip.unfocus.pixmap:     <filename>
window.handle.focus:            <texture type>
window.handle.focus.color:      <color>
window.handle.focus.colorTo:    <color>
window.handle.focus.pixmap:     <filename>
window.handle.unfocus:          <texture type>
window.handle.unfocus.color:    <color>
window.handle.unfocus.colorTo:  <color>
window.handle.unfocus.pixmap:   <filename>
window.handleWidth:             <integer>
window.iconify.pixmap:          <filename>
window.iconify.pressed.pixmap:  <filename>
window.iconify.unfocus.pixmap:  <filename>
window.justify:                 <{Left|Right|Center}>
window.label.active:            <texture type>
window.label.active.textColor:  <color>
window.label.focus:             <texture type>
window.label.focus.color:       <color>
window.label.focus.colorTo:     <color>
window.label.focus.font:        <font>
window.label.focus.pixmap:      <filename>
window.label.unfocus:           <texture type>
window.label.unfocus.color:     <color>
window.label.unfocus.colorTo:   <color>
window.label.unfocus.font:      <font>
window.label.unfocus.pixmap:    <filename>
window.label.focus.textColor:   <color>
window.label.unfocus.textColor: <color>
window.maximize.pixmap:         <filename>
window.maximize.pressed.pixmap: <filename>
window.maximize.unfocus.pixmap: <filename>
window.roundCorners:            <{Top|Bottom}{Left|Right}>
window.shade.pixmap:            <filename>
window.shade.pressed.pixmap:    <filename>
window.shade.unfocus.pixmap:    <filename>
window.stick.pixmap:            <filename>
window.stick.pressed.pixmap:    <filename>
window.stick.unfocus.pixmap:    <filename>
window.stuck.pixmap:            <filename>
window.stuck.unfocus.pixmap:    <filename>
window.lhalf.pixmap:            <filename>
window.lhalf.unfocus.pixmap:    <filename>
window.rhalf.pixmap:            <filename>
window.rhalf.unfocus.pixmap:    <filename>
window.title.focus:             <texture type>
window.title.focus.color:       <color>
window.title.focus.colorTo:     <color>
window.title.focus.pixmap:      <filename>
window.title.height:            <integer>
window.title.unfocus:           <texture type>
window.title.unfocus.color:     <color>
window.title.unfocus.colorTo:   <color>
window.title.unfocus.pixmap:    <filename>
-----------------------------------------

notice how it's all lil clusters, iykyk 🎀 you've got your window.button.focus, window.button.unfocus and window.button.pressed families, each one packing a .color, a .colorTo, a .pixmap, and — plot twist — the focus and unfocus ones also get a .picColor. then window.grip.* and window.handle.* do the same focus/unfocus dance, and window.handleWidth takes an <integer> while window.bevelWidth, window.borderWidth are chilling at the top with <integer> too, plus window.borderColor for a <color>.

the title bar girlies are window.title.focus and window.title.unfocus (each with .color, .colorTo, .pixmap) and then window.title.height: <integer> if you're feeling particular about how much vertical real estate the title gets.

the whole button squad — window.close, window.iconify, window.maximize, window.shade, window.stick, window.stuck, window.lhalf and window.rhalf — are pixmap-only, all <filename>, no texture types invited. slay. note that window.stuck, window.lhalf and window.rhalf only come in base + .unfocus, while the others also bring a .pressed to the function. and window.frame.focusColor / window.frame.unfocusColor are the camelCase rebels of the family, no dots before the F — do not let that trip you up bestie, literally just copy it as written 🙈

also a subtle lil thing: window.justify wants <{Left|Right|Center}> with capital letters. keep that in your pocket, because the menu section does it differently and the vibe check will fail if you mix them up. 💀

and window.roundCorners: <{Top|Bottom}{Left|Right}> — yes you read that right, it takes two of them smooshed together. cute corners, iconic behaviour. ✨

everything you need to make your menu look pretty. your right-click deserves a glow-up fr fr.

-----------------------------------------
menu.bevelWidth:                <integer>
menu.borderColor:               <color>
menu.borderWidth:               <integer>
menu.bullet:                    <{empty|square|triangle|diamond}>
menu.bullet.position:           <{left|right}>
menu.frame:                     <texture type>
menu.frame.color:               <color>
menu.frame.colorTo:             <color>
menu.frame.disableColor:        <color>
menu.frame.font:                <font>
menu.frame.justify:             <{Left|Right|Center}>
menu.frame.pixmap:              <filename>
menu.frame.textColor:           <color>
menu.hilite:                    <texture type>
menu.hilite.color:              <color>
menu.hilite.colorTo:            <color>
menu.hilite.font:               <font>
menu.hilite.justify:            <{left|center|right}>
menu.hilite.pixmap:             <filename>
menu.hilite.textColor:          <color>
menu.itemHeight:                <integer>
menu.title:                     <texture type>
menu.title.color:               <color>
menu.title.colorTo:             <color>
menu.title.font:                <font>
menu.title.pixmap:              <filename>
menu.title.textColor:           <color>
menu.title.justify:             <{Left|Right|Center}>
menu.titleHeight:               <integer>
menu.roundCorners:              <{Top|Bottom}{Left|Right}>
menu.selected.pixmap:           <filename>
menu.submenu.pixmap:            <filename>
menu.unselected.pixmap:         <filename>
-----------------------------------------

the three glow-up targets here are menu.frame (the body of the menu), menu.hilite (the item you're hovering, the star of the show honestly 👑) and menu.title (the little header up top). each of those takes a <texture type> plus .color, .colorTo, .pixmap, a .font, a .textColor, and a justify option.

okay and here is the trap i warned you about: menu.frame.justify and menu.title.justify both take <{Left|Right|Center}> — capitals — but menu.hilite.justify takes <{left|center|right}> — all lowercase. not me getting emotional over capitalization 😭 just copy it exactly, bestie.

menu.frame.disableColor: <color> is the vibe for greyed-out entries. menu.bullet picks what your submenu arrows look like — <{empty|square|triangle|diamond}> — and menu.bullet.position decides <{left|right}> side. menu.itemHeight and menu.titleHeight are <integer>, menu.bevelWidth / menu.borderWidth are <integer>, menu.borderColor is a <color>. and menu.roundCorners: <{Top|Bottom}{Left|Right}> because of course she matches the windows. 💅

then the three loner pixmaps: menu.selected.pixmap, menu.unselected.pixmap, menu.submenu.pixmap — all <filename>, all yours. 🦋

🌈 BACKGROUND 🌈

okay this one's highkey important — every style must specify the background option, no exceptions. if you don't want your style to change the user's background, then use background: none and everyone stays happy. 🫶

here's the shape of the whole thing:

background: centered|aspect|tiled|fullscreen|random|solid|gradient <texture>|mod|none|unset
background.pixmap: <file or directory>
background.color: <color>
background.colorTo: <color>
background.modX: <integer>
background.modY: <integer>

now the rules, and yes there are rules, keep up ✨:

  • the options centered, aspect, tiled and fullscreen require background.pixmap to contain a valid file name.
  • the random option requires background.pixmap to contain a valid directory name.
  • for those options, fluxbox(1) will call fbsetbg(1) to set the background.
  • gradient, solid and mod all require background.color to be set.
  • gradient and mod both require background.colorTo.
  • mod additionally requires background.modX and background.modY to be set as well.
  • those options get passed to fbsetroot(1) to set the background.
and the special one: unset is for use in user overlay files only. it specifies that fbsetbg should never be run — because by default, even when none is set in the overlay, fluxbox will still try to run fbsetbg -z to restore the last wallpaper. so if you want zero wallpaper shenanigans, that's your girl. 🙈

🧚 SLIT 🧚

short and sweet, here are all of the options for the slit:

-----------------------------------------
slit: <texture type>
slit.bevelWidth: <integer>
slit.borderColor: <color>
slit.borderWidth:               <integer>
slit.color:                     <color>
slit.colorTo:                   <color>
slit.pixmap:                    <filename>
-----------------------------------------

you get the base slit: <texture type>, a slit.bevelWidth and slit.borderWidth as <integer>, slit.borderColor as <color>, the slit.color / slit.colorTo pair, and slit.pixmap: <filename> if you're an image kind of person. that's it, that's the whole section, we love a low-effort icon. 🎀

👑 TOOLBAR OPTIONS 👑

below you will find all of the configuration possibilities for the toolbar, and bestie, the list is extensive. it genuinely offers you many options to make your toolbar look just the way you want it. let's go:

-----------------------------------------
toolbar: <texture type>
toolbar.bevelWidth:             <integer (0-255)>
toolbar.borderColor:            <color>
toolbar.borderWidth:            <integer>
toolbar.button.scale:           <integer>
toolbar.color:                  <color>
toolbar.colorTo:                <color>
toolbar.clock:                  <texture type>
toolbar.clock.borderColor:      <color>
toolbar.clock.borderWidth:      <integer>
toolbar.clock.font:             <font>
toolbar.clock.justify:          <{Left|Right|Center}>
toolbar.clock.pixmap:           <filename>
toolbar.clock.color:            <color>
toolbar.clock.colorTo:          <color>
toolbar.clock.textColor:        <color>
toolbar.height:                 <integer>
toolbar.iconbar.focused:        <texture type>
toolbar.iconbar.focused.color:  <color>
toolbar.iconbar.focused.colorTo:<color>
toolbar.iconbar.focused.pixmap: <filename>
toolbar.iconbar.unfocused:      <texture type>
toolbar.iconbar.unfocused.color:  <color>
toolbar.iconbar.unfocused.colorTo: <color>
toolbar.iconbar.unfocused.pixmap: <filename>
toolbar.iconbar.empty:          <texture type>
toolbar.iconbar.empty.color:    <color>
toolbar.iconbar.empty.colorTo:  <color>
toolbar.iconbar.empty.pixmap:   <filename>
toolbar.iconbar.focused.borderColor: <color>
toolbar.iconbar.focused.borderWidth:    <integer>
toolbar.iconbar.unfocused.borderColor: <color>
toolbar.iconbar.unfocused.borderWidth:  <integer>
toolbar.iconbar.borderColor:    <color>
toolbar.iconbar.borderWidth:    <integer>
toolbar.iconbar.focused.font:   <font>
toolbar.iconbar.focused.justify:        <{Left|Right|Center}>
toolbar.iconbar.focused.textColor: <color>
toolbar.iconbar.unfocused.font: <font>
toolbar.iconbar.unfocused.justify:      <{Left|Right|Center}>
toolbar.iconbar.unfocused.textColor: <color>
toolbar.pixmap:                 <filename>
toolbar.shaped:                 <boolean>
toolbar.workspace.font:         <font>
toolbar.workspace.justify:      <{Left|Right|Center}>
toolbar.workspace.textColor:    <color>
toolbar.workspace:              <texture type>
toolbar.workspace.borderColor:  <color>
toolbar.workspace.borderWidth:  <integer>
toolbar.workspace.color:        <color>
toolbar.workspace.colorTo:      <color>
toolbar.workspace.pixmap:       <filename>
-----------------------------------------

the way there are three whole sub-sections living in here is sending me 😭 you got toolbar.clock, toolbar.iconbar (with focused, unfocused and empty variants — trio energy) and toolbar.workspace, all doing their own thing on top of the base toolbar: <texture type> with its .color and .colorTo.

couple of lil details that are easy to miss: toolbar.bevelWidth is <integer (0-255)> — yes, a range, respect the range. toolbar.button.scale and toolbar.height are plain <integer>. toolbar.shaped is a <boolean>. toolbar.pixmap is a <filename>. and toolbar.iconbar.focused.colorTo:<color> has no space after the colon in the original, which is giving chaotic but honestly it's fine, just vibe with it. 💀

the iconbar also gets its own border treatment layered like a little onion — toolbar.iconbar.focused.borderColor / .borderWidth, toolbar.iconbar.unfocused.borderColor / .borderWidth, and the general toolbar.iconbar.borderColor / .borderWidth — plus fonts, justifies and textColors for both focused and unfocused. periodt. 🔥

and toolbar.clock, toolbar.clock.font, toolbar.clock.justify with <{Left|Right|Center}> — capitals again, love that for us — plus .pixmap, .color, .colorTo and .textColor. the clock is literally the main character of the toolbar ngl ⭐

same for toolbar.workspace: .font, .justify (also <{Left|Right|Center}>), .textColor, the base <texture type>, .borderColor, .borderWidth, .color, .colorTo and .pixmap. she has range. 🌸

okay and there's still more coming in the next bit, so don't go anywhere — we're just getting to the good part 🫶💜

✨ EXAMPLES ✨

okay bestie, don't panic when you look at this list 😭 like yes it's long, but here's the tea: when you make your own style you can literally set most of these keys with a single component. no cap. for an example of this:

-----------------------------------------
*color: slategrey
*colorTo:       darkslategrey
*unfocus.color: darkslategrey
*unfocus.colorTo:       black
*textColor:     white
*unfocus.textColor:     lightgrey
*font:  lucidasans-10
-----------------------------------------

the way that one little block sets nice defaults for so many components… slay 💅 like that's the whole vibe, one component doing the absolute most.

🌈 COLOR FORMATS 🌈

so these are the color formats for styles, and there's genuinely only two of them so this is a short one 🎀

  • #000000 (Hexadecimal)
  • rgb:<0-255>/<0-255>/<0-255>

and if you want the full explanation, go peek at /usr/share/X11/rgb.txt — it's giving textbook, it's giving reference material, it's giving "i have all the answers" 📖✨

🫶 AUTHORS 🫶

so Blackbox was written and maintained by Brad Hughes <blackbox at alug.org> and Jeff Raven <jraven at psu.edu>. iconic of them honestly 👑

and fluxbox(1) is written and maintained by Henrik Kinnunen <fluxgen at fluxbox.org> with contributions and patches merged from many individuals around the world. like the whole planet showed up to help, we love to see it 🌍💖

the official fluxbox(1) website: http://www.fluxbox.org — and if you want styles, there are a LOT of them here: http://tenr.de/ — go wild, bestie 🦋

this manpage was composed from various resources including the official documentation, fluxbox(1) man page and numerous other resources by Curt "Asenchi" Micol. and if you notice any errors or problems with this page, please contact him here: <asenchi at asenchi.com> — and using the great contributions of <grubert at users.sourceforge.net>. and lowkey, numerous other languages could be available if someone jumps in 👀 like the door is open, someone come through 🙈

👀 SEE ALSO 👀

go read those too, they're the supporting cast and they ate ✨

💜 AUTHOR 💜

  • Henrik Kinnunen <fluxgen@fluxbox.org> — Author. 👑

and that's a wrap on the whole page, bestie 🎀 the source is fluxbox-style.txt, dated 08 February 2015, and it lives in the FLUXBOX-STYLE(5) section — so if anyone asks where you got all this, that's the receipt 💅✨ go forth and make something iconic 🌸🦋

📦 where this page comes from