freenode/#stumpwm - IRC Chatlog
Search
17:31:28
sjl
is there a better way to get the current frame (in code) than (tile-group-current-frame (current-group)) ?
19:29:55
kriyative
sjl: that seems to be the idiomatic way, at least across the stumpwm source files. Is there an issue/limitation getting it that way?
19:53:34
sjl
kriyative: no, just wondering if there's something simpler I was missing. there's (current-group) and (current-window) but no (current-frame), so I wasn't sure if maybe there was a reason I shouldn't be doing things based on the current frame
20:02:52
kriyative
sjl: ah, depends on what you're trying to do - I suppose. If it's window oriented (which tends to be most things I do) then you could just use `current-window`
20:04:19
sjl
I'm trying to write a move-focus replacement that will run gnext if you run it while already at the rightmost frame
20:04:20
kriyative
The current frame would be useful when you are working on frame management, I'd imagine - like managing the screen real-estate in some way
20:08:46
sjl
if I'm moving right, and I'm at the right edge, I want to move to the next group but ALSO make sure the leftmost frame in that group is focused
20:09:19
sjl
so I just moved left ten times, assuming I'll never have more than ten frames in a group
20:19:33
kriyative
sjl: might want to look at `group-frames` and `frame-by-number` for a more precise way to select the frame to move focus to
20:20:02
sjl
unfortunately the numbers don't seem to be grouped horizontally left-to-right necessarily
20:20:50
kriyative
hmm, maybe I need to move my frames/windows around a bit, but the little I did the ordering seemed to be maintained in `group-frames`
20:46:54
sjl
and unfortunately I don't see a way to detect if a group happens to be a floating group