vincentbernat.i3wm-configur.../rc/quake.lua

local quake = loadrc("quake", "vbe/quake")

local quakeconsole = {}
for s = 1, screen.count() do
   quakeconsole[s] = quake({ terminal = config.terminal,
                             argname = "--name %s",
			     height = 0.3,
			     screen = s })
end

config.keys.global = awful.util.table.join(
   config.keys.global,
   awful.key({ modkey }, "`",
	     function () quakeconsole[mouse.screen]:toggle() end,
	     "Toggle Quake console"))
quake: new Quake module that handles awesome restart gracefully The previous RC file is moved as a module. We don't rely on the fact that the next window to be managed after spawning a new terminal will be this terminal. Instead, we rely on terminal name to know if we need to manage them. For each console, we have a manage hook that tries to identify if the window to manage is the console. In this case, it is transformed and fitted as a Quake console. Moreover, we clean things that look like QuakeConsole but that are not because we already have one. For example, when switching from a two-screen setup to a single-screen setup. 2012-07-15 12:44:46 +02:00			`local quake = loadrc("quake", "vbe/quake")`
quake: add a quake-like console 2012-07-13 15:23:22 +02:00
quake: new Quake module that handles awesome restart gracefully The previous RC file is moved as a module. We don't rely on the fact that the next window to be managed after spawning a new terminal will be this terminal. Instead, we rely on terminal name to know if we need to manage them. For each console, we have a manage hook that tries to identify if the window to manage is the console. In this case, it is transformed and fitted as a Quake console. Moreover, we clean things that look like QuakeConsole but that are not because we already have one. For example, when switching from a two-screen setup to a single-screen setup. 2012-07-15 12:44:46 +02:00			`local quakeconsole = {}`
			`for s = 1, screen.count() do`
			`quakeconsole[s] = quake({ terminal = config.terminal,`
terminal: don't use env variable to give a name to GTK terminal GTK applications accept `--name` as a special parameter just for that. 2014-09-23 20:49:21 +02:00			`argname = "--name %s",`
quake: new Quake module that handles awesome restart gracefully The previous RC file is moved as a module. We don't rely on the fact that the next window to be managed after spawning a new terminal will be this terminal. Instead, we rely on terminal name to know if we need to manage them. For each console, we have a manage hook that tries to identify if the window to manage is the console. In this case, it is transformed and fitted as a Quake console. Moreover, we clean things that look like QuakeConsole but that are not because we already have one. For example, when switching from a two-screen setup to a single-screen setup. 2012-07-15 12:44:46 +02:00			`height = 0.3,`
			`screen = s })`
quake: add a quake-like console 2012-07-13 15:23:22 +02:00			`end`

			`config.keys.global = awful.util.table.join(`
			`config.keys.global,`
quake: new Quake module that handles awesome restart gracefully The previous RC file is moved as a module. We don't rely on the fact that the next window to be managed after spawning a new terminal will be this terminal. Instead, we rely on terminal name to know if we need to manage them. For each console, we have a manage hook that tries to identify if the window to manage is the console. In this case, it is transformed and fitted as a Quake console. Moreover, we clean things that look like QuakeConsole but that are not because we already have one. For example, when switching from a two-screen setup to a single-screen setup. 2012-07-15 12:44:46 +02:00			awful.key({ modkey }, "`",
			`function () quakeconsole[mouse.screen]:toggle() end,`
			`"Toggle Quake console"))`