Re: [STUMP] window/frame model

[Eric Abrahamsen]

On Sat, Sep 15 2012, Michael Raskin wrote:

> <address@hidden>)
> Mime-Version: 1.0
> Content-type: text/plain; charset="UTF-8"
>
>>Interesting That's good to know, though my problem here is with
>>targeting the correct frame and window, not with sending the keypress.
>>I'll muddle with it a bit more.
>
> Could you specify more precisely what you do want? You could just 
> iterate over all the windows and choose based on window title/window 
> class/window role. Then bring the window to front and send whatever 
> events you want. 
>
> Or you could use my window-tags contrib module, tag the window once and
> simply bring it up by tag - if every tag is only used once filtering 
> problem is non-existent. 
>
> Or if you don't want to use either window tags or manual iteration, you
> can get my wse.lisp contrib-candidate module 
> http://mtn-host.prjek.net/viewmtn/stumpwm-tagging/branch/changes/com.ignorelist.401a0bf1.raskin.stumpwm-config
> (browse files and get wse.lisp). The code will look like
>
> (act-on-matching-windows
>   (w :screen)
>   (and
>     (or
>       (titled-p w "Precise Title")
>       (title-re-p w "Title re[gu]{2}lar expression")
>       )
>     (classed-p w "Window class")
>     (in-current-group-p w)
>     )
>   ; Bring the w window where you wish (probably, focus-window and 
>   ; really-raise-window could be used) and send it events
>   )

Thanks -- these are some interesting options, and I've been meaning to
look at the window-tags contrib module for a while. In this instance I
actually *don't* want anything very complicated: my use-case is just to
throw individual keypresses (most often scrolling a web-page) at the
frame next to the one I'm working in, and 90% of the time that's the
frame I accessed most recently.

Eric