Open MOIS3Y opened 1 year ago
Yes the way that the used awesomewm version is detected doesn't work reliably because the version "tag" is set as a build variable and is thus up to the package manager most of the time. So this change would break for arch users and probably others instead. It is a valid issue and I don't have a proper solution right now but open for input
@Nooo37 I think something similar to this could work?
local _ruled_status, ruled = pcall(function()
return require("ruled")
end)
if not _ruled_status or not ruledthen
-- 4.3 code
else
-- 4.4 code
end
@Kasper24 That looks good!
I have this problem too. Is it still not possible to fix it?
Hello, I'm not sure whether it was worth opening the issue, I encountered a strange import problem on awesome wm stable 4.3
I just add bling as a git submodule in ~/.config/awesome/modules/bling
When trying to start awesomewm:
Here is this line:
I checked what result I would get in my rc.lua:
Accordingly, if fix ./bling/module/scratchpad.lua:6
Everything is working.
Like I said, I'm not sure if this is a module issue or if I'm the only one experiencing this. In case this is important, I use the nixOS version of awesomewm without modifications which comes with the configuration: