awesome/lib/naughty/init.lua

---------------------------------------------------------------------------
-- @author Uli Schlachter <psychon@znc.in>
-- @copyright 2014 Uli Schlachter
-- @module naughty
---------------------------------------------------------------------------

local naughty = require("naughty.core")
local gdebug = require("gears.debug")
local capi = {awesome = awesome, screen = screen}
if dbus then
    naughty.dbus = require("naughty.dbus")
end

naughty.action = require("naughty.action")
naughty.list = require("naughty.list")
naughty.layout = require("naughty.layout")
naughty.widget = require("naughty.widget")
naughty.container = require("naughty.container")
naughty.action = require("naughty.action")
naughty.notification = require("naughty.notification")

-- Attempt to handle early errors when using the manual screen mode.
--
-- Creating a notification popup before the screens are added won't work. To
-- work around this, the code below initializes some screens. One potential
-- problem is that it could emit enough signal to cause even more errors and
-- lose the original error.
--
-- For example, the following error can be displayed using this fallback:
--
--    screen.connect_signal("scanned", function() foobar() end)
--
local function screen_fallback()
    if capi.screen.count() == 0 then
        gdebug.print_warning("An error occurred before a screen was added")

        -- Private API to scan for screens now.
        if #screen._viewports() == 0 then
            screen._scan_quiet()
        end

        local viewports = screen._viewports()

        if #viewports > 0 then
            for _, viewport in ipairs(viewports) do
                local geo = viewport.geometry
                local s = capi.screen.fake_add(geo.x, geo.y, geo.width, geo.height)
                s.outputs = viewport.outputs
            end
        else
            capi.screen.fake_add(0, 0, 640, 480)
        end
    end
end

-- Handle runtime errors during startup
if capi.awesome.startup_errors then

    -- Wait until `rc.lua` is executed before creating the notifications.
    -- Otherwise nothing is handling them (yet).
    client.connect_signal("scanning", function()
        -- A lot of things have to go wrong for this to happen, but it can.
        screen_fallback()

        naughty.emit_signal(
            "request::display_error", capi.awesome.startup_errors, true
        )
    end)
end

-- Handle runtime errors after startup
do
    local in_error = false

    capi.awesome.connect_signal("debug::error", function (err)
        -- Make sure we don't go into an endless error loop
        if in_error then return end

        in_error = true

        screen_fallback()

        naughty.emit_signal("request::display_error", tostring(err), false)

        in_error = false
    end)

end

return naughty

-- vim: filetype=lua:expandtab:shiftwidth=4:tabstop=8:softtabstop=4:textwidth=80