Skip to main content

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

3
  • Indeed. It also means that I have to store it somewhere as part of my .bashrc, and deal with any weird inconsistencies. That's helpful to know though, it's more reliable than using wmctrl :ACTIVE:. edit: ..err wait, I just skimmed the answer. Umm actually that's really helpful, thanks. Maybe I could run inotify on those files...?? Is that a crazy idea?
    – intuited
    Commented Aug 8, 2010 at 22:23
  • The effects of having screen in play are interesting: this means that I'm actually looking for a list of window IDs. I was gonna let that go, for now :)
    – intuited
    Commented Aug 8, 2010 at 22:24
  • err.. nevermind, inotify wouldn't work unless something in the process environment changes when something like that happens, which I doubt. I'd have to check the parent (screen, roxterm, etc.) environment for changes, assuming it tracks that there, which seems unlikely.
    – intuited
    Commented Aug 8, 2010 at 22:30