-
-
Save tych0/2165083 to your computer and use it in GitHub Desktop.
| new windows don't steal focus from prompt widget | |
| * make new windows stealing focus configurable | |
| default config in /etc/qtile/config.py |
Blegh.
Ok - let's run a diff against the upstream and our fork and see what's different and if the changes are fast-forwards?
Easier in theory than in practice. Go for it if you want, though :-)
Even a diff would be useful to know where we've diverged, tbh. You know? Even if it turns out that they won't accept patches and we really do need our own fork of it, then it's best to know where and what code needs to stay untouched vs upstream.
Feel free to look yourself:
git remote add freedesktop git://anongit.freedesktop.org/xcb/xpyb
git diff master freedesktop/master
Do you recommend a diff against your branch?
libqtile/manager.py/cmd_function, btw ;)
Ah, cool. Looks exactly like what I had :-). And yeah, I think my branch is the only one with 1.3.1 merged into it.
Right, I ran a diff last night with your master v freedesktop/master and I poured over it a lil' and it seems there are quite a few changes here and there.
I'd like to test that cmd_function a bit more and also, maybe look into creating a decorator to apply to functions?
Something like:
@keycommand(Key([alt], "f"))
def super_awesome_function(qtile):
qtile.groupMap['group1'].windows
# do awesome cool stuffs
return 1Thoughts on that? Lazy has a reference to Qtile therefore a reference to the commands. Could work with some minor modifications to manager.Key.
Finally, me and Cjbarnes had a pretty boss idea of having app specific key maps using the Qtile.keyMap dictionary and mutating it on python client_new and python focus_change hooks. Thoughts on that? Could even hook layout_change to modally change the keyMap because there are some commands that become rundundant in people's configs in certain layout modes.
Just a thought, the keyMap mechanism is very interesting!
Evidentally, I'm a github markdown noob,
As far as I know, we still need xpyb-ng. As for what's different, we've had one guy install from upstream and, although his unit tests fail with what looks like xpyb vs xpyb-ng related errors, he says the WM runs fine (although I expect he'll get some crashes at some point). I too would like to stop maintaining this fork, but I haven't had time to push patches upstream.