Hello there.
I'm running this plugin for years now, and if I remember well,
the first thing I did after installing it was to remove the rule L.103,
that states it should cycle only among unminimized windows.
I don't see the point in that. Wouldn't be more rational to provide
a very standard behavior and then let users customize it to their needs ?
-- Default builtin filters.
-- (meant to get applied always, but you could override them)
cycle_filters = {
--function(c, source_c) return not c.minimized end, --luacheck: no unused args
},
Configured like so to avoid excessive flashing displays
cyclefocus.key({ "Mod1", }, "Tab", { show_clients = false, focus_clients = true, }),
IMO, this plugin lands in the domain of
"the functions users are very used to have on a WM"
and that, when missing, may lead them to look somewhere else.
Thanks a lot for writing it !
Hello there.
I'm running this plugin for years now, and if I remember well,
the first thing I did after installing it was to remove the rule L.103,
that states it should cycle only among unminimized windows.
I don't see the point in that. Wouldn't be more rational to provide
a very standard behavior and then let users customize it to their needs ?
Configured like so to avoid excessive flashing displays
IMO, this plugin lands in the domain of
"the functions users are very used to have on a WM"
and that, when missing, may lead them to look somewhere else.
Thanks a lot for writing it !