This post is about what must be done before modularizing rc.lua. It is more about Lua Code style, and the process of splitting the codes. And not the configuration itself. I’m using Object Oriented Approach, a beginner perspective.

It is too early for me to release my modularized awesome WM configuration. This topic itself is long enough, that I don’t want to mix it with another topic.


No long configuration, short enough to be analyzed

I have refactored rc.lua into some files few month ago, but it is not enough. I’m a beginner in lua world, and I’m not smart enough to read long source code. So I decide to make my rc.lua part smaller. Each files should be small enough to be analyzed file by file.

Problem Definition

After a hard time of reading rc.lua, I finaly realized that rc.lua consist of these parts

  1. Sequence of code, e.g

    • Error Handling

    • Initializing Theme

    • Signals

    • User Variables: Theme, Device, Statusbar Design

  2. Defining Variable

    • Layouts and Tags

    • Menu, submenu, menu generator

    • Rules

    • GlotbalKeys, GlobalButtons

    • ClientKeys, Clientbuttons

  3. Other than those two above

    • Creating Wibox: Pack sequence of code into Function

    • Miscelannous

It takes Lua knowledge to split lua-based configuration

Modularized Awesome WM Code Main

Loading module in Lua

There is a strange concept of array in Lua called Table. Table is a container of associative array stored in key/value pairs. Since Module in Lua is just container of stuff. Then Module in Lua is just a Table.

You can call a module by simply use the require keyword.

Optionally, when calling a Module, it can be stored in a variable, this variable can be thought as an alias of modules.

-- Required libraries
local awful     = require("awful")
local beautiful = require("beautiful")
local menubar = require("menubar")
naughty = require('naughty')

Splitting Config

Splitting configuration source code is easy, the ‘dofile’ function can do the horsework.

This dofile simply run another lua file, and doesn’t do any check like require does.

local config_path = awful.util.getdir("config") .. "/"

dofile(config_path .. "main/error-handling.lua")
dofile(config_path .. "main/theme.lua")

Now I can move-and-paste the lua-code from rc.lua to other lua file.

Now let’s see what is in this file main/theme.lua.

Configuration Source Code: main/theme.lua

home = os.getenv("HOME")

-- Themes define colours, icons, font and wallpapers.

if beautiful.wallpaper then
    for s = 1, screen.count() do
        gears.wallpaper.maximized(beautiful.wallpaper, s, true)

Require in Each Lua

There is something you should do each time move-and-paste lua-code. You should also move the required module.

In that configuration above, it needs some beautiful and gears.

---- Standard awesome library
local gears     = require("gears")

-- Theme handling library
local beautiful = require("beautiful")

Module Containing Variable

The next steps is move each variables to Lua files.

Sample Configuration Source Code: main/user-variables.lua

Let’s say we have terminal variable

terminal = "xfce4-terminal"

We can just move-and-paste to a file, e.g myvar.lua and let the variable be a global variable.

terminal = "xfce4-terminal"

As n00b coming from other language, I avoid global variable as possible.

There are some alternative on how to make module in Lua

Lua 5.0, using module function


function get_terminal()
  return "xfce4-terminal"

This is deprecated.

Lua 5.2, using table

We can use any table name, e.g. _M

local _M = {}

function _M.get_terminal()
  return "xfce4-terminal"

return _M

And in main rc.lua, we can call

local myvar = require("main.myvar")

local terminal = myvar.get_terminal()

I also made the terminal in rc.lua as local.

Module Containing Only One Variable

For module with only one variable, We can also make the call simple.

local _M = {}

function _M.get()
  return "xfce4-terminal"

return setmetatable({}, { __call = function(_, ...) return _M.get(...) end })

And in main rc.lua, we can call

local myvar = require("main.myvar")

local terminal = myvar()

No need to call get() explicitly.

Real lua.rc Sample

Let’s see our globalbutton moved to main/globalbuttons.lua. Do not confuse the name globalbuttons with global variables. It is just a variable name, it could be global or local.

Modularized Awesome WM Code Module

Original in rc.lua.

  awful.button({ }, 3, function () mymainmenu:toggle() end),
  awful.button({ }, 4, awful.tag.viewnext),
  awful.button({ }, 5, awful.tag.viewprev)

Splitted from rc.lua.

To binding/globalbuttons.lua

Configuration Source Code: binding/globalbuttons.lua

local awful = require("awful")

local _M = {}

function _M.get()
  local globalbuttons = awful.util.table.join(
      awful.button({ }, 3, function () mymainmenu:toggle() end),
      awful.button({ }, 4, awful.tag.viewnext),
      awful.button({ }, 5, awful.tag.viewprev)

  return globalbuttons

return setmetatable({}, { __call = function(_, ...) return _M.get(...) end })

Calling from rc.lua

local binding = {
  globalbuttons = require("binding.globalbuttons")

-- Set root

Splitting Long Module

Not everything should be packed with these code style. It all depends on your creativity and imagination.

I once had my wibox statusbar configuration. I have packed some plain sequence of code into bunch of function. Short enough for expert, but long enough for me, so I move some function into a helper.

Let’s see the code. Instead of the _M table that can be returned as public. I also make a WB table that is private, only visible for this module.

Note how I declare global table wibox_package as a bridge between these two Lua file.

in anybox/arrow/statusbar.lua

Configuration Source Code: statusbar.lua

local _M = {}

local WB = {}
wibox_package = WB               -- global object name

local config_path = awful.util.getdir("config") .. "/anybox/"
dofile(config_path .. "helper.lua")

WB.generate_wibox_top = function (s)

WB.generate_wibox_bottom = function (s)

function _M.init()

return _M

in anybox/arrow/helper.lua

Configuration Source Code: helper.lua

local WB = wibox_package

function WB.initdeco() ... end
function WB.updatelayoutbox(layout, s) ... end
WB.setup_common_boxes = function (s) ... end
WB.vicious_widgets = function (screen) ... end
WB.multicolor_widgets_top = function (screen) ... end

Module with many containers

The issue goes further when I decorate Wibox. It has a bunch of monitoring stuff, e.g cpu, mem, netup, netdown, time, battery, diskfree, alsabar, mpd and so on. Each widget utilize icon and text. For example cpu, it has memicon and memtext.

Instead of using namespace as memicon and cmemtext. I’m using table approach I.mem, and W.mem.

I’m using global table, instead of local _M table.

in anybox/lain/lain.lua

Configuration Source Code: lain.lua

local W = {}
lain_widget_set = W           -- object name

local I = {}
lain_icon_set = I             -- object name = ... = ...

I.mem = ...
W.mem = ...


I also move long chunks, that require a lot of variable.

in anybox/lain/lain-diskfree

Configuration Source Code: lain-diskfree.lua

I.disk = ...

W.disk_bar = ...
W.disk_margin = wibox.layout.margin(W.disk_bar, 2, 7)

local disk_widget_settings = function()

W.disk_widget_update = lain.widgets.fs({

W.disk_bar_widget = wibox.widget.background(W.disk_margin)

That’s all for now.

It doesn’t look complicated once, you get in to the source code.

In fact the source configuration is easier to be read now.

Configuration Source

This the result.

├── rc.lua
├── main
│   ├── error-handling.lua
│   ├── layouts.lua
│   ├── menu.lua
│   ├── rules.lua
│   ├── signals.lua
│   ├── tags.lua
│   ├── theme.lua
│   └── user-variables.lua
├── binding
│   ├── bindtotags.lua
│   ├── clientbuttons.lua
│   ├── clientkeys.lua
│   ├── globalbuttons.lua
│   ├── globalkeys.lua
│   ├── taglist.lua
│   └── tasklist.lua
├── modules
│   └── menugen
├── themes
│   └── clone
└── anybox
    ├── titlebar.lua
    ├── simple
    │   └── statusbar.lua
    └── *

Thank you for reading